Issue

• GRO is disabled but we still see back traces in the messages file indicating that it called the GRO routines.
• One common thing with all these stack traces is the presence of the Emulex driver's GRO receive functions. Seems odd to me that in a system where GRO has been disabled that the Emulex driver is serving up ingress skbs with a size that supports over MTU sized frames and that functions that appear to be related to GRO are always in the call stack. If GRO is not enabled, why would the skb's truesize be larger that the size of an standard ethernet frame and why would the GRO functions be in the call stack?