From: Vasiliy Tolstov <v.tolstov@selfip.ru>
To: Jan Beulich <JBeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Dan Magenheimer <dan.magenheimer@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen/tmem: cleanup
Date: Tue, 7 Feb 2012 14:23:05 +0400 [thread overview]
Message-ID: <CACaajQt0MDNAN51g6AuYZn7ApwvuVgn+=GdyPNDJYVh95ecD0g@mail.gmail.com> (raw)
In-Reply-To: <4F30E62B02000078000717EB@nat28.tlf.novell.com>
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.
--
Vasiliy Tolstov,
Clodo.ru
e-mail: v.tolstov@selfip.ru
jabber: vase@selfip.ru
next prev parent reply other threads:[~2012-02-07 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 15:09 [PATCH] xen/tmem: cleanup Jan Beulich
2012-02-04 16:42 ` Dan Magenheimer
2012-02-06 8:12 ` Jan Beulich
2012-02-06 16:37 ` Dan Magenheimer
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 10:23 ` Vasiliy Tolstov [this message]
2012-02-09 20:40 ` [Xen-devel] " Konrad Rzeszutek Wilk
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='CACaajQt0MDNAN51g6AuYZn7ApwvuVgn+=GdyPNDJYVh95ecD0g@mail.gmail.com' \
--to=v.tolstov@selfip.ru \
--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=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 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).