What is the best way to disable it? I know I can do an ethtool -K ethx gro
off, but is there a better way to disable it? Ideally something that keeps
it from coming on before I can turn it off.

Thanks,
Scott

On Wed, Dec 23, 2009 at 5:19 PM, Tantilov, Emil S <emil.s.tanti...@intel.com
> wrote:

> Ed Ravin wrote:
> > On Wed, Dec 23, 2009 at 02:02:19PM -0700, Tantilov, Emil S wrote:
> >> There were issues with GRO and routing in the initial implementations
> >> (2.6.29 I think was where GRO was introduced). Try newer kernel
> >> (2.6.32.x) and it should work.
> >
> > Emil - what is the earliest kernel that has a working GRO?  I'm using
> > a distribution with a 2.6.31 kernel, and I'm hoping I won't have to
> > rebuild it.
> >
> > Thanks,
> >
> >       -- Ed
>
> Not sure. The majority of the work was done in 2.6.29/30 I think, so you
> may be OK. If you have issues just disable it.
>
> Thanks,
> Emil
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> E1000-devel mailing list
> E1000-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel

Reply via email to