Andrew Gallatin wrote: > Nitin Hande wrote: >> Andrew Gallatin wrote: > >>> When looking at this, I noticed mac_tx_serializer_mode(). Am I reading >>> this right, in that is serializes a single queue? That seems lacking, >>> compared to the nxge_serialize stuff it replaces. >> >> Yes. This part was done for nxge and as far as I remember recent >> performance of this scheme was very close to that of the previous >> scheme. I think Gopi can comment more on this. What part do you >> think is missing here ? > > Perhaps I'm missing something.. Doesn't nxge support multiple TX rings?
yes. > If so, does the existing serialization serialize all traffic to a > single ring, or is mac_tx_serializer_mode() applied after > mac_tx_fanout_mode()? Neither. Cutting and pasting from my previous reply: ... mac_tx_serializer_mode() is used when you have a single Tx ring. nxge would not use that mode. It exposes multiple Tx rings. When multiple Tx rings are present, mac_tx_fanout_mode() is used. mac_tx_fanout_mode() can operate in serialized mode also in which case there would be a serializer (soft ring) for each Tx ring. Nxge uses that mode. ... -krgopi > > I had thought the original nxge serializer serialized each TX ring > separately in nxge. The fork I made of it for myri10ge certainly > works that way. > > Drew > > > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss --
