> -----Original Message----- > From: Eric W. Biederman [mailto:[EMAIL PROTECTED]
> How do you classify channels? Multiple rx steering criterias are available, for example tcp tuple (or subset) hash, direct tcp tuple (or subset) match, MAC address, pkt size, vlan tag, QOS bits, etc. > > If your channels can map directly to the VAN Jacobsen > channels then when the kernel starts using them, it sounds > like the ideal strategy is to use the current NAPI algorithm > of disabling interrupts (on a per channel basis (assuming > MSI-X here) until that channel gets caught up Then enable > interrupts again. Right. Interrupt moderation is done on per channel basis. The only addition to the current NAPI mechanism I'd like to see is to have NAPI setting desired interrupt rate (once interrupts are ON), rather than use an interrupt per packet or a driver default. Arguably, NAPI can figure out desired interrupt rate a bit better than a driver can. > > I wonder if someone could make that the default policy in their NICs? Some NICs can support this today. If there is a consensus on a channel-aware NIC driver interface (including interrupt mgmt per channel), this will become a default NIC implementation. Over time, NIC development is always driven by the OS/stack requirements. > > Eric > - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
