All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	shemminger@linux-foundation.org, kaber@trash.net,
	fubar@us.ibm.com, eric.dumazet@gmail.com,
	nicolas.2p.debian@gmail.com, andy@greyhouse.net
Subject: Re: [RFC patch net-next-2.6] net: allow multiple rx_handler registration
Date: Thu, 30 Jun 2011 11:13:59 -0700	[thread overview]
Message-ID: <4E0CBCE7.4060403@candelatech.com> (raw)
In-Reply-To: <1309447009-8898-1-git-send-email-jpirko@redhat.com>

On 06/30/2011 08:16 AM, Jiri Pirko wrote:
> For some net topos it is necessary to have multiple "soft-net-devices"
> hooked on one netdev. For example very common is to have
> eth<->(br+vlan). Vlan is not using rh_handler (yet) but also for example
> macvlan would be useful to have hooked on same netdev as br.
>
> This patch introduces rx_handler list. size struct net_device stays
> intact. Measured performance regression on eth-br topo is ~1% (on received
> pkts generated by pktgen) and on eth-bond topo it is ~0.25%
>
> On br I think that the performance can be brought back maybe by using per-cpu
> variables to store port in rx_path (I must check this)

> +enum rx_handler_prio {
> +	RX_HANDLER_PRIO_BRIDGE,
> +	RX_HANDLER_PRIO_BOND,
> +	RX_HANDLER_PRIO_MACVLAN,
> +};

Maybe add RX_HANDLER_PRIO_LATER, RX_HANDLER_PRIO_FIRST
for other modules that want to link
here, but don't have specific ordering other than before
or after these specific types?

Or maybe start PRIO_BRIDGE at 100, BOND 110, MACVLAN 120
to leave gaps.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  parent reply	other threads:[~2011-06-30 18:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 15:16 [RFC patch net-next-2.6] net: allow multiple rx_handler registration Jiri Pirko
2011-06-30 16:27 ` Stephen Hemminger
2011-06-30 17:22   ` Jiri Pirko
2011-06-30 17:29     ` Ben Greear
2011-06-30 17:32       ` Jiri Pirko
2011-07-01  6:36     ` Michał Mirosław
2011-07-01 14:57       ` Nicolas de Pesloüan
2011-07-01 15:00         ` Jiri Pirko
2011-07-01 15:01         ` Michał Mirosław
2011-07-01 16:45           ` Nicolas de Pesloüan
2011-07-01 16:49             ` Ben Greear
2011-07-01 16:58               ` Nicolas de Pesloüan
2011-07-01 17:08                 ` David Lamparter
2011-07-01 17:50             ` Michał Mirosław
2011-06-30 18:13 ` Ben Greear [this message]
2011-06-30 18:28   ` Jiri Pirko
2011-06-30 18:53     ` Ben Greear
2011-06-30 19:50 ` Nicolas de Pesloüan
2011-07-01  5:45   ` Jiri Pirko
2011-07-01 16:55     ` David Lamparter
2011-07-01 12:48 ` Jiri Pirko

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=4E0CBCE7.4060403@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=fubar@us.ibm.com \
    --cc=jpirko@redhat.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.2p.debian@gmail.com \
    --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 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.