From: William Lee Irwin III <wli@holomorphy.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>, linux-mm@kvack.org
Subject: Re: severely bloated slabs
Date: Thu, 1 Aug 2002 11:15:17 -0700 [thread overview]
Message-ID: <20020801181517.GR29537@holomorphy.com> (raw)
In-Reply-To: <200207302013.01958.tomlins@cam.org>
On July 30, 2002 01:53 pm, William Lee Irwin III wrote:
>> 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.
On Tue, Jul 30, 2002 at 08:13:01PM -0400, Ed Tomlinson wrote:
> 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.
Sounds reasonable, not sure what the general consensus is on periodic
prunes, though. I'm mostly thinking of the desktop workload for this
one, as servers are probably not going to really care. But I'm not a good
testcase for this one as even my "desktop" usage patterns are atypical.
Cheers,
Bill
--
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/
prev parent reply other threads:[~2002-08-01 18:15 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
2002-08-01 18:15 ` William Lee Irwin III [this message]
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=20020801181517.GR29537@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=tomlins@cam.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