From: "kautuk.c @samsung.com" <consul.kautuk@gmail.com>
To: 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>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Why isn't shrink_slab more zone oriented ?
Date: Mon, 26 Sep 2011 17:21:12 +0530 [thread overview]
Message-ID: <CAFPAmTRHFOT+tc=J-=jTBpvi8ksnp6H32UsEwptrrv=hagjUsA@mail.gmail.com> (raw)
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.
My questions are:
- Will this be a strain on the direct/indirect reclamation algorithm ?
The loops involved expects to free something from that particular zone.
shrink_slab might take more time than is required to free up pages from that
particular zone which might not be optimal.
Am I right about this conclusion ?
- If the above is correct, then is there any work happening on this
front, i.e., to
make shrink_slab functionality and the shrinker callbacks more zone-centric ?
Are there any patches that I could look at or download from
somewhere for this ?
- Are there any other considerations to be careful of for making
shrink_slab more
zone centric ? Can there be other side effects that affects
performance if the
shrink_slab and shrinker callbacks are made to free pages only from
a particular
zone ?
Thanks,
Kautuk.
--
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>
next reply other threads:[~2011-09-26 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 11:51 kautuk.c @samsung.com [this message]
2011-09-28 0:04 ` Dave Chinner
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='CAFPAmTRHFOT+tc=J-=jTBpvi8ksnp6H32UsEwptrrv=hagjUsA@mail.gmail.com' \
--to=consul.kautuk@gmail.com \
--cc=akpm@linux-foundation.org \
--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