summaryrefslogtreecommitdiffstats
path: root/fs/readdir.c
diff options
context:
space:
mode:
authorJoe Korty <joe.korty@ccur.com>2008-10-29 14:22:16 -0700
committerJeff Garzik <jgarzik@redhat.com>2008-11-02 08:30:43 -0500
commitdccd547e2bf2c01a13c967ae03a705338394fad6 (patch)
treed77c9bba24742b4a50bcb27da02e1d128e97af20 /fs/readdir.c
parent0befdb3e0a26a8949063915274e1bec8873c526b (diff)
downloadkernel-crypto-dccd547e2bf2c01a13c967ae03a705338394fad6.tar.gz
kernel-crypto-dccd547e2bf2c01a13c967ae03a705338394fad6.tar.xz
kernel-crypto-dccd547e2bf2c01a13c967ae03a705338394fad6.zip
forcdeth: increase max_interrupt_work
This eliminates the following often-generated warning from my 64 bit Opteron SMP test stand: eth0: too many iterations (6) in nv_nic_irq According to the web, the problem is that the forcedeth driver has a too-low value for max_interrupt_work. Grepping the kernel I see that forcedeth has the second lowest value of all ethernet drivers (ie, 6). Most are in the 20-40 range. So this patch increases this a bit, from 6 to 15 (at 15 forcedeth becomes the driver with third-lowest max_interrupt_work value). My test stand, which used to print out the above warnings repetitively whenever it was under heavy net load, no longer does so. Signed-off-by: Joe Korty <joe.korty@ccur.com> Cc: Ayaz Abdulla <aabdulla@nvidia.com> Cc: Jeff Garzik <jeff@garzik.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Diffstat (limited to 'fs/readdir.c')
0 files changed, 0 insertions, 0 deletions