From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm mailing list <linux-mm@kvack.org>
Subject: Re: ZONE_NORMAL exhaustion (dcache slab)
Date: Mon, 21 Oct 2002 23:21:02 -0700 [thread overview]
Message-ID: <3DB4EE4E.88311B7B@digeo.com> (raw)
In-Reply-To: <2629107186.1035240598@[10.10.2.3]>
"Martin J. Bligh" wrote:
>
> > Oh it's reproduceable OK. Just run
> >
> > make-teeny-files 7 7
>
> Excellent - thanks for that ... will try it.
When it goes stupid, you can then run and kill some big memory-hog
to force reclaim of lots of highmem pages. Once you've done that,
you can watch the inode cache fall away as the inodes which used
to have pagecache become reclaimable.
> > Maybe you didn't cat /dev/sda2 for long enough?
>
> Well, it's a multi-gigabyte partition. IIRC, I just ran it until
> it died with "input/output error" ... which I assumed at the time
> was the end of the partition, but it should be able to find that
> without error, so maybe it just ran out of ZONE_NORMAL ;-)
Oh. Well it should have just hit eof. Maybe you have a dud
sector and it terminated early.
> > Perhaps we need to multiply the slab cache scanning pressure by the
> > slab occupancy. That's simple to do.
>
> That'd make a lot of sense (to me, at least). I presume you mean
> occupancy on a per-slab basis, not global.
It's already performing slab cache scanning proportional to
the size of the slab. Multiplied by the rate of page scanning.
But I'm thinking that this linear pressure isn't right
at either end of the scale, so it needs to become nonlinear - even
less pressure when there's little slab, and more pressure when
there's a lot. So multiply the slab scanning ratio by
amount_of_slab/amount_of_normal_zone. Maybe.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-22 6:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 20:40 Martin J. Bligh
2002-10-21 21:13 ` Andrew Morton
2002-10-21 21:16 ` Martin J. Bligh
2002-10-21 21:33 ` Andrew Morton
2002-10-21 21:33 ` Martin J. Bligh
2002-10-21 21:49 ` Andrew Morton
2002-10-21 22:30 ` Rik van Riel
2002-10-21 22:53 ` Andrew Morton
2002-10-22 0:31 ` Martin J. Bligh
2002-10-22 3:39 ` Andrew Morton
2002-10-22 3:53 ` Martin J. Bligh
2002-10-22 4:20 ` Andrew Morton
2002-10-22 5:49 ` Martin J. Bligh
2002-10-22 6:21 ` Andrew Morton [this message]
2002-10-22 16:13 ` Martin J. Bligh
2002-10-24 11:35 ` Ed Tomlinson
2002-10-24 14:28 ` Martin J. Bligh
2002-10-22 16:33 ` Rik van Riel
2002-10-22 17:05 ` Andrew Morton
2002-10-22 16:21 ` Dipankar Sarma
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=3DB4EE4E.88311B7B@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=riel@conectiva.com.br \
/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