Sunay Tripathi wrote: > > I forgot to make one thing clear though - for your kind of NIC > (which has multiple Rx/Tx rings) a partial port to Crossbow > is going to be very harmful. Keep in mind, that unless crossbow > sees all the Rx/Tx rings, it will not use them. Also, dynamic > interrupt blanking has been removed (don't need heuristic based > approach) and replaced by dynamic polling. So unless you expose > interfaces for dynamic polling, you will see huge differences. > > So do enable dynamic polling and then do the things I mentioned > below to give us some data. >
Sunay, Thanks for the info. From looking at the new API I don't believe I can expose my multiple RX/TX rings to crossbow because my traffic steering algorithm is fixed (it's an LFSR hash based on TCP/IP headers) and the current h/w does not support multiple MAC addresses (although I could do this in s/w of course). Is there a way I can take advantage of the polling API without needing to claim levels of virtualization that the h/w does not support? Paul PS: In general I don't think it's a good idea to assume that h/w that can traffic steer based on TCP/IP headers can also steer based on MAC address/VLAN tag.
