All of lore.kernel.org
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani@hp.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	jiang.liu@huawei.com, wujianguo@huawei.com, wency@cn.fujitsu.com,
	laijs@cn.fujitsu.com, linfeng@cn.fujitsu.com, yinghai@kernel.org,
	isimatu.yasuaki@jp.fujitsu.com, rob@landley.net,
	kosaki.motohiro@jp.fujitsu.com, minchan.kim@gmail.com,
	mgorman@suse.de, rientjes@google.com, guz.fnst@cn.fujitsu.com,
	rusty@rustcorp.com.au, lliubbo@gmail.com,
	jaegeuk.hanse@gmail.com, tony.luck@intel.com,
	glommer@parallels.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option
Date: Mon, 14 Jan 2013 17:05:01 -0700	[thread overview]
Message-ID: <1358208301.14145.118.camel@misato.fc.hp.com> (raw)
In-Reply-To: <20130114143456.3962f3bd.akpm@linux-foundation.org>

On Mon, 2013-01-14 at 14:34 -0800, Andrew Morton wrote:
> On Mon, 14 Jan 2013 09:31:33 -0800
> "H. Peter Anvin" <hpa@zytor.com> wrote:
> 
> > On 01/14/2013 01:15 AM, Tang Chen wrote:
> > >
> > > For now, users can disable this functionality by not specifying the boot option.
> > > Later, we will post SRAT support, and add another option value "movablecore_map=acpi"
> > > to using SRAT.
> > >
> > 
> > I still think the option "movablecore_map" is uglier than hell.  "core" 
> > could just as easily refer to CPU cores there, but it is a memory mem. 
> > "movablemem" seems more appropriate.
> > 
> > Again, without SRAT I consider this patchset to be largely useless for 
> > anything other than prototyping work.
> > 
> 
> hm, why.  Obviously SRAT support will improve things, but is it
> actually unusable/unuseful with the command line configuration?

I think it is useful for prototyping and testing.  I do not think it is
suitable for regular users.

> Also, "But even if we can use SRAT, users still need an interface to
> enable/disable this functionality if they don't want to loose their
> NUMA performance.  So I think, an user interface is always needed."

Yes, but such user interface could be provided through the management
interface (GUI/CLI) of the platforms (or VMs).  If user sets for
performance, SRAT could be generated with no hot-pluggable memory.  If
user sets node N to be hot-removable, SRAT could be generated in such
way that all memory ranges in node N are hot-pluggable.

Thanks,
-Toshi


> There's also the matter of other architectures.  Has any thought been
> given to how (eg) powerpc would hook into here?
> 
> And what about VMs (xen, KVM)?  I wonder if there is a case for those
> to implement memory hotplug.  
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Toshi Kani <toshi.kani@hp.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	jiang.liu@huawei.com, wujianguo@huawei.com, wency@cn.fujitsu.com,
	laijs@cn.fujitsu.com, linfeng@cn.fujitsu.com, yinghai@kernel.org,
	isimatu.yasuaki@jp.fujitsu.com, rob@landley.net,
	kosaki.motohiro@jp.fujitsu.com, minchan.kim@gmail.com,
	mgorman@suse.de, rientjes@google.com, guz.fnst@cn.fujitsu.com,
	rusty@rustcorp.com.au, lliubbo@gmail.com,
	jaegeuk.hanse@gmail.com, tony.luck@intel.com,
	glommer@parallels.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option
Date: Mon, 14 Jan 2013 17:05:01 -0700	[thread overview]
Message-ID: <1358208301.14145.118.camel@misato.fc.hp.com> (raw)
In-Reply-To: <20130114143456.3962f3bd.akpm@linux-foundation.org>

On Mon, 2013-01-14 at 14:34 -0800, Andrew Morton wrote:
> On Mon, 14 Jan 2013 09:31:33 -0800
> "H. Peter Anvin" <hpa@zytor.com> wrote:
> 
> > On 01/14/2013 01:15 AM, Tang Chen wrote:
> > >
> > > For now, users can disable this functionality by not specifying the boot option.
> > > Later, we will post SRAT support, and add another option value "movablecore_map=acpi"
> > > to using SRAT.
> > >
> > 
> > I still think the option "movablecore_map" is uglier than hell.  "core" 
> > could just as easily refer to CPU cores there, but it is a memory mem. 
> > "movablemem" seems more appropriate.
> > 
> > Again, without SRAT I consider this patchset to be largely useless for 
> > anything other than prototyping work.
> > 
> 
> hm, why.  Obviously SRAT support will improve things, but is it
> actually unusable/unuseful with the command line configuration?

I think it is useful for prototyping and testing.  I do not think it is
suitable for regular users.

> Also, "But even if we can use SRAT, users still need an interface to
> enable/disable this functionality if they don't want to loose their
> NUMA performance.  So I think, an user interface is always needed."

Yes, but such user interface could be provided through the management
interface (GUI/CLI) of the platforms (or VMs).  If user sets for
performance, SRAT could be generated with no hot-pluggable memory.  If
user sets node N to be hot-removable, SRAT could be generated in such
way that all memory ranges in node N are hot-pluggable.

Thanks,
-Toshi


> There's also the matter of other architectures.  Has any thought been
> given to how (eg) powerpc would hook into here?
> 
> And what about VMs (xen, KVM)?  I wonder if there is a case for those
> to implement memory hotplug.  
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  parent reply	other threads:[~2013-01-15  0:14 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  9:15 [PATCH v5 0/5] Add movablecore_map boot option Tang Chen
2013-01-14  9:15 ` Tang Chen
2013-01-14  9:15 ` [PATCH v5 1/5] x86: get pg_data_t's memory from other node Tang Chen
2013-01-14  9:15   ` Tang Chen
2013-01-14  9:15 ` [PATCH v5 2/5] page_alloc: add movable_memmap kernel parameter Tang Chen
2013-01-14  9:15   ` Tang Chen
2013-01-14 22:35   ` Andrew Morton
2013-01-14 22:35     ` Andrew Morton
2013-01-14  9:15 ` [PATCH v5 3/5] page_alloc: Introduce zone_movable_limit[] to keep movable limit for nodes Tang Chen
2013-01-14  9:15   ` Tang Chen
2013-01-14  9:15 ` [PATCH v5 4/5] page_alloc: Make movablecore_map has higher priority Tang Chen
2013-01-14  9:15   ` Tang Chen
2013-01-14  9:15 ` [PATCH v5 5/5] page_alloc: Bootmem limit with movablecore_map Tang Chen
2013-01-14  9:15   ` Tang Chen
2013-01-14 17:31 ` [PATCH v5 0/5] Add movablecore_map boot option H. Peter Anvin
2013-01-14 17:31   ` H. Peter Anvin
2013-01-14 22:34   ` Andrew Morton
2013-01-14 22:34     ` Andrew Morton
2013-01-14 22:41     ` Luck, Tony
2013-01-14 22:41       ` Luck, Tony
2013-01-14 22:46       ` Andrew Morton
2013-01-16  6:25         ` Yasuaki Ishimatsu
2013-01-16  6:25           ` Yasuaki Ishimatsu
2013-01-16 21:29           ` Andrew Morton
2013-01-16 21:29             ` Andrew Morton
2013-01-16 22:01             ` KOSAKI Motohiro
2013-01-16 22:01               ` KOSAKI Motohiro
2013-01-16 23:00               ` H. Peter Anvin
2013-01-16 23:00                 ` H. Peter Anvin
2013-01-17 20:27                 ` KOSAKI Motohiro
2013-01-17 20:27                   ` KOSAKI Motohiro
2013-01-16 22:52             ` H. Peter Anvin
2013-01-16 22:52               ` H. Peter Anvin
2013-01-17  1:49               ` Tang Chen
2013-01-17  1:49                 ` Tang Chen
2013-01-17 20:20                 ` KOSAKI Motohiro
2013-01-17 20:20                   ` KOSAKI Motohiro
2013-01-17  5:08               ` Yasuaki Ishimatsu
2013-01-17  5:08                 ` Yasuaki Ishimatsu
2013-01-17  6:03                 ` H. Peter Anvin
2013-01-17  6:03                   ` H. Peter Anvin
2013-01-17 16:30                   ` Luck, Tony
2013-01-17 16:30                     ` Luck, Tony
2013-01-17 20:28                     ` KOSAKI Motohiro
2013-01-17 20:28                       ` KOSAKI Motohiro
2013-01-18  6:05                       ` Yasuaki Ishimatsu
2013-01-18  6:05                         ` Yasuaki Ishimatsu
2013-01-18  6:25                         ` H. Peter Anvin
2013-01-18  6:25                           ` H. Peter Anvin
2013-01-18  7:38                           ` Yasuaki Ishimatsu
2013-01-18  7:38                             ` Yasuaki Ishimatsu
2013-01-18  8:08                             ` Tang Chen
2013-01-18  8:08                               ` Tang Chen
2013-01-18  9:23                               ` li guang
2013-01-18  9:23                                 ` li guang
2013-01-18 18:29                                 ` Luck, Tony
2013-01-18 18:29                                   ` Luck, Tony
2013-01-19  1:06                                   ` Jiang Liu
2013-01-19  7:52                                     ` Chen Gong
2013-01-21  7:36                                   ` Yasuaki Ishimatsu
2013-01-15  1:23       ` Yasuaki Ishimatsu
2013-01-15  1:23         ` Yasuaki Ishimatsu
2013-01-15  3:44         ` H. Peter Anvin
2013-01-15  3:44           ` H. Peter Anvin
2013-01-15  4:04           ` Luck, Tony
2013-01-15  4:04             ` Luck, Tony
2013-01-15  0:05     ` Toshi Kani [this message]
2013-01-15  0:05       ` Toshi Kani

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=1358208301.14145.118.camel@misato.fc.hp.com \
    --to=toshi.kani@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=glommer@parallels.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=hpa@zytor.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=jaegeuk.hanse@gmail.com \
    --cc=jiang.liu@huawei.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linfeng@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=mgorman@suse.de \
    --cc=minchan.kim@gmail.com \
    --cc=rientjes@google.com \
    --cc=rob@landley.net \
    --cc=rusty@rustcorp.com.au \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tony.luck@intel.com \
    --cc=wency@cn.fujitsu.com \
    --cc=wujianguo@huawei.com \
    --cc=yinghai@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.