lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Apr 2007 11:04:57 +0200 From: Patrick McHardy <kaber@...sh.net> To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com> CC: davem@...emloft.net, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, jgarzik@...ox.com, cramerj <cramerj@...el.com>, "Kok, Auke-jan H" <auke-jan.h.kok@...el.com>, "Leech, Christopher" <christopher.leech@...el.com> Subject: Re: [PATCH] NET: [UPDATED] Multiqueue network device support implementation. Waskiewicz Jr, Peter P wrote: > Thanks Pat for the initial feedback. I can post a set of patches to > e1000 using the new API; I'll try to get them out asap (need to apply to > this kernel tree). Thanks. > However, the PRIO qdisc still uses the priority in > the bands for dequeueing priority, and will feed the queues on the NIC. > The e1000, and any other multiqueue NIC, will schedule Tx based on how > the PRIO qdisc feeds the queues. So the only priority here is the > dequeuing priority from the kernel. The e1000 will use the new API for > starting/stopping the individual queues based on the descriptors > available, much like it does today for the global queue. Packets will only be dequeued from a band if the associated subqueue is active, which moves the decision from prio to the driver, no? What policy does e1000 use for scheduling its internal queues? - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists