From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange dcache memory pressure when highmem enabled
Date: Tue, 14 Oct 2003 22:05:45 -0700 [thread overview]
Message-ID: <1066194345.16993.12.camel@camp4.serpentine.com> (raw)
In-Reply-To: <16268.52761.907998.436272@notabene.cse.unsw.edu.au>
On Tue, 2003-10-14 at 21:33, Neil Brown wrote:
> I have a fairly busy NFS server which has been having performance
> problems lately. I have managed to work around the problems, but
> would really like to get the root problem fixed.
Funny, I have seen exactly the same problem, though with a Red Hat
2.4.20 kernel, rather than a vanilla-ish 2.4.
I have a few thousand more entries in my dentry cache on a 2G machine,
but it's still a pitiful number.
What workarounds did you find?
<b
next prev parent reply other threads:[~2003-10-15 5:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 4:33 Strange dcache memory pressure when highmem enabled Neil Brown
2003-10-15 5:05 ` Bryan O'Sullivan [this message]
2003-10-15 5:10 ` Neil Brown
2003-10-15 5:43 ` Andrew Morton
2003-10-15 5:46 ` Neil Brown
2003-10-15 9:58 ` Stephan von Krawczynski
2003-10-16 13:33 ` Andrea Arcangeli
2003-10-21 22:57 ` Neil Brown
2003-10-22 1:03 ` Andrea Arcangeli
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=1066194345.16993.12.camel@camp4.serpentine.com \
--to=bos@serpentine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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