On Wed, Aug 06, 2008 at 11:07:41PM -0700, David Miller wrote:

quoted

quoted

I would start hacking on this beast but I haven't yet come up with
a clean way to share a lot of code with the existing sw GSO engine.
That's the key to implementing this properly.

I think it's doable.  We could refactor the software GSO so that
it spits out one fragment at a time and the output could either
be written to some memory provided by the caller or fed through
a callback.

BTW, loner term we should start thinking about breaking the 64K
barrier.

So I had this idea.  My goal is to minimize the number of DMA
mappings the driver has to make.

FWIW, this wouldn't make much of a difference in my case..

Another nice aspect of this idea is that we can make the existing GSO
code just build this funny "TSO plus hidden headers" SKB, and then do
the by-hand unpacking into new SKB chunks that we will let smart
drivers do directly into their TX rings.

..but I'm pretty sure that this would.