From: Minchan Kim <minchan.kim@gmail.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, npiggin@kernel.dk,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
kosaki.motohiro@jp.fujitsu.com, cl@linux.com,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH 2/3] Refactor zone_reclaim (v2)
Date: Tue, 14 Dec 2010 19:01:26 +0900 [thread overview]
Message-ID: <AANLkTimeecObDMQMbWzNhL1mE+UT9D3o1WWS4bmxtR4U@mail.gmail.com> (raw)
In-Reply-To: <20101210143018.29934.11893.stgit@localhost6.localdomain6>
Hi Balbir,
On Fri, Dec 10, 2010 at 11:31 PM, Balbir Singh
<balbir@linux.vnet.ibm.com> wrote:
> Move reusable functionality outside of zone_reclaim.
> Make zone_reclaim_unmapped_pages modular
>
> Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
> ---
> mm/vmscan.c | 35 +++++++++++++++++++++++------------
> 1 files changed, 23 insertions(+), 12 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index e841cae..4e2ad05 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -2815,6 +2815,27 @@ static long zone_pagecache_reclaimable(struct zone *zone)
> }
>
> /*
> + * Helper function to reclaim unmapped pages, we might add something
> + * similar to this for slab cache as well. Currently this function
> + * is shared with __zone_reclaim()
> + */
> +static inline void
> +zone_reclaim_unmapped_pages(struct zone *zone, struct scan_control *sc,
> + unsigned long nr_pages)
> +{
> + int priority;
> + /*
> + * Free memory by calling shrink zone with increasing
> + * priorities until we have enough memory freed.
> + */
> + priority = ZONE_RECLAIM_PRIORITY;
> + do {
> + shrink_zone(priority, zone, sc);
> + priority--;
> + } while (priority >= 0 && sc->nr_reclaimed < nr_pages);
> +}
As I said previous version, zone_reclaim_unmapped_pages doesn't have
any functions related to reclaim unmapped pages.
The function name is rather strange.
It would be better to add scan_control setup in function inner to
reclaim only unmapped pages.
--
Kind regards,
Minchan Kim
--
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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-12-14 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 14:29 [PATCH 0/3] Provide unmapped page cache control (v2) Balbir Singh
2010-12-10 14:30 ` [PATCH 1/3] Move zone_reclaim() outside of CONFIG_NUMA (v2) Balbir Singh
2010-12-10 14:31 ` [PATCH 2/3] Refactor zone_reclaim (v2) Balbir Singh
2010-12-14 10:01 ` Minchan Kim [this message]
2010-12-14 11:45 ` Balbir Singh
2010-12-14 22:38 ` Minchan Kim
2010-12-22 6:10 ` Balbir Singh
2010-12-15 6:45 ` Balbir Singh
2010-12-10 14:32 ` [PATCH 3/3] Provide control over unmapped pages (v2) Balbir Singh
2010-12-14 11:02 ` Minchan Kim
2010-12-23 8:33 ` Balbir Singh
2010-12-24 0:52 ` Minchan Kim
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=AANLkTimeecObDMQMbWzNhL1mE+UT9D3o1WWS4bmxtR4U@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@kernel.dk \
/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).