From: Juergen Gross <jgross@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Jim Fehlig <jfehlig@suse.com>, Wei Liu <wei.liu2@citrix.com>
Subject: Re: memory hotplug for domUs
Date: Fri, 20 Jan 2017 17:06:50 +0100 [thread overview]
Message-ID: <d1e97e86-8087-e31d-ae30-d8ecfe9f4530@suse.com> (raw)
In-Reply-To: <22658.12973.598314.89177@mariner.uk.xensource.com>
On 20/01/17 16:54, Ian Jackson wrote:
> Juergen Gross writes ("memory hotplug for domUs"):
>> We first thought to enhance "xl mem-set", but after some more thinking
>> about it I'd rather add a new xl command, e.g. "mem-add" (we could later
>> even add "mem-remove" to support memory unplug).
>
> Why ? Why would xl mem-set not automatically do the right thing ?
How would you specify the numa node to add the memory to?
Especially for removal of memory ballooning and hotplug are _very_
different.
> This problem with lack of support (and indeed requirementse to do
> hotplug things) is a detail that in the long term should not be a
> problem, and in the meantime can be dealt with by a force option.
I think it would be clearer with new commands for hotplugging. I
don't feel very strong about this, so in case everyone else is fine
with handling everything via mem-set I won't object.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-20 16:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 9:26 memory hotplug for domUs Juergen Gross
2017-01-20 11:08 ` Andrew Cooper
2017-01-20 13:50 ` Konrad Rzeszutek Wilk
2017-01-20 14:19 ` Boris Ostrovsky
2017-01-20 14:27 ` Roger Pau Monné
2017-01-20 14:34 ` Juergen Gross
2017-01-20 14:36 ` Boris Ostrovsky
2017-01-20 15:54 ` Ian Jackson
2017-01-20 16:06 ` Juergen Gross [this message]
2017-01-20 16:37 ` Ian Jackson
2017-01-20 16:38 ` Juergen Gross
2017-01-24 23:03 ` Jim Fehlig
2017-01-25 13:02 ` Dario Faggioli
2017-02-03 10:04 ` Juergen Gross
2017-02-03 12:19 ` Ian Jackson
2017-02-03 13:16 ` Juergen Gross
2017-02-03 13:23 ` Ian Jackson
2017-02-03 13:29 ` Juergen Gross
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=d1e97e86-8087-e31d-ae30-d8ecfe9f4530@suse.com \
--to=jgross@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jfehlig@suse.com \
--cc=wei.liu2@citrix.com \
--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 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.