| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 16 Dec 2015 10:25:27 +0100
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: Daniel Kiper <daniel.kiper@...cle.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dan Williams <dan.j.williams@...el.com>,
Tang Chen <tangchen@...fujitsu.com>,
David Vrabel <david.vrabel@...rix.com>,
David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Gu Zheng <guz.fnst@...fujitsu.com>,
Xishi Qiu <qiuxishi@...wei.com>,
Mel Gorman <mgorman@...hsingularity.net>,
"K. Y. Srinivasan" <kys@...rosoft.com>
Subject: Re: [PATCH RFC] memory-hotplug: add automatic onlining policy for the newly added memory
Daniel Kiper <daniel.kiper@...cle.com> writes:
> Hey Vitaly,
>
> On Tue, Dec 15, 2015 at 07:05:53PM +0100, Vitaly Kuznetsov wrote:
>> Currently, all newly added memory blocks remain in 'offline' state unless
>> someone onlines them, some linux distributions carry special udev rules
>> like:
>>
>> SUBSYSTEM=="memory", ACTION=="add", ATTR{state}=="offline", ATTR{state}="online"
>>
>> to make this happen automatically. This is not a great solution for virtual
>> machines where memory hotplug is being used to address high memory pressure
>> situations as such onlining is slow and a userspace process doing this
>> (udev) has a chance of being killed by the OOM killer as it will probably
>> require to allocate some memory.
>>
>> Introduce default policy for the newly added memory blocks in
>> /sys/devices/system/memory/hotplug_autoonline file with two possible
>> values: "offline" (the default) which preserves the current behavior and
>> "online" which causes all newly added memory blocks to go online as
>> soon as they're added.
>
> In general idea make sense for me but...
>
>> Cc: Jonathan Corbet <corbet@....net>
>> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> Cc: Daniel Kiper <daniel.kiper@...cle.com>
>> Cc: Dan Williams <dan.j.williams@...el.com>
>> Cc: Tang Chen <tangchen@...fujitsu.com>
>> Cc: David Vrabel <david.vrabel@...rix.com>
>> Cc: David Rientjes <rientjes@...gle.com>
>> Cc: Andrew Morton <akpm@...ux-foundation.org>
>> Cc: Naoya Horiguchi <n-horiguchi@...jp.nec.com>
>> Cc: Gu Zheng <guz.fnst@...fujitsu.com>
>> Cc: Xishi Qiu <qiuxishi@...wei.com>
>> Cc: Mel Gorman <mgorman@...hsingularity.net>
>> Cc: "K. Y. Srinivasan" <kys@...rosoft.com>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@...hat.com>
>> ---
>> - I was able to find previous attempts to fix the issue, e.g.:
>> http://marc.info/?l=linux-kernel&m=137425951924598&w=2
>> http://marc.info/?l=linux-acpi&m=127186488905382
>> but I'm not completely sure why it didn't work out and the solution
>> I suggest is not 'smart enough', thus 'RFC'.
>> ---
>> Documentation/memory-hotplug.txt | 21 +++++++++++++++++----
>> drivers/base/memory.c | 35 +++++++++++++++++++++++++++++++++++
>> include/linux/memory_hotplug.h | 2 ++
>> mm/memory_hotplug.c | 8 ++++++++
>> 4 files changed, 62 insertions(+), 4 deletions(-)
>>
>> diff --git a/Documentation/memory-hotplug.txt b/Documentation/memory-hotplug.txt
>> index ce2cfcf..fe576d9 100644
>> --- a/Documentation/memory-hotplug.txt
>> +++ b/Documentation/memory-hotplug.txt
>> @@ -254,12 +254,25 @@ If the memory block is online, you'll read "online".
>> If the memory block is offline, you'll read "offline".
>>
>>
>> -5.2. How to online memory
>> +5.2. Memory onlining
>> ------------
>> -Even if the memory is hot-added, it is not at ready-to-use state.
>> -For using newly added memory, you have to "online" the memory block.
>> +When the memory is hot-added, the kernel decides whether or not to "online"
>> +it according to the policy which can be read from "hotplug_autoonline" file:
>>
>> -For onlining, you have to write "online" to the memory block's state file as:
>> +% cat /sys/devices/system/memory/hotplug_autoonline
>> +
>> +The default is "offline" which means the newly added memory will not be at
>> +ready-to-use state and you have to "online" the newly added memory blocks
>> +manually.
>> +
>> +Automatic onlining can be requested by writing "online" to "hotplug_autoonline"
>> +file:
>> +
>> +% echo online > /sys/devices/system/memory/hotplug_autoonline
>> +
>> +If the automatic onlining wasn't requested or some memory block was offlined
>> +it is possible to change the individual block's state by writing to the "state"
>> +file:
>>
>> % echo online > /sys/devices/system/memory/memoryXXX/state
>>
>> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
>> index 25425d3..001fefe 100644
>> --- a/drivers/base/memory.c
>> +++ b/drivers/base/memory.c
>> @@ -438,6 +438,40 @@ print_block_size(struct device *dev, struct device_attribute *attr,
>>
>> static DEVICE_ATTR(block_size_bytes, 0444, print_block_size, NULL);
>>
>> +
>> +/*
>> + * Memory auto online policy.
>> + */
>> +
>> +static ssize_t
>> +show_memhp_autoonline(struct device *dev, struct device_attribute *attr,
>> + char *buf)
>> +{
>> + if (memhp_autoonline == MMOP_ONLINE_KEEP)
>> + return sprintf(buf, "online\n");
>> + else if (memhp_autoonline == MMOP_OFFLINE)
>> + return sprintf(buf, "offline\n");
>> + else
>> + return sprintf(buf, "unknown\n");
>
> You do not allow unknown state below, so, I do not know how it can appear
> here. If it appears out of the blue then I think that we should be alert
> because something magic happens around us. Hence, if you wish to leave
> this unknown stuff then I suppose we should at least call WARN_ON() if
> not BUG_ON() there too (well, I am not convinced about latter).
>
Sure,
it is definitelly impossible to see 'unknown' with the current code. The
one (small) reason I added it is that there are two more possible values
for /sys/devices/system/memory/memoryXXX/state: online_movable and
online_kernel. While I don't see how 'online_kernel' can be used for
automatic hotplug (all new memory blocks are being added to ZONE_NORMAL)
'online_movable' could (in theory) be used here so all new memroy blocks
will go to ZONE_MOVABLE. To achieve that someone could set
memhp_autoonline to MMOP_ONLINE_MOVABLE and it will (in theory) work but
I didn't want to add such option to the
/sys/devices/system/memory/hotplug_autoonline interface without a
reason.
I can of course remove this (or replace with WARN_ON) for now.
Thanks,
>> +}
>> +
>> +static ssize_t
>> +store_memhp_autoonline(struct device *dev, struct device_attribute *attr,
>> + const char *buf, size_t count)
>> +{
>> + if (sysfs_streq(buf, "online"))
>> + memhp_autoonline = MMOP_ONLINE_KEEP;
>> + else if (sysfs_streq(buf, "offline"))
>> + memhp_autoonline = MMOP_OFFLINE;
>> + else
>> + return -EINVAL;
>
> Here you are not able to set anything which is not allowed.
> So, please look above.
>
> Daniel
--
Vitaly
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists