From: Ben Greear <greearb@candelatech.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: David Miller <davem@davemloft.net>,
deri@ntop.org, shemminger@vyatta.com, brad.doctor@gmail.com,
netdev@vger.kernel.org
Subject: Re: PF_RING: Include in main line kernel?
Date: Thu, 15 Oct 2009 09:33:53 -0700 [thread overview]
Message-ID: <4AD74EF1.6080106@candelatech.com> (raw)
In-Reply-To: <20091015070234.GA29506@ioremap.net>
On 10/15/2009 12:02 AM, Evgeniy Polyakov wrote:
> On Wed, Oct 14, 2009 at 02:49:23PM -0700, David Miller (davem@davemloft.net) wrote:
>>> Maybe something similar to the attached patch?
>>
>> This is not something I'm interested in applying.
>>
>> It makes implementing proprietary complete networking stacks
>> for Linux way too easy.
>
> Such kernels will be tainted and thus its bugs and problems will be
> clearly indicated by the proprietary module.
>
>> Instead I'd rather have a GPL exported function that allows indication
>> of consumption somehow. That's why we have a special hook for
>> bonding, so it cannot be abused in proprietary modules.
>
> I believe bonding with its hook is a historical heritage and priority
> absence in packet hooks which do not currently allow something to be
> registered very first and steal packets from the stack.
>
> Looks like bonding could be implemented as a packet handler with Ben's
> patch applied, isn't it?
Bonding, bridging, mac-vlans, pktgen-rx logic, sniffers, and others could. The only trick is
ordering...it may be better to keep the hard-coded hooks in a definite
order than to allow users to switch them around.
Or, could have a precedence value when adding hooks (protocols) so that modules
can properly order themselves by default, but users *could* reorder
them if they really wanted to (might be useful to have mac-vlans before
bonding some of the time, and after it others, for instance...)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2009-10-15 16:35 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 14:33 PF_RING: Include in main line kernel? Brad Doctor
2009-10-14 16:01 ` Stephen Hemminger
2009-10-14 17:02 ` Brad Doctor
2009-10-14 19:33 ` Stephen Hemminger
2009-10-14 20:17 ` Luca Deri
2009-10-14 20:27 ` David Miller
2009-10-15 0:25 ` Eric Dumazet
2009-10-14 20:36 ` Evgeniy Polyakov
2009-10-14 21:27 ` Ben Greear
2009-10-14 21:34 ` Luca Deri
2009-10-14 21:49 ` David Miller
2009-10-14 23:29 ` Ben Greear
2009-10-15 7:02 ` Evgeniy Polyakov
2009-10-15 7:22 ` David Miller
2009-10-15 16:33 ` Ben Greear [this message]
2009-10-18 12:45 ` Harald Welte
2009-10-18 12:43 ` Harald Welte
2009-10-18 14:18 ` Evgeniy Polyakov
2009-10-14 16:46 ` Jarek Poplawski
2009-10-14 17:02 ` Brad Doctor
2009-10-14 17:18 ` Jarek Poplawski
2009-10-18 12:47 ` [OT] ntop / GPL (was Re: PF_RING: Include in main line kernel?) Harald Welte
2009-10-19 5:55 ` Jarek Poplawski
2009-10-19 7:12 ` Jarek Poplawski
2009-10-14 18:19 ` PF_RING: Include in main line kernel? Brent Cook
2009-10-14 19:54 ` Luca Deri
2009-10-14 20:15 ` David Miller
2009-10-14 20:26 ` Luca Deri
2009-10-14 20:29 ` David Miller
2009-10-14 20:34 ` Luca Deri
2009-10-14 20:50 ` Mark Smith
2009-10-18 12:56 ` Harald Welte
2009-10-18 12:50 ` Harald Welte
2009-10-18 14:50 ` Evgeniy Polyakov
2009-10-15 7:35 ` Rémi Denis-Courmont
2009-10-18 12:38 ` Harald Welte
2009-10-18 17:37 ` Luca Deri
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=4AD74EF1.6080106@candelatech.com \
--to=greearb@candelatech.com \
--cc=brad.doctor@gmail.com \
--cc=davem@davemloft.net \
--cc=deri@ntop.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=zbr@ioremap.net \
/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;
as well as URLs for NNTP newsgroup(s).