Bill Gray wrote:
See attachment with two graphs: (1) cache bandwidth, (2) blowup of
sustained memory bandwidth region...
Bill,
I had some difficulty with this document under ooffice.
A recent version seized and an older version didn't seem
to render correctly. Could you export it as pdf?
. However I wanted to call this out here in the
event we're overlooking something.
Thanks,
-john
http://post-office.corp.redhat.com/archives/rhvirt-patches/2010-July/msg01110.html
http://post-office.corp.redhat.com/archives/rhvirt-patches/2010-July/msg00831.html
john cooper wrote:
Addresses BZs
Dor Laor wrote:
What about another approach for the cpuid issue:
I think that dealing with specific flags is pretty error prone on all
levels - virt-mgr, libvirt, qemu, migration, and even the guest.
..and performance verification, QA, and the average end user.
Unless we reduce all possible
Daniel P. Berrange wrote:
* configure.in: Add check for mntent.h
* qemud/libvirtd_qemu.aug, qemud/test_libvirtd_qemu.aug, src/qemu.conf
Add 'hugetlbfs_mount' config parameter
* src/qemu_conf.c, src/qemu_conf.h: Check for -mem-path flag in QEMU,
and pass it when hugepages are requested.
Mark McLoughlin wrote:
Other options include:
- hugepages/
- memory hugepages=yesX/memory
Yes, I'd expect additional options will need to
be addressed. Currently the only additional
qemu-resident knob is the -mem-prealloc flag
which is enabled by default. I've removed
support
Daniel P. Berrange wrote:
On Wed, Jul 22, 2009 at 09:25:02PM -0400, john cooper wrote:
This patch allows passing of a -mem-path arg
flag to qemu for support of huge page backed
guests. A guest may request this option via
specifying:
hugepageon/hugepage
in its domain definition xml
, verifying the mount
point is correct/usable, nor assure sufficient
free huge pages are available; which are assumed
to be addressed by other means.
Signed-off-by: john cooper john.coo...@redhat.com
---
diff --git a/src/domain_conf.c b/src/domain_conf.c
index f3e4c6c..04d6911 100644
--- a/src
Jim Meyering wrote:
Hi John,
I tried to apply that, but failed miserably,
since all of the following was recently redone to
use virBufferVSprintf rather than snprintf.
Yea I suspected the code was likely seeing some
motion. Thanks for bringing it forward.
And it's
a good thing, because with
Daniel P. Berrange wrote:
If you loook at src/qemu_conf.c, you'll find a nice method called
qemudExtractVersionInfo, which runs 'qemu -help' and checks for
certain interesting command line arguments :-)
That problem does seem to be crying for some type
of structured interface to avoid subtle
Daniel P. Berrange wrote:
A couple of extra things needed
- Addition to tests/qemuxml2argvtest.c to validate the XML to
struct to QEMU ARGV conversion.
- Addition to tests/qemuxml2xmltest.c to validate XML to
struct to XML round-trip conversions.
- Addition to the docs/libvirt.rng
We have found certain application scenarios where
overriding of the default qemu host cache mode
provides a substantial improvement in guest
performance. In particular, disabling host caching
of the file/dev backing a guest drive. A summary
of performance metrics may be found below.
Attached
11 matches
Mail list logo