From: Ed Tomlinson <tomlins@cam.org>
To: William Lee Irwin III <wli@holomorphy.com>,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: linux-mm@kvack.org
Subject: Re: severely bloated slabs
Date: Tue, 30 Jul 2002 20:13:01 -0400 [thread overview]
Message-ID: <200207302013.01958.tomlins@cam.org> (raw)
In-Reply-To: <20020730175339.GF29537@holomorphy.com>
On July 30, 2002 01:53 pm, William Lee Irwin III wrote:
> At some point in the past, I wrote:
> >> 132MB of ZONE_NORMAL on a 16GB i386 box tied up in buffer_head slabs
> >> when all of 3% of it is in use gives me the willies. Periodic slab
> >> pruning anyone? Might be useful in addition to slab-in-lru.
>
> On Tue, Jul 30, 2002 at 10:39:35AM -0700, Martin J. Bligh wrote:
> > As long as we give this up under memory pressure, why does this
> > matter?
>
> Mostly a question of response time and long idle times being a good
> indicator of upcoming workload shifts. I'd say it's behaving as
> designed, but not as desired.
Was this with full rmap + slablru or with a linus kernel? With slablru
I would expect this to happen to some extent. When vm pressure picks
up slablru is fast to free the 'old' slabs... On the other hand, if periodic
prunes are really a good idea, it would be easy to have slablru do them
for us. As it stands now, slablru adds a flag bit to each slab cache telling
slablru to prune the cache instead of just the page encounted. This flag
gets set when we are able to add a page to the lru (when the pagemap_lru
lock is busy). I would not be hard to set this flag under other conditions.
Ed
--
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-07-31 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 17:23 William Lee Irwin III
2002-07-30 17:39 ` Martin J. Bligh
2002-07-30 17:53 ` William Lee Irwin III
2002-07-31 0:13 ` Ed Tomlinson [this message]
2002-08-01 18:15 ` William Lee Irwin III
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=200207302013.01958.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=Martin.Bligh@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.com \
/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