[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0199E0D51A61344794750DC57738F58E70B1836BED@GVW1118EXC.americas.hpqcorp.net>
Date: Wed, 2 Jun 2010 16:20:49 +0000
From: "Fischer, Anna" <anna.fischer@...com>
To: Jiri Pirko <jpirko@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"kaber@...sh.net" <kaber@...sh.net>,
"eric.dumazet@...il.com" <eric.dumazet@...il.com>,
"shemminger@...tta.com" <shemminger@...tta.com>
Subject: RE: [PATCH net-next-2.6] net: replace hooks in __netif_receive_skb
V5
> Subject: [PATCH net-next-2.6] net: replace hooks in __netif_receive_skb
> V5
>
> What this patch does is it removes two receive frame hooks (for bridge
> and for
> macvlan) from __netif_receive_skb. These are replaced them with a single
> hook for both. It only supports one hook per device because it makes no
> sense to do bridging and macvlan on the same device.
>
> Then a network driver (of virtual netdev like macvlan or bridge) can
> register
> an rx_handler for needed net device.
>
> Signed-off-by: Jiri Pirko <jpirko@...hat.com>
> Signed-off-by: Stephen Hemminger <shemminger@...tta.com>
I would like to see this being accepted. As mentioned before I would love to be able to support multiple receive frame hooks per device, but I think this is a good start.
I think especially with virtualization coming into Linux and new network virtualization approaches being developed it would be nice to have a more generic function for packet receive handlers to hook into the network stack more cleanly. Current approaches rely on 'misusing' the bridging hook into the kernel, because the packet 'sniffing' hooks (via dev_pack_add()) do not give enough control over packet processing.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists