From: Stephen Hemminger <shemminger@vyatta.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kaber@trash.net,
eric.dumazet@gmail.com
Subject: Re: net: replace hooks in __netif_receive_skb (v4)
Date: Tue, 1 Jun 2010 09:10:04 -0700 [thread overview]
Message-ID: <20100601091004.7885cd8c@nehalam> (raw)
In-Reply-To: <20100601154106.GA4929@psychotron.redhat.com>
On Tue, 1 Jun 2010 17:41:07 +0200
Jiri Pirko <jpirko@redhat.com> wrote:
> Actually, I'm not happy about this (reducing to only one hook) and for two
> reasons:
>
> 1) I think it's a good behaviour to "mask" one handler by another in case device
> is for example used for macvlan and then added to bridge. Because when it's
> again removed from the bridge, the original functionality is restored. And also,
> this would be consistent with the current behaviour.
>
> 2) I would imagine a situation, when multiple handers are needed in cascade.
> Actually I'm working on a virtual device draft which uses two handlers, although
> in corner situation.
>
> Regards,
> Jirka
I don't like it because:
1) Adding macvlan to bridge makes no sense. The bridge is already in promicious mode.
2) I don't like to see functionality added when it is not needed.
3) The extra overhead of traversing list causes more cache activity in extreme
hot path.
Wait and add the multiple handlers when your code is included.
--
http://www.extremeprogramming.org/rules/early.html
next prev parent reply other threads:[~2010-06-01 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 18:08 [PATCH net-next-2.6] net: replace hooks in __netif_receive_skb V2 Jiri Pirko
2010-05-27 20:08 ` Stephen Hemminger
2010-05-28 5:51 ` Jiri Pirko
2010-05-28 6:12 ` [PATCH net-next-2.6] net: replace hooks in __netif_receive_skb V3 Jiri Pirko
2010-05-28 7:02 ` Eric Dumazet
2010-05-28 7:33 ` [PATCH net-next-2.6] net: replace hooks in __netif_receive_skb V4 Jiri Pirko
2010-06-01 15:28 ` net: replace hooks in __netif_receive_skb (v4) Stephen Hemminger
2010-06-01 15:41 ` Jiri Pirko
2010-06-01 16:10 ` Stephen Hemminger [this message]
2010-06-02 7:02 ` Jiri Pirko
2010-06-01 16:13 ` Fischer, Anna
2010-06-02 6:50 ` Jiri Pirko
2010-06-02 7:24 ` net: " Jiri Pirko
2010-06-02 7:52 ` [PATCH net-next-2.6] net: replace hooks in __netif_receive_skb V5 Jiri Pirko
2010-06-02 14:11 ` David Miller
2010-06-02 15:07 ` Stephen Hemminger
2010-06-02 15:15 ` Eric Dumazet
2010-06-02 20:43 ` Paul E. McKenney
2010-06-02 16:20 ` Fischer, Anna
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=20100601091004.7885cd8c@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jpirko@redhat.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.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).