All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: hadi@cyberus.ca
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Harald Welte <laforge@netfilter.org>,
	lmb@suse.de, ahu@ds9a.nl, hch@infradead.org, netdev@oss.sgi.com,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables CLUSTERIP target)
Date: Fri, 22 Oct 2004 16:32:39 +0400	[thread overview]
Message-ID: <1098448359.5211.199.camel@uganda> (raw)
In-Reply-To: <1098447593.1112.77.camel@jzny.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

On Fri, 2004-10-22 at 16:19, jamal wrote:
> On Fri, 2004-10-22 at 07:39, Herbert Xu wrote:
> > On Fri, Oct 22, 2004 at 07:29:39AM -0400, jamal wrote:
> > > 
> > > Evgeniy Polyakov(aka mr. Sean Paul) posted code a while back for
> > > something that uses netlink that he calls  "kernel Konnector". I think
> > 
> > That patch puts the ID in each message, right?
> 
> Yes, the ID is necessary for "routing" the message. Remember this is for
> a messaging subsystem so you cant avoid having something that is in the
> packet that is used to find where to go next.
> I was suggesting also messaging by name.
> 
> > That would mean paying the lookup cost for each message rather than
> > once when you create the socket.
> > 
> 
> Take a look at the patch. See how it can be made better.
> Evgeniy, Do you have something new to post?

Nothing major, only multicast group selection by id.
Although I think message sending mechanism can use unicast.
Both have it's own advantages.

> cheers,
> jamal
-- 
	Evgeniy Polyakov

Crash is better than data corruption. -- Art Grabowski

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-22 12:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 22:38 [PATCH 2.6] iptables CLUSTERIP target Harald Welte
2004-10-20 23:18 ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-21  4:40   ` David S. Miller
2004-10-21  7:44 ` Christoph Hellwig
2004-10-21  7:55 ` Christoph Hellwig
2004-10-21  9:12   ` Harald Welte
2004-10-21  9:40     ` Herbert Xu
2004-10-21 11:05     ` bert hubert
2004-10-21 13:03       ` Harald Welte
2004-10-21 13:33         ` Lars Marowsky-Bree
2004-10-21 14:25           ` Harald Welte
2004-10-21 15:08             ` bert hubert
2004-10-21 21:31             ` Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables CLUSTERIP target) Herbert Xu
2004-10-21 22:53               ` Thomas Graf
2004-10-21 23:02                 ` Allowing netlink_family to be any integer Ben Greear
2004-10-22 12:25                 ` Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables CLUSTERIP target) Herbert Xu
2004-10-22 12:53                   ` jamal
2004-10-22 11:29               ` jamal
2004-10-22 11:39                 ` Herbert Xu
2004-10-22 12:19                   ` jamal
2004-10-22 12:32                     ` Evgeniy Polyakov [this message]
2004-10-22 23:05               ` David S. Miller
2004-10-22 23:16                 ` Herbert Xu
2004-10-26  3:27                   ` David S. Miller
2004-10-21 16:36 ` [PATCH 2.6] iptables CLUSTERIP target, seq_file version Harald Welte
2004-10-21 17:44   ` jamal
2004-10-21 18:03     ` Harald Welte
2004-10-21 18:41       ` Henrik Nordstrom
2004-10-22  5:52   ` David S. Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1098448359.5211.199.camel@uganda \
    --to=johnpol@2ka.mipt.ru \
    --cc=ahu@ds9a.nl \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=hch@infradead.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=laforge@netfilter.org \
    --cc=lmb@suse.de \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.