On Thu, Oct 16, 2008 at 1:54 AM, David Miller <davem@xxxxxxxxxxxxx> wrote: > From: <Madhukar.Mythri@xxxxxxxxxxx> > Date: Thu, 16 Oct 2008 13:31:44 +0800 > >> It differs for each driver. Generally, for intel drivers, the driver >> version says whether its NAPI-mode or not. We can know this by >> command "modinfo e1000 |grep NAPI" . Or else, 'ethtool -i >> <interface name>' (where interface-name, should be intel-device >> interface-name like: eth0 or eth1..). >> >> Where as for Broadcom, the driver version, doesn't say, whether its >> NAPI-mode or not. I don't' know how to identify this for Broadcom? > > NAPI is unconditionally on, always, for all Broadcom drivers. > > In fact we want all drivers to unconditionally use NAPI > and not allow this to be configurable. It's a very > inconsistent user experience, make for more code to > validate, more situations to test, and more bugs. I agree with all of the above reasons for not having a switch/option, but at one point, I thought that NAPI and NETPOLL/NETCONSOLE didn't really like each other. Has this been resolved and is it just my understanding that is incorrect/out of date? Paul. -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
