Paul Durrant wrote:
> On 19/09/2007, Erik Nordmark <[EMAIL PROTECTED]> wrote:
>
>> If the GLD framework causes msgdsize to be called multiple times for the
>> same packet, then it might make sense to expand on the GLD interfaces to
>> pass the packet length along.
>>
>>
>
> If the nemo TX entry point it only ever called with one packet at a
> time then clearly, adding the packet length as an argument would be
> easy to do; otherwise you're looking at attaching packet metadata to
> the mblk and that's a whole other can of worms.
>
> BTW; if the nemo tx entry point really *is* only ever called with one
> packet at a time then the drivers TX code could be significantly
> simplified (since they have to assume a packet chain at the moment).
>
I guess the outer loop could be moved up the stack slightly, but as I
understood it, part of the motivation for doing this is to help amortize
the per-call overheads (e.g. acquiring locks, etc.) Unfortunately, the
common approach I've seen in device drivers fails to realize any gains
with this.
The other time I think that a packet chain may come down is in response
to mac_tx_update(). Although, to be fair, I've not actually *verified*
that.
-- Garrett
> Paul
>
>
_______________________________________________
networking-discuss mailing list
[email protected]
