From: Dave Chinner <david@fromorbit.com>
To: "kautuk.c @samsung.com" <consul.kautuk@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Minchan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Why isn't shrink_slab more zone oriented ?
Date: Wed, 28 Sep 2011 10:04:29 +1000 [thread overview]
Message-ID: <20110928000429.GD3159@dastard> (raw)
In-Reply-To: <CAFPAmTRHFOT+tc=J-=jTBpvi8ksnp6H32UsEwptrrv=hagjUsA@mail.gmail.com>
On Mon, Sep 26, 2011 at 05:21:12PM +0530, kautuk.c @samsung.com wrote:
> Hi,
>
> I was going through the do_try_to_free_pages(), balance_pgdat(),
> __zone_reclaim()
> functions and I see that shrink_zone and shrink_slab are called for each zone.
>
> But, shrink_slab() doesn't seem to bother about the zone from where it
> is freeing
> memory.
Work is in progress to do this.
http://lwn.net/Articles/456071/
Dirty slab objects are currently not tracked in a manner that makes
per-zone reclaim efficient to do, os that needs to be corrected
first. Once we have generic per-zone LRU infrastructure, then we
can easily push zone reclaim hints down into the shrinkers for them
to scan the appropriate LRU....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-09-28 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 11:51 Why isn't shrink_slab more zone oriented ? kautuk.c @samsung.com
2011-09-28 0:04 ` Dave Chinner [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=20110928000429.GD3159@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=consul.kautuk@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).