From: Tomasz Kłoczko <[email protected]>
Date: Fri, 16 Sep 2005 14:42:56 +0200 (CEST)
> On Thu, 15 Sep 2005, David S. Miller wrote:
>
> > I wonder if the NFS daemon code needs to have some limits put on
> > how much cpu it consumes handling requests before it gives up the
> > cpu. Perhaps, it has such throttling already, I don't know.
>
> But this not case NFS server but NSF client. During this lookups I observe
> rpciod takes 90-99% time of single processor. Load is between 10 and 20.
After studying some code yesterday, NFS client has the same
exact problem as NFS daemon, namely that if you give it enough
work it will never give up the cpu so that other tasks can
be scheduled.
This is a serious bug, and can easily trigger those soft lockup
messages. Based upon some other reports seen on linux-kernel
and elsewhere, things like the raid1 kernel daemon have a similar
issue as well.
I think you can help things _enormusly_ by turning off SLAB
poisioning, as I said that debugging feature is _VERY_ expensive.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |