From: Wu Fengguang <fengguang.wu@intel.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Bob Liu <lliubbo@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [PATCH] do_migrate_range: avoid failure as much as possible
Date: Mon, 25 Oct 2010 11:06:34 +0800 [thread overview]
Message-ID: <20101025030634.GA15386@localhost> (raw)
In-Reply-To: <20101025025703.GA13858@localhost>
On Mon, Oct 25, 2010 at 10:57:03AM +0800, Wu Fengguang wrote:
> On Mon, Oct 25, 2010 at 10:40:17AM +0800, KAMEZAWA Hiroyuki wrote:
> > On Mon, 25 Oct 2010 10:47:31 +0800
> > Bob Liu <lliubbo@gmail.com> wrote:
> >
> > > It's normal for isolate_lru_page() to fail at times. The failures are
> > > typically temporal and may well go away when offline_pages() retries
> > > the call. So it seems more reasonable to migrate as much as possible
> > > to increase the chance of complete success in next retry.
> > >
> > > This patch remove page_count() check and remove putback_lru_pages() and
> > > call migrate_pages() regardless of not_managed to reduce failure as much
> > > as possible.
> > >
> > > Signed-off-by: Bob Liu <lliubbo@gmail.com>
> >
> > -EBUSY should be returned.
>
> It does return -EBUSY when ALL pages cannot be isolated from LRU (or
> is non-LRU pages at all). That means offline_pages() will repeat calls
> to do_migrate_range() as fast as possible as long as it can make
> progress.
>
> Is that behavior good enough? It does need some comment for this
> non-obvious return value.
>
> btw, the caller side code can be simplified (no behavior change).
>
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index dd186c1..606d358 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -848,17 +848,13 @@ repeat:
> pfn = scan_lru_pages(start_pfn, end_pfn);
> if (pfn) { /* We have page on LRU */
> ret = do_migrate_range(pfn, end_pfn);
> - if (!ret) {
> - drain = 1;
> - goto repeat;
> - } else {
> - if (ret < 0)
> - if (--retry_max == 0)
> - goto failed_removal;
> + if (ret < 0) {
> + if (--retry_max <= 0)
> + goto failed_removal;
> yield();
> - drain = 1;
> - goto repeat;
> }
> + drain = 1;
> + goto repeat;
> }
> /* drain all zone's lru pagevec, this is asyncronous... */
> lru_add_drain_all();
And it seems the costly drain operations could be avoided as long as
it's making progress. What do you think?
--- linux-next.orig/mm/memory_hotplug.c 2010-10-25 11:04:05.000000000 +0800
+++ linux-next/mm/memory_hotplug.c 2010-10-25 11:04:22.000000000 +0800
@@ -852,8 +852,8 @@ repeat:
if (--retry_max <= 0)
goto failed_removal;
yield();
+ drain = 1;
}
- drain = 1;
goto repeat;
}
/* drain all zone's lru pagevec, this is asyncronous... */
--
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>
next prev parent reply other threads:[~2010-10-25 3:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 2:47 [PATCH] do_migrate_range: avoid failure as much as possible Bob Liu
2010-10-25 2:40 ` KAMEZAWA Hiroyuki
2010-10-25 2:57 ` Wu Fengguang
2010-10-25 3:05 ` KAMEZAWA Hiroyuki
2010-10-25 3:09 ` KAMEZAWA Hiroyuki
2010-10-25 3:48 ` Wu Fengguang
2010-10-25 3:48 ` KAMEZAWA Hiroyuki
2010-10-25 4:06 ` Wu Fengguang
2010-10-25 4:34 ` KAMEZAWA Hiroyuki
2010-10-25 4:55 ` Wu Fengguang
2010-10-25 4:00 ` Bob Liu
2010-10-25 3:28 ` Wu Fengguang
2010-10-25 3:50 ` KAMEZAWA Hiroyuki
2010-10-25 3:06 ` Wu Fengguang [this message]
2010-10-25 3:16 ` Wu Fengguang
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=20101025030634.GA15386@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=mel@csn.ul.ie \
/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).