Messages in this thread |  | | Subject | Re: 2.6 must-fix list, v2 | From | Trond Myklebust <> | Date | 13 May 2003 13:36:14 +0200 |
| |
>>>>> " " == Andrew Morton <akpm@digeo.com> writes:
> - NFS client gets an OOM deadlock. > - Some fixes exist in -mm. Seem to mostly work. > - NFS client runs very slowly consuming 100% CPU under heavy > writeout. > - Unsubtle fix exists in -mm. (Looks like it's fixed anyway).
<snip>
> - davej: NFS seems to have a really bad time for some people. (Including > myself on one testbox). The common factor seems to be a high > spec client torturing an underpowered NFS server with lots of > IO. (fsx/fsstress etc show this up). Lots of "NFS server > cheating" messages get dumped, and a whole lot of bogus > packets start appearing. They look severely corrupted, (they > even crashed ethereal once 8-)
Could people please test these items out again using the latest Bitkeeper release? I believe I've addressed all these issues with the patches that have gone to Linus in the last 2-3 weeks.
Cheers, Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |