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: Fri, 27 Apr 2007 08:46:36 -0700 From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com> To: "Jeff Garzik" <jgarzik@...ox.com>, <hadi@...erus.ca> Cc: "Patrick McHardy" <kaber@...sh.net>, "Stephen Hemminger" <shemminger@...ux-foundation.org>, <netdev@...r.kernel.org>, "cramerj" <cramerj@...el.com>, "Kok, Auke-jan H" <auke-jan.h.kok@...el.com>, "Leech, Christopher" <christopher.leech@...el.com>, <davem@...emloft.net> Subject: RE: [PATCH] IPROUTE: Modify tc for new PRIO multiqueue behavior > jamal wrote: > > Heres the way i see it from a user perspective: > > If a NIC has 3 hardware queues; if that NIC supports strict > priority > > (i.e the prio qdisc) which we already support, there should > be no need > > for the user to really explicitly enable that support. > > It should be transparent to them - because by configuring a multi > > queue prio qdisc (3 bands/queues default), they are already > doing multiqueues. > > Agreed. > > Jeff > Then for clarification, are you asking that I remove the "multiqueue" option to TC and sch_prio, and have it behave the way it did a few patches ago? Thanks, -PJ - 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