From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Harald Welte <laforge@netfilter.org>,
James Morris <jmorris@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
netdev@redhat.com
Subject: Re: Netlink connector
Date: Tue, 26 Jul 2005 13:01:14 +0400 [thread overview]
Message-ID: <20050726090114.GA870@2ka.mipt.ru> (raw)
In-Reply-To: <20050726084214.GG7925@rama>
On Tue, Jul 26, 2005 at 04:42:14AM -0400, Harald Welte (laforge@netfilter.org) wrote:
> On Mon, Jul 25, 2005 at 02:02:10AM -0400, James Morris wrote:
> > On Sun, 24 Jul 2005, David S. Miller wrote:
> > >From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
> > >Date: Sat, 23 Jul 2005 13:14:55 +0400
> > >>Andrew has no objection against connector and it lives in -mm
> > >A patch sitting in -mm has zero significance.
> >
> > The significance I think is that Andrew is trying to gently encourage some
> > further progress in the area.
>
> Patrick McHardy is currently working on some ideas on how to extend
> netlink.
>
> The fundamental problem that the connector is trying to solve:
>
> 1) provide more 'groups' (to transport more different kinds of events)
> 2) provide an abstract API for other kernel code, so it doesn't have to
> know anything about skb's or networking.
>
> IMHO issue number '1' should (and can) be adressed within netlink. Wait
> for Patrick's work on this to show up on netdev. We can then think
> whether the connctor API (or something similar) can be put on top of it.
Fair enough.
Let's do it this way.
> --
> - Harald Welte <laforge@netfilter.org> http://netfilter.org/
> ============================================================================
> "Fragmentation is like classful addressing -- an interesting early
> architectural error that shows how much experimentation was going
> on while IP was being designed." -- Paul Vixie
--
Evgeniy Polyakov
prev parent reply other threads:[~2005-07-26 9:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 12:54 [PATCH] 1 Wire drivers illegally overload NETLINK_NFLOG Harald Welte
2005-07-23 3:05 ` YOSHIFUJI Hideaki / 吉藤英明
2005-07-23 13:33 ` Harald Welte
2005-07-25 2:09 ` David S. Miller
2005-07-25 2:15 ` David S. Miller
2005-07-26 9:48 ` Harald Welte
2005-07-23 9:14 ` Evgeniy Polyakov
2005-07-25 2:17 ` David S. Miller
2005-07-25 6:02 ` Netlink connector James Morris
2005-07-25 7:06 ` Evgeniy Polyakov
2005-07-25 14:32 ` Patrick McHardy
2005-07-25 14:43 ` Eric Leblond
2005-07-25 19:33 ` Evgeniy Polyakov
2005-07-26 8:45 ` Harald Welte
2005-07-25 19:28 ` Evgeniy Polyakov
2005-07-25 23:46 ` Patrick McHardy
2005-07-25 23:56 ` Thomas Graf
2005-07-26 0:16 ` Patrick McHardy
2005-07-26 0:30 ` Thomas Graf
2005-07-26 4:45 ` Evgeniy Polyakov
2005-07-26 4:56 ` Stephen Hemminger
2005-07-26 5:01 ` Evgeniy Polyakov
2005-07-26 6:14 ` Thomas Graf
2005-07-26 6:31 ` Evgeniy Polyakov
2005-07-26 8:42 ` Harald Welte
2005-07-26 9:01 ` Evgeniy Polyakov [this message]
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=20050726090114.GA870@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=jmorris@redhat.com \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@redhat.com \
--cc=netfilter-devel@lists.netfilter.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox