Le mercredi 15 septembre 2010 à 23:38 -0700, David Miller a écrit : > From: Stephen Hemminger <[email protected]> > Date: Wed, 15 Sep 2010 23:21:25 -0700 > > > I think it is more complex than that. GRO is tied to NAPI, > > and bridge/bond don't use NAPI directly. They use netif_rx() for receiving > > because layered drivers can't directly up call because of possible > > issues with stack depth. > > > > To get GRO working for netif_rx case, > > the logic in process_backlog would have to change. > > But this queue is processing packets from multiple devices so > > it is not clear if GRO could be used. > > Bonding's un-layering on RX is done in the normal netif_receive_skb() > control flow. > > And bridging only uses netif_rx for multicast replication.
Yes, bonding case should be easy, I'll take a look today. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
