From: Vladimir Zidar <mr_w@mindnever.org>
To: Chris Lalancette <clalance@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: hypervisor memory usage
Date: Wed, 28 Oct 2009 15:13:31 +0100 [thread overview]
Message-ID: <4AE8518B.2090101@mindnever.org> (raw)
In-Reply-To: <4AE844A3.90300@redhat.com>
Chris,
good that you pointed to 5.2 vs 5.3 vs 5.4,
the difference in number of pages is noticed between these:
xen.gz-2.6.18-92.1.22.el5 - last 5.2 update - all pages are ok,
xen.gz-2.6.18-128.el5 - first 5.3 release - ~80000 pages missing
on 8GB ram setup.
Chris Lalancette wrote:
> Vladimir Zidar wrote:
>
>> Sounds possible. However it would be great if there was switch to
>> disable that feature in case hardware is not capable of VT-d, as I'd
>> rather use those 300mb than have software support for something that I
>> can't actually use.
>>
>
> In point of fact, VT-d is disabled by default; you need to explicitly enable it
> for it to use memory. However, it's possible that there's a bug, or some other
> change caused the memory difference, so it's worthwhile to try and track it down
> a little better. In particular, you jumped from the 5.2 kernel to the 5.4, so
> it would be worthwhile to try the 5.3 kernel and see what you get.
>
>
next prev parent reply other threads:[~2009-10-28 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 9:29 hypervisor memory usage Vladimir Zidar
2009-10-28 9:45 ` Pasi Kärkkäinen
2009-10-28 9:53 ` Vladimir Zidar
2009-10-28 10:40 ` Keir Fraser
2009-10-28 11:19 ` Vladimir Zidar
2009-10-28 11:58 ` Pasi Kärkkäinen
2009-10-28 12:02 ` Vladimir Zidar
2009-10-28 13:12 ` Pasi Kärkkäinen
2009-10-28 13:18 ` Chris Lalancette
2009-10-28 14:13 ` Vladimir Zidar [this message]
2009-10-29 11:07 ` Vladimir Zidar
2009-10-29 11:19 ` Vladimir Zidar
2009-10-29 12:05 ` Keir Fraser
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=4AE8518B.2090101@mindnever.org \
--to=mr_w@mindnever.org \
--cc=clalance@redhat.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 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.