| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20130322.101139.1942128058226201237.davem@davemloft.net> Date: Fri, 22 Mar 2013 10:11:39 -0400 (EDT) From: David Miller <davem@...emloft.net> To: afleming@...escale.com Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [PATCH] net: Add support for handling queueing in hardware From: Andy Fleming <afleming@...escale.com> Date: Wed, 13 Jul 2011 08:52:04 -0500 > The QDisc code does a bunch of locking which is unnecessary if > you have hardware which handles all of the queueing. Add > support for this, and skip over all of the queueing code if > the feature is enabled on a given device, which breaks QDisc > support on dpaa_eth, and also coopts the FCOE feature bit. > > Signed-off-by: Andy Fleming <afleming@...escale.com> > Signed-off-by: Ben Collins <ben.c@...vergy.com> Sorry, no. If we are going to support something like this then there needs to be full coordination, configuration wise, so that if we enable a qdisc that the hardware supports we submit it directly, but if we enable a qdisc the HW does not support, we still use the software qdisc. This also means that we need to have a way to determine if the qdisc configuration exceeds that parametorial limits of the device's HW capabilities, and fallback to software qdisc in those cases too. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists