linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Kate Stewart" <kstewart@linuxfoundation.org>,
	"Rich Felker" <dalias@libc.org>,
	linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"Heiko Carstens" <heiko.carstens@de.ibm.com>,
	linux-mm@kvack.org,
	"Pavel Tatashin" <pavel.tatashin@microsoft.com>,
	"Paul Mackerras" <paulus@samba.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Rashmica Gupta" <rashmica.g@gmail.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
	linux-s390@vger.kernel.org, "Michael Neuling" <mikey@neuling.org>,
	"Stephen Hemminger" <sthemmin@microsoft.com>,
	"Yoshinori Sato" <ysato@users.sourceforge.jp>,
	linux-acpi@vger.kernel.org, "Ingo Molnar" <mingo@redhat.com>,
	xen-devel@lists.xenproject.org, "Rob Herring" <robh@kernel.org>,
	"Len Brown" <lenb@kernel.org>,
	"Fenghua Yu" <fenghua.yu@intel.com>,
	"Stephen Rothwell" <sfr@canb.auug.org.au>,
	"mike.travis@hpe.com" <mike.travis@hpe.com>,
	"Haiyang Zhang" <haiyangz@microsoft.com>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Joe Perches" <joe@perches.com>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Mike Rapoport" <rppt@linux.vnet.ibm.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Andy Lutomirski" <luto@kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Joonsoo Kim" <iamjoonsoo.kim@lge.com>,
	"Oscar Salvador" <osalvador@suse.de>,
	"Juergen Gross" <jgross@suse.com>,
	"Tony Luck" <tony.luck@intel.com>,
	"Mathieu Malaterre" <malat@debian.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org,
	"Mauricio Faria de Oliveira" <mauricfo@linux.vnet.ibm.com>,
	"Philippe Ombredanne" <pombredanne@nexb.com>,
	"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
	devel@linuxdriverproject.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linuxppc-dev@lists.ozlabs.org,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH RFC] mm/memory_hotplug: Introduce memory block types
Date: Thu, 4 Oct 2018 09:40:56 +0200	[thread overview]
Message-ID: <060bd891-f88e-13e1-2bb3-26d96f6d28cb@redhat.com> (raw)
In-Reply-To: <20181004062811.GC22173@dhcp22.suse.cz>

On 04/10/2018 08:28, Michal Hocko wrote:
> On Wed 03-10-18 19:00:29, David Hildenbrand wrote:
> [...]
>> Let me rephrase: You state that user space has to make the decision and
>> that user should be able to set/reconfigure rules. That is perfectly fine.
>>
>> But then we should give user space access to sufficient information to
>> make a decision. This might be the type of memory as we learned (what
>> some part of this patch proposes), but maybe later more, e.g. to which
>> physical device memory belongs (e.g. to hotplug it all movable or all
>> normal) ...
> 
> I am pretty sure that user knows he/she wants to use ballooning in
> HyperV or Xen, or that the memory hotplug should be used as a "RAS"
> feature to allow add and remove DIMMs for reliability. Why shouldn't we
> have a package to deploy an appropriate set of udev rules for each of
> those usecases? I am pretty sure you need some other plumbing to enable
> them anyway (e.g. RAS would require to have movable_node kernel
> parameters, ballooning a kernel module etc.).
> 
> Really, one udev script to rule them all will simply never work.
> 

I am on your side. We will need multiple ones. But we need sane
defaults. And a default rule will always exist. And users will expect
that the defaults somewhat match their expectation unless they really
have some special use cases.

All I am saying is, again, that if user space is to make decisions, it
should get sufficient information to make sane decision. And in my point
of view, the type of memory allows us to make these decision and to
provide a "single udev script to rule them all" with sane defaults.

I at least think the distinction between "auto-online" and "standby" is
required (what Dave suggested).

The we can make a simple rule

if (auto-online memory) {
	if (virtual environment) {
		"online"
	} else {
		"online_movable"
	}
}
/* standby memory not onlined as default */

We are able to provide sane defaults.

-- 

Thanks,

David / dhildenb

  reply	other threads:[~2018-10-04  7:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 15:03 [PATCH RFC] mm/memory_hotplug: Introduce memory block types David Hildenbrand
2018-09-28 17:02 ` Dave Hansen
2018-10-01  9:13   ` David Hildenbrand
2018-10-01 16:24     ` Dave Hansen
2018-10-04  7:48       ` David Hildenbrand
2018-10-01  8:40 ` Michal Hocko
2018-10-01  9:34   ` David Hildenbrand
2018-10-02 13:47     ` Michal Hocko
2018-10-02 15:25       ` David Hildenbrand
2018-10-03 13:38         ` Vitaly Kuznetsov
2018-10-03 13:44           ` Michal Hocko
2018-10-03 13:52             ` Vitaly Kuznetsov
2018-10-03 14:07               ` Dave Hansen
2018-10-03 14:34                 ` Vitaly Kuznetsov
2018-10-03 17:14                   ` David Hildenbrand
2018-10-04  6:19                     ` Michal Hocko
2018-10-04  8:13                       ` David Hildenbrand
2018-10-04 15:28                         ` Michal Suchánek
2018-10-04 15:45                           ` David Hildenbrand
2018-10-04 17:50                             ` Michal Suchánek
2018-10-05  7:37                               ` David Hildenbrand
2018-10-03 14:24               ` Michal Hocko
2018-10-03 17:06                 ` David Hildenbrand
2018-10-04  8:12                 ` David Hildenbrand
2018-10-03 13:54         ` Michal Hocko
2018-10-03 17:00           ` David Hildenbrand
2018-10-04  6:28             ` Michal Hocko
2018-10-04  7:40               ` David Hildenbrand [this message]
2018-11-23 11:13 ` David Hildenbrand
2018-11-23 18:06   ` Michal Suchánek
2018-11-26 12:30     ` David Hildenbrand
2018-11-26 13:33       ` David Hildenbrand
2018-11-26 14:20         ` Michal Suchánek
2018-11-26 15:59           ` David Hildenbrand
2018-11-27 16:32             ` Michal Suchánek
2018-11-27 16:47               ` 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=060bd891-f88e-13e1-2bb3-26d96f6d28cb@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=dalias@libc.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=devel@linuxdriverproject.org \
    --cc=fenghua.yu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hpa@zytor.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=j.neuschaefer@gmx.net \
    --cc=jglisse@redhat.com \
    --cc=jgross@suse.com \
    --cc=joe@perches.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=kys@microsoft.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luto@kernel.org \
    --cc=malat@debian.org \
    --cc=mauricfo@linux.vnet.ibm.com \
    --cc=mhocko@kernel.org \
    --cc=mike.travis@hpe.com \
    --cc=mikey@neuling.org \
    --cc=mingo@redhat.com \
    --cc=npiggin@gmail.com \
    --cc=osalvador@suse.de \
    --cc=paulus@samba.org \
    --cc=pavel.tatashin@microsoft.com \
    --cc=peterz@infradead.org \
    --cc=pombredanne@nexb.com \
    --cc=rashmica.g@gmail.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh@kernel.org \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=sthemmin@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=ysato@users.sourceforge.jp \
    /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).