From: Stephan von Krawczynski <skraw@ithnet.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Strange dcache memory pressure when highmem enabled
Date: Wed, 15 Oct 2003 11:58:37 +0200 [thread overview]
Message-ID: <20031015115837.63444093.skraw@ithnet.com> (raw)
In-Reply-To: <16268.57123.661746.500616@notabene.cse.unsw.edu.au>
On Wed, 15 Oct 2003 15:46:11 +1000
Neil Brown <neilb@cse.unsw.edu.au> wrote:
> On Tuesday October 14, akpm@osdl.org wrote:
> > Neil Brown <neilb@cse.unsw.edu.au> wrote:
> > >
> > > I noticed that shrink_caches calls shrink_dcache_memory independant
> > > of the classzone that is being shrunk. So if we are trying to
> > > shrink ZONE_HIGHMEM, the dentry_cache is shrunk, even though the
> > > dentry_cache doesn't live in highmem. However I'm not sure if I have
> > > understood the classzones well enough for that observation even to
> > > make sense.
> >
> > Makes heaps of sense. Here's an instabackport of what we did in
> > 2.6:
>
> Hey!!! That's what I call *Service*.
>
> I'll give it a try tomorrow (let the poor students get a feeling of
> stability first before I start changing things again :-)
>
> > + if (classzone - classzone->zone_pgdat->node_zones <
> > + ZONE_HIGHMEM) {
>
> That's the bit I was missing. I feel that once I fully understand
> that, I will be a long way towards understanding the zones memory
> management :-)
>
> NeilBrown
I have another simple advice for you: use the latest 2.4.23-pre. I think I saw
your problem and it seems solved.
Regards,
Stephan
next prev parent reply other threads:[~2003-10-15 9:58 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
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 [this message]
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=20031015115837.63444093.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=akpm@osdl.org \
--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