I'm running a system with multiple e1000 devices, using 9KB jumbo frames. I'm running a modified 2.6.10 with e1000 driver 5.5.4-k2.
I'm a bit concerned about the behaviour of this driver with jumbo frames. We ask for 9KB. The driver then bumps that up to a power-of-two, so it calls dev_alloc_skb(16384). That then bumps it up a bit to allow for its own overhead, so it appears that we end up asking for 32KB of physically contiguous memory for every packet coming in. Ouch.
Add to that the fact that this version of the driver doesn't do copybreak, and it means that after we're up for a few days it starts complaining about not being able to allocate buffers.
Anyone have any suggestions on how to improve this? Upgrading kernels isn't an option. I could port back the copybreak stuff fairly easily.
Back in 2.4 some of the drivers used to retry buffer allocations using GFP_KERNEL once interrupts were reenabled. I don't see many of them doing that anymore--would there be any benefit to that?
Thanks, Chris - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
