From: Andy Fleming <aflem...@freescale.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 <aflem...@freescale.com> > Signed-off-by: Ben Collins <be...@servergy.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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/