Hello,
Thanks for the inputs.. But, if we cannot move back to 2.2.19
and need to stick with 2.4.0 for our own reasons concerning the
work underway, would it be possible to give us a pointer us to
the list of issues related to this problem in the vm, so that we
may attempt to try and get some fixes or workarounds done -
well, they may or may not be accepted into mainstream linux for
various reasons, but we may need to get them fixed to ship our
stuff and may plan to do so..
Any pointers, suggestions, opinions, etc. are most welcome..
Thanks
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
---- On Wed, 4 Apr 2001, Alan Cox (alan@lxorguk.ukuu.org.uk)
wrote:
> > We have been seeing some problems with running nfs
benchmarks
> > at very high loads and were wondering if somebody could show
> > some pointers to where the problem lies.
> > The system is a 2.4.0 kernel on a 6.2 Red at distribution (
so
>
> Use 2.2.19. The 2.4 VM is currently too broken to survive high
I/O
> benchmark
> tests without going silly
>
>
>
-
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/
This archive was generated by hypermail 2b29 : Sun Apr 15 2001 - 21:00:11 EST