From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: Jan Beulich <JBeulich@suse.com>,
linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] [PATCH] xen/tmem: cleanup
Date: Thu, 9 Feb 2012 16:40:18 -0400 [thread overview]
Message-ID: <20120209204018.GC14007@andromeda.dapyr.net> (raw)
In-Reply-To: <CACaajQt0MDNAN51g6AuYZn7ApwvuVgn+=GdyPNDJYVh95ecD0g@mail.gmail.com>
On Tue, Feb 07, 2012 at 02:23:05PM +0400, Vasiliy Tolstov wrote:
> 2012/2/7 Jan Beulich <JBeulich@suse.com>:
>
> >
> > As outlined above, it is possible, but I'm not certain it is a good idea
> > to have balloon_set_new_target() exported. If you think that's
> > acceptable, I can certainly put together a patch doing that (on top
> > of the one here, and probably not immediately).
> >
> > Jan
>
> Exporting balloon_set_new_target can be grate feature to do own
> modules for balloon memory inside xen guest, becouse some times we
> need more realtime control from dom0 for memory growing speed inside
> guest.
Sounds like we have two use cases :-)
I am not seeing anything against it but I wonder if other virtualization
offerings would benefit from this as well? As in would it make sense to
export the virtio-ballon or the microsoft one as well? And perhaps have
an unified API? So that the ballloon drivers register and then have a
"virt_mem_set_new_target" exported?
prev parent reply other threads:[~2012-02-09 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 15:09 [PATCH] xen/tmem: cleanup Jan Beulich
2012-02-03 15:09 ` Jan Beulich
2012-02-04 16:42 ` Dan Magenheimer
2012-02-06 8:12 ` Jan Beulich
2012-02-06 8:12 ` Jan Beulich
2012-02-06 16:37 ` Dan Magenheimer
2012-02-06 16:49 ` Jan Beulich
2012-02-06 16:49 ` Jan Beulich
2012-02-06 17:02 ` Konrad Rzeszutek Wilk
2012-02-06 17:22 ` Dan Magenheimer
2012-02-09 20:15 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-02-07 7:51 ` Jan Beulich
2012-02-07 7:51 ` Jan Beulich
2012-02-07 10:23 ` [Xen-devel] " Vasiliy Tolstov
2012-02-09 20:40 ` Konrad Rzeszutek Wilk [this message]
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=20120209204018.GC14007@andromeda.dapyr.net \
--to=konrad@darnok.org \
--cc=JBeulich@suse.com \
--cc=dan.magenheimer@oracle.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=v.tolstov@selfip.ru \
--cc=xen-devel@lists.xensource.com \
/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.