From: Dave Hansen <dave.hansen@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Zhang Zhen <zhenzhang.zhang@huawei.com>
Cc: Toshi Kani <toshi.kani@hp.com>,
David Rientjes <rientjes@google.com>,
isimatu.yasuaki@jp.fujitsu.com, n-horiguchi@ah.jp.nec.com,
wangnan0@huawei.com, linux-kernel@vger.kernel.org,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v2] memory-hotplug: add sysfs zones_online_to attribute
Date: Fri, 22 Aug 2014 15:21:58 -0700 [thread overview]
Message-ID: <53F7C286.50800@intel.com> (raw)
In-Reply-To: <20140822151622.6786c1089548ea5ceb3732bf@linux-foundation.org>
On 08/22/2014 03:16 PM, Andrew Morton wrote:
> Also, it's not really clear to me why we need this sysfs file at all.
> Do people really read sysfs files, make onlining decisions and manually
> type in commands? Or is this stuff all automated? If the latter then
> the script can take care of all this? For example, attempt to online
> the memory into the desired zone and report failure if that didn't
> succeed?
I guess we can just iterate over all possible zone types from userspace
until we find one. Seems a bit hokey, but it would work at least until
we add a new zone type and we have to teach the scripts about the new
type. But that's a pretty rare event I guess. Let's hope the script
writers get this right, and don't make omissions like ZONE_MOVABLE
because it's not that common in practice.
--
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: Dave Hansen <dave.hansen@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Zhang Zhen <zhenzhang.zhang@huawei.com>
Cc: Toshi Kani <toshi.kani@hp.com>,
David Rientjes <rientjes@google.com>,
isimatu.yasuaki@jp.fujitsu.com, n-horiguchi@ah.jp.nec.com,
wangnan0@huawei.com, linux-kernel@vger.kernel.org,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v2] memory-hotplug: add sysfs zones_online_to attribute
Date: Fri, 22 Aug 2014 15:21:58 -0700 [thread overview]
Message-ID: <53F7C286.50800@intel.com> (raw)
In-Reply-To: <20140822151622.6786c1089548ea5ceb3732bf@linux-foundation.org>
On 08/22/2014 03:16 PM, Andrew Morton wrote:
> Also, it's not really clear to me why we need this sysfs file at all.
> Do people really read sysfs files, make onlining decisions and manually
> type in commands? Or is this stuff all automated? If the latter then
> the script can take care of all this? For example, attempt to online
> the memory into the desired zone and report failure if that didn't
> succeed?
I guess we can just iterate over all possible zone types from userspace
until we find one. Seems a bit hokey, but it would work at least until
we add a new zone type and we have to teach the scripts about the new
type. But that's a pretty rare event I guess. Let's hope the script
writers get this right, and don't make omissions like ZONE_MOVABLE
because it's not that common in practice.
next prev parent reply other threads:[~2014-08-22 22:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1407902811-4873-1-git-send-email-zhenzhang.zhang@huawei.com>
2014-08-13 4:10 ` [PATCH v2] memory-hotplug: add sysfs zones_online_to attribute Zhang Zhen
2014-08-13 4:10 ` Zhang Zhen
2014-08-15 21:37 ` Toshi Kani
2014-08-15 21:37 ` Toshi Kani
2014-08-18 3:25 ` Zhang Zhen
2014-08-18 3:25 ` Zhang Zhen
2014-08-18 6:20 ` Yasuaki Ishimatsu
2014-08-18 6:20 ` Yasuaki Ishimatsu
2014-08-22 22:16 ` Andrew Morton
2014-08-22 22:16 ` Andrew Morton
2014-08-22 22:21 ` Dave Hansen [this message]
2014-08-22 22:21 ` Dave Hansen
2014-08-25 1:55 ` Zhang Zhen
2014-08-25 1:55 ` Zhang Zhen
2014-08-25 13:58 ` Toshi Kani
2014-08-25 13:58 ` Toshi Kani
2014-08-18 6:11 ` Yasuaki Ishimatsu
2014-08-18 6:11 ` Yasuaki Ishimatsu
2014-08-19 7:35 ` Zhang Zhen
2014-08-19 7:35 ` Zhang Zhen
2014-08-19 10:42 ` Yasuaki Ishimatsu
2014-08-19 10:42 ` Yasuaki Ishimatsu
2014-08-18 21:48 ` David Rientjes
2014-08-18 21:48 ` David Rientjes
2014-08-19 1:43 ` Zhang Zhen
2014-08-19 1:43 ` Zhang Zhen
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=53F7C286.50800@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.com \
--cc=toshi.kani@hp.com \
--cc=wangnan0@huawei.com \
--cc=zhenzhang.zhang@huawei.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 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.