From: Michal Hocko <mhocko@kernel.org>
To: David Hildenbrand <david@redhat.com>
Cc: linux-mm@kvack.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Ingo Molnar <mingo@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
Dan Williams <dan.j.williams@intel.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Reza Arbab <arbab@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:XEN HYPERVISOR INTERFACE"
<xen-devel@lists.xenproject.org>
Subject: Re: [PATCH RFC 7/8] mm: allow to control onlining/offlining of memory by a driver
Date: Fri, 13 Apr 2018 17:59:43 +0200 [thread overview]
Message-ID: <20180413155943.GY17484@dhcp22.suse.cz> (raw)
In-Reply-To: <20180413133334.3612-1-david@redhat.com>
On Fri 13-04-18 15:33:28, David Hildenbrand wrote:
> Some devices (esp. paravirtualized) might want to control
> - when to online/offline a memory block
> - how to online memory (MOVABLE/NORMAL)
> - in which granularity to online/offline memory
>
> So let's add a new flag "driver_managed" and disallow to change the
> state by user space. Device onlining/offlining will still work, however
> the memory will not be actually onlined/offlined. That has to be handled
> by the device driver that owns the memory.
Is there any reason to create the memblock sysfs interface to this
memory at all? ZONE_DEVICE mem hotplug users currently do not do that
and manage the memory themselves. It seems you want to achieve the same
thing, no?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-13 15:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 13:16 [PATCH RFC 0/8] mm: online/offline 4MB chunks controlled by device driver David Hildenbrand
2018-04-13 13:16 ` [PATCH RFC 1/8] mm/memory_hotplug: Revert "mm/memory_hotplug: optimize memory hotplug" David Hildenbrand
2018-04-13 13:16 ` [PATCH RFC 2/8] mm: introduce PG_offline David Hildenbrand
2018-04-13 13:40 ` Michal Hocko
2018-04-13 13:46 ` David Hildenbrand
2018-04-17 11:50 ` David Hildenbrand
2018-04-13 17:11 ` Matthew Wilcox
2018-04-16 8:31 ` David Hildenbrand
2018-04-21 16:52 ` Vlastimil Babka
2018-04-22 3:01 ` Matthew Wilcox
2018-04-22 8:17 ` David Hildenbrand
2018-04-22 14:02 ` Matthew Wilcox
2018-04-22 15:13 ` David Hildenbrand
2018-04-29 21:08 ` Michal Hocko
2018-04-30 6:31 ` David Hildenbrand
2018-04-20 7:30 ` David Hildenbrand
2018-04-13 13:16 ` [PATCH RFC 3/8] mm: use PG_offline in online/offlining code David Hildenbrand
2018-04-13 13:31 ` [PATCH RFC 4/8] kdump: expose PG_offline David Hildenbrand
2018-04-13 13:33 ` [PATCH RFC 5/8] mm: only mark section offline when all pages are offline David Hildenbrand
2018-04-13 13:33 ` [PATCH RFC 6/8] mm: offline_pages() is also limited by MAX_ORDER David Hildenbrand
2018-04-13 13:33 ` [PATCH RFC 7/8] mm: allow to control onlining/offlining of memory by a driver David Hildenbrand
2018-04-13 15:59 ` Michal Hocko [this message]
2018-04-13 16:32 ` David Hildenbrand
2018-04-13 13:33 ` [PATCH RFC 8/8] mm: export more functions used to online/offline memory David Hildenbrand
2018-04-13 13:44 ` [PATCH RFC 0/8] mm: online/offline 4MB chunks controlled by device driver Michal Hocko
2018-04-13 14:01 ` David Hildenbrand
2018-04-13 14:20 ` Michal Hocko
2018-04-13 14:59 ` David Hildenbrand
2018-04-13 15:02 ` David Hildenbrand
2018-04-13 16:03 ` Michal Hocko
2018-04-13 16:36 ` David Hildenbrand
2018-04-13 15:59 ` Michal Hocko
2018-04-13 16:31 ` David Hildenbrand
2018-04-16 14:08 ` Michal Hocko
2018-04-16 14:48 ` David Hildenbrand
2018-04-18 15:46 ` David Hildenbrand
2018-04-19 7:33 ` Michal Hocko
2018-04-26 15:30 ` David Hildenbrand
2018-04-29 21:05 ` Michal Hocko
2018-04-30 6:24 ` David Hildenbrand
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=20180413155943.GY17484@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arbab@linux.vnet.ibm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=pasha.tatashin@oracle.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=xen-devel@lists.xenproject.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 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).