Andrew,
Andrew Gallatin wrote:
Let me rephrase the question. If the minumum frame size for ethernet
is 60 bytes, and our device does not pad frames to 60 bytes by itself,
will filling in 60 cause the stack to do the padding for me?
No, that won't cause any padding to be done for you.
> As of Solaris Nevada build 30, we provided the softrings mechanism which
> is implemented at the Nemo layer, and optionally performs load spreading
> to multiple threads in software, when the NIC does not support multiple
> hardware rings. We need to write a full description of this mechanism,
> but if you can find the implementation at:
>
> http://cvs.opensolaris.org/source/xref/on/usr/src/uts/common/io/dls/dls_soft_ring.c
Cool. From the comments in that file, it sounds like this also
preserves locality. Is this slated for a merge into a shipping
Solaris10 version? Eg, I know some version of Nemo is in 10U1. Are
softrings in 10U1?
Softrings did not make S10U1 but should be in the next update.
One thing I omitted yesterday was that I really like how m_tx()
handles chained packets. Depending on how far up the stack the chain
can be built, it sounds almost like a poor man's TSO. it will be
interesting to compare our TSO CPU utilization on linux with Nemo on
Solaris..
Yes, it can provide some similar savings, but for now it really kicks in
only in the flow controlled case. However we are also adding true LSO
capabilities to Nemo.
Nicolas.
--
Nicolas Droux, Solaris Networking
Sun Microsystems, Inc. http://blogs.sun.com/droux
_______________________________________________
networking-discuss mailing list
[email protected]
