From: Glauber Costa <glommer@parallels.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-mm@kvack.org, cgroups@vger.kernel.org,
Dave Shrinnker <david@fromorbit.com>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH v2 0/2] slightly change shrinker behaviour for very small object sets
Date: Mon, 14 Jan 2013 11:58:36 -0800 [thread overview]
Message-ID: <50F4636C.6030908@parallels.com> (raw)
In-Reply-To: <1356086810-6950-1-git-send-email-glommer@parallels.com>
On 12/21/2012 02:46 AM, Glauber Costa wrote:
> Hi,
>
> * v2: fix sysctl_vfs_cache_pressure for all users.
>
> I've recently noticed some glitches in the object shrinker mechanism when a
> very small number of objects is used. Those situations are theoretically
> possible, albeit unlikely. But although it may feel like it is purely
> theoretical, they can become common in environments with many small containers
> (cgroups) in a box.
>
> Those patches came from some experimentation I am doing with targetted-shrinking
> for kmem-limited memory cgroups (Dave Shrinnker is already aware of such work).
> In such scenarios, one can set the available memory to very low limits, and it
> becomes easy to see this.
>
>
Hi,
Who should pick this one up?
Are there any comments aside from Dave's Reviewed-by tag that I wrongly
transcribed?
Thanks!
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-01-14 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 10:46 Glauber Costa
2012-12-21 10:46 ` [PATCH v2 1/2] super: fix calculation of shrinkable objects for small numbers Glauber Costa
2012-12-21 11:08 ` Carlos Maiolino
2012-12-21 10:46 ` [PATCH v2 2/2] vmscan: take at least one pass with shrinkers Glauber Costa
2012-12-21 11:10 ` Carlos Maiolino
2012-12-22 23:53 ` Dave Chinner
2012-12-22 23:56 ` Glauber Costa
2013-01-14 19:58 ` Glauber Costa [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=50F4636C.6030908@parallels.com \
--to=glommer@parallels.com \
--cc=cgroups@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
/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