From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Gerald Schaefer <gerald.schaefer@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Dave Hansen <haveblue@us.ibm.com>
Subject: Re: [PATCH] Make CONFIG_MIGRATION available for s390
Date: Mon, 07 Jul 2008 19:24:06 +0900 [thread overview]
Message-ID: <20080707185433.5A5D.E1E9C6FF@jp.fujitsu.com> (raw)
In-Reply-To: <20080707090635.GA6797@shadowen.org>
> > Index: linux-2.6/include/linux/migrate.h
> > ===================================================================
> > --- linux-2.6.orig/include/linux/migrate.h
> > +++ linux-2.6/include/linux/migrate.h
> > @@ -13,6 +13,7 @@ static inline int vma_migratable(struct
> > {
> > if (vma->vm_flags & (VM_IO|VM_HUGETLB|VM_PFNMAP|VM_RESERVED))
> > return 0;
> > +#ifdef CONFIG_NUMA
> > /*
> > * Migration allocates pages in the highest zone. If we cannot
> > * do so then migration (at least from node to node) is not
> > @@ -22,6 +23,7 @@ static inline int vma_migratable(struct
> > gfp_zone(mapping_gfp_mask(vma->vm_file->f_mapping))
> > < policy_zone)
> > return 0;
> > +#endif
>
> include/linux/mempolicy.h already has a !NUMA section could we not just
> define policy_zone as 0 in that and leave this code unconditionally
> compiled? Perhaps also adding a NUMA_BUILD && to this 'if' should that
> be clearer.
>
Ah, yes. It's better. :-)
> But this does make me feel uneasy. Are we really saying all memory on
> an s390 is migratable. That seems unlikely. As I understand the NUMA
> case, we only allow migration of memory in the last zone (last two if we
> have a MOVABLE zone) why are things different just because we have a
> single 'node'. Hmmm. I suspect strongly that something is missnamed
> more than there is a problem.
If my understanding is correct, even if this policy_zone check is removed,
page isolation will just fail due to some busy pages.
In hotplug case, it means giving up of hotremoving,
and kernel must be rollback to make same condition of previous
starting offline_pages().
This check means just "early" check, but not so effective for hotremoving,
I think....
Thanks.
--
Yasunori Goto
--
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:[~2008-07-07 10:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 14:35 [PATCH] Make CONFIG_MIGRATION available for s390, " Gerald Schaefer
2008-07-07 6:22 ` Yasunori Goto
2008-07-07 9:16 ` Andy Whitcroft
2008-07-07 10:24 ` Yasunori Goto [this message]
2008-07-07 16:41 ` Gerald Schaefer
2008-07-07 16:53 ` Christoph Lameter
2008-07-07 15:09 ` Christoph Lameter
2008-07-07 17:28 ` Gerald Schaefer
2008-07-07 17:38 ` Christoph Lameter
2008-07-07 18:25 ` Gerald Schaefer
2008-07-07 18:32 ` Christoph Lameter
2008-07-08 10:50 ` [PATCH] Make CONFIG_MIGRATION available w/o NUMA Gerald Schaefer
2008-07-08 13:35 ` Christoph Lameter
2008-07-08 13:47 ` Christoph Lameter
2008-07-11 13:05 ` Gerald Schaefer
-- strict thread matches above, loose matches on Subject: below --
2008-07-04 14:58 [PATCH] Make CONFIG_MIGRATION available for s390, [PATCH] Make CONFIG_MIGRATION available for s390 Gerald Schaefer
2008-07-05 4:02 ` KAMEZAWA Hiroyuki
2008-07-05 6:14 ` Yasunori Goto
2008-07-06 14:30 ` Gerald Schaefer
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=20080707185433.5A5D.E1E9C6FF@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=schwidefsky@de.ibm.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