From: Kapish K <kapish@ureach.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: nfs performance at high loads
Date: Mon, 9 Apr 2001 11:48:23 -0400 [thread overview]
Message-ID: <200104091548.LAA05492@www22.ureach.com> (raw)
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
>
>
>
next reply other threads:[~2001-04-09 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 15:48 Kapish K [this message]
2001-04-09 19:57 ` Re: nfs performance at high loads Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-04-25 19:05 Kapish K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200104091548.LAA05492@www22.ureach.com \
--to=kapish@ureach.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox