From: Dario Faggioli <dario.faggioli@citrix.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
Wei Liu <wei.liu2@citrix.com>
Cc: Maryam Masoudian <maryammasoudian@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen Memory de-duplication
Date: Wed, 20 Apr 2016 19:34:47 +0100 [thread overview]
Message-ID: <1461177287.6768.4.camel@citrix.com> (raw)
In-Reply-To: <CABfawhmtKrDZ551kF4h7=MOTsnqpOMiA+Sj+-V4_3CoJCHvX6g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1230 bytes --]
On Wed, 2016-04-20 at 10:25 -0600, Tamas K Lengyel wrote:
>
>
> On Wed, Apr 20, 2016 at 7:24 AM, Wei Liu <wei.liu2@citrix.com> wrote:
> > On Tue, Apr 19, 2016 at 07:07:01AM -0400, Maryam Masoudian wrote:
> > > Thanks.
> > > One more thing, is it possible to see the percentage of shared
> > memory among
> > > VMs by xl tool?
> > > As there is a xl sharing and I want to know whether this provides
> > this
> > > facility ...
> > >
> >
> > Not sure. You can check xl manpage for those commands.
> xl doesn't have any command that shows you a breakdown of sharing
> among VMs,
>
Can we add it? (as soon as practical, of course)
There are other per-vm memory related info that I'd like to be able to
query from xl --like how much memory is on each NUMA node-- so a new
sub-command like `xl meminfo' (name subject to improvement! :-D), with
various parameters selecting what to actually show, could be an useful
addition.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-20 18:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 11:25 Xen Memory de-duplication Maryam Masoudian
2016-04-17 12:15 ` Wei Liu
2016-04-17 13:58 ` Maryam Masoudian
2016-04-17 14:20 ` Wei Liu
[not found] ` <CAOJrJTc5dynTwiMrtE4Logpz1_ct3oM9vz3HWh1s1sDMY+hSxw@mail.gmail.com>
2016-04-20 13:24 ` Wei Liu
2016-04-20 16:25 ` Tamas K Lengyel
2016-04-20 18:34 ` Dario Faggioli [this message]
2016-04-20 19:01 ` Tamas K Lengyel
2016-04-21 12:47 ` Dario Faggioli
[not found] ` <CAOJrJTeK3ntGGwyAjY25xL0g8AXtDcoUOcipF4jmZDCfbdA9Kw@mail.gmail.com>
2016-04-21 15:24 ` Tamas K Lengyel
-- strict thread matches above, loose matches on Subject: below --
2010-10-09 17:56 Xen Memory De-duplication Aditya Gadre
2010-10-09 19:09 ` Pasi Kärkkäinen
2010-10-09 23:40 ` Dan Magenheimer
2010-10-10 5:24 ` Aditya Gadre
2010-10-10 12:34 ` Pasi Kärkkäinen
2010-10-11 7:58 ` Shriram Rajagopalan
2010-10-12 10:20 ` Thomas Goirand
2010-10-12 10:33 ` Tim Deegan
2010-10-11 12:59 ` Tim Deegan
2010-10-08 19:01 Aditya Gadre
2010-10-08 19:02 ` Aditya Gadre
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=1461177287.6768.4.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=maryammasoudian@gmail.com \
--cc=tamas.k.lengyel@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).