From: Daniel Kiper <daniel.kiper@oracle.com>
To: ian.campbell@citrix.com, ian.jackson@eu.citrix.com,
konrad.wilk@oracle.com, xen-devel@lists.xensource.com
Subject: [PATCH v2 0/2] libxl: memory management patches
Date: Thu, 21 Mar 2013 14:52:57 +0100 [thread overview]
Message-ID: <1363873979-6087-1-git-send-email-daniel.kiper@oracle.com> (raw)
Hi,
Here are two small but important libxl/xl memory management patches:
- libxl: xl mem-max et consortes must update static-max in xenstore too,
- xl: Add mem_set_enforce_limit option to xl.conf file.
Daniel
next reply other threads:[~2013-03-21 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:52 Daniel Kiper [this message]
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
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=1363873979-6087-1-git-send-email-daniel.kiper@oracle.com \
--to=daniel.kiper@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=konrad.wilk@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).