From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH v2 2/2] xl: Add mem_set_enforce_limit option to xl.conf file
Date: Tue, 26 Mar 2013 09:10:53 -0400 [thread overview]
Message-ID: <20130326131053.GA18215@phenom.dumpdata.com> (raw)
In-Reply-To: <20816.30750.731502.73036@mariner.uk.xensource.com>
On Mon, Mar 25, 2013 at 04:15:26PM +0000, Ian Jackson wrote:
> Daniel Kiper writes ("[PATCH v2 2/2] xl: Add mem_set_enforce_limit option to xl.conf file"):
> > Add mem_set_enforce_limit option to xl.conf file.
> > It gives a chance to align xl mem-set behavior
> > to xm mem-set behavior. Default xl mem-set
> > behavior is not changed.
>
> Should this be a per-domain config option ? I confess I don't
> understand the usage model very well but it would seem that enforcing
> against some guests but not others would be a sensible otpion.
This option is to provide a mechanism to fallback to xend behavior.
>
> Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-03-26 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:52 [PATCH v2 0/2] libxl: memory management patches Daniel Kiper
2013-03-21 13:52 ` [PATCH v2 1/2] libxl: xl mem-max et consortes must update static-max in xenstore too Daniel Kiper
2013-03-25 16:17 ` Ian Jackson
2013-04-10 9:02 ` Ian Campbell
2013-03-21 13:52 ` [PATCH v2 2/2] xl: Add mem_set_enforce_limit option to xl.conf file Daniel Kiper
2013-03-23 13:42 ` Konrad Rzeszutek Wilk
2013-03-25 16:15 ` Ian Jackson
2013-03-26 13:10 ` Konrad Rzeszutek Wilk [this message]
2013-03-27 21:02 ` [PATCH v2 0/2] libxl: memory management patches Daniel Kiper
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=20130326131053.GA18215@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=daniel.kiper@oracle.com \
--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).