| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [PATCH V3] xen/balloon: Memory hotplug support for Xen b
|
To: |
Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [PATCH V3] xen/balloon: Memory hotplug support for Xen balloon driver |
|
From: |
Vasiliy G Tolstov <v.tolstov@xxxxxxxxx> |
|
Date: |
Wed, 18 May 2011 11:24:54 +0400 |
|
Cc: |
"jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "haicheng.li@xxxxxxxxxxxxxxx" <haicheng.li@xxxxxxxxxxxxxxx>, "konrad.wilk@xxxxxxxxxx" <konrad.wilk@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Dan, Magenheimer <dan.magenheimer@xxxxxxxxxx>, "dave@xxxxxxxxxxxxxxxxxx" <dave@xxxxxxxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, "wdauchy@xxxxxxxxx" <wdauchy@xxxxxxxxx>, "rientjes@xxxxxxxxxx" <rientjes@xxxxxxxxxx>, "andi.kleen@xxxxxxxxx" <andi.kleen@xxxxxxxxx>, "akpm@xxxxxxxxxxxxxxxxxxxx" <akpm@xxxxxxxxxxxxxxxxxxxx>, "fengguang.wu@xxxxxxxxx" <fengguang.wu@xxxxxxxxx>, Daniel Kiper <dkiper@xxxxxxxxxxxx> |
|
Delivery-date: |
Wed, 18 May 2011 00:25:58 -0700 |
|
Dkim-signature: |
v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=selfip.ru; s=dk; h=Content-Transfer-Encoding:Mime-Version:Message-ID:Date:Content-Type:References:In-Reply-To:Cc:To:Reply-To:From:Subject; bh=4ZgRdKc7jpuwZbnOgbpYPwoQQ/Si4kwzkhQOivKVEZg=; b=g+287vkfs8S1Y1/lWxkIvvw+Kk91OWCJrsJX5mIY7BbFI/YLk/cfg67X23JY+tBfp+OvBZ7IsRiAZzpYQxBivXCQZc6/YRwjbOeuERMs5xqjebmMCVHQKjw+FcLGeBqv; |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<1305703309.7738.23.camel@xxxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
Organization: |
Selfip.Ru |
|
References: |
<20110517214421.GD30232@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1305701868.28175.1.camel@vase> <1305703309.7738.23.camel@xxxxxxxxxxxxxxxxxxxx> |
|
Reply-to: |
v.tolstov@xxxxxxxxx |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On Wed, 2011-05-18 at 08:21 +0100, Ian Campbell wrote:
> On Wed, 2011-05-18 at 07:57 +0100, Vasiliy G Tolstov wrote:
> > On Tue, 2011-05-17 at 23:44 +0200, Daniel Kiper wrote:
> > > + Memory could be hotplugged in following steps:
> > > +
> > > + 1) dom0: xl mem-max <domU> <maxmem>
> > > + where <maxmem> is >= requested memory size,
> > > +
> > > + 2) dom0: xl mem-set <domU> <memory>
> > > + where <memory> is requested memory size; alternatively memory
> > > + could be added by writing proper value to
> > > + /sys/devices/system/xen_memory/xen_memory0/target or
> > > + /sys/devices/system/xen_memory/xen_memory0/target_kb on dumU,
> > > +
> > > + 3) domU: for i in /sys/devices/system/memory/memory*/state; do \
> > > + [ "`cat "$i"`" = offline ] && echo online > "$i"; done
> > > +
>
> > Very good. Is that possible to eliminate step 3 ? And do it automatic if
> > domU runs with specific xen balloon param?
>
> When we faced the same question WRT VCPU hotplug we ended up using a
> udev rule. Presumably the same could be done here. In the VCPU case the
> rule is:
>
> ACTION=="add", SUBSYSTEM=="cpu", RUN+="/bin/sh -c '[ ! -e /sys$devpath/online
> ] || echo 1 > /sys$devpath/online'"
>
> Presumably the memory one will be broadly similar.
>
> Ian.
>
Ok. very good solution. Thank's.
--
Vasiliy G Tolstov <v.tolstov@xxxxxxxxx>
Selfip.Ru
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home