From: Andi Kleen <andi@firstfloor.org>
To: David Miller <davem@davemloft.net>
Cc: shemminger@linux-foundation.org, greearb@candelatech.com,
bridge@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH] bridge: avoid ptype_all packet handling
Date: 03 Mar 2007 03:14:29 +0100 [thread overview]
Message-ID: <p733b4ncbui.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070228.233034.74746721.davem@davemloft.net>
David Miller <davem@davemloft.net> writes:
>
> And in fact that effectively makes the new socket option
> pointless, since it doesn't buy us anything since we have
> to support the old stuff fully anyways.
I don't think it's pointless because it would still allow
newer DHCP clients to have less impact on other packets
when they are active.
This can matter when you have a system with multiple
interfaces where DHCP doesn't get a address on one.
That's pretty common with many x86 server boards because
they come with two NICs by default but must people only
plug the cable into one. However the distro installers
run DHCP on all.
When this happens all packets are always forced through
ptype_all chains before being rejected by AF_PACKETs device
bind, which adds some overhead to them.
-Andi
next prev parent reply other threads:[~2007-03-03 1:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 1:18 [PATCH] bridge: avoid ptype_all packet handling Stephen Hemminger
2007-03-01 1:28 ` Ben Greear
2007-03-01 3:56 ` Stephen Hemminger
2007-03-01 4:05 ` Ben Greear
2007-03-01 7:04 ` Stephen Hemminger
2007-03-01 7:22 ` David Miller
2007-03-01 7:26 ` Stephen Hemminger
2007-03-01 7:30 ` David Miller
2007-03-01 11:47 ` jamal
2007-03-03 2:14 ` Andi Kleen [this message]
2007-03-03 4:22 ` David Miller
2007-03-03 7:09 ` Stephen Hemminger
2007-03-03 12:30 ` Andi Kleen
2007-03-02 21:26 ` David Miller
2007-03-02 22:09 ` [RFC 1/2] " Stephen Hemminger
2007-03-02 22:14 ` [RFC 2/2] bridge: per device promiscious taps Stephen Hemminger
2007-03-02 22:48 ` [RFC 1/2] bridge: avoid ptype_all packet handling David Miller
2007-03-02 23:18 ` David Miller
2007-03-02 23:34 ` Stephen Hemminger
2007-03-02 23:41 ` David Miller
2007-03-03 5:38 ` Herbert Xu
2007-03-03 5:59 ` David Miller
2007-03-03 6:42 ` Herbert Xu
2007-03-02 22:15 ` Stephen Hemminger
2007-03-03 12:04 ` [PATCH] " Stefan Rompf
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=p733b4ncbui.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=bridge@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).