From: Elliott Mitchell <ehem+xen@m5p.com>
To: xen-devel@lists.xenproject.org
Cc: Wei Liu <wl@xen.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>
Subject: [PATCH 00/10] Increase consistency of domain examples
Date: Tue, 19 Apr 2022 19:10:17 -0700 [thread overview]
Message-ID: <cover.1650420617.git.ehem+xen@m5p.com> (raw)
The "xlexample.*" files have drifted apart rather distinctly. This may
cause puzzlement at why the distinct choices were made. Worse, I have an
unpleasant suspicion a naive user could benchmark with these files and
not realize performance differences were due to different settings, not
the domain type.
I chose 3 vCPUs and 384MB of memory. This is in-between the values
currently in the examples. I wonder whether I should have used the
values from pvhlinux as those may better reflect typical small VMs now.
Elliott Mitchell (10):
docs: xlexample.hvm: Mention this isn't useful for other guests
docs: xlexample.*: Use consistent vCPU count
docs: xlexample.*: Use consistent initial memory
docs: xlexample.pvhlinux: Add commented maxmem setting
docs: xlexample.hvm: Fix maxmem value
docs: xlexample.hvm: Add reference to nographic option
docs: xlexample.pvhlinux: Make disk setting consistent with other
examples
docs: xlexample.hvm: Fix grammmer
docs: xlexample.pvlinux: Add "type" setting
docs: xlexample.pvhlinux: Use similar text to other examples
tools/examples/xlexample.hvm | 19 ++++++++++---------
tools/examples/xlexample.pvhlinux | 13 +++++++++----
tools/examples/xlexample.pvlinux | 7 +++++--
3 files changed, 24 insertions(+), 15 deletions(-)
--
2.30.2
next reply other threads:[~2022-04-20 2:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 2:10 Elliott Mitchell [this message]
2021-01-09 17:52 ` [PATCH 01/10] docs: xlexample.hvm: Mention this isn't useful for other guests Elliott Mitchell
2021-01-09 17:54 ` [PATCH 02/10] docs: xlexample.*: Use consistent vCPU count Elliott Mitchell
2021-01-09 17:58 ` [PATCH 03/10] docs: xlexample.*: Use consistent initial memory Elliott Mitchell
2021-01-09 18:01 ` [PATCH 04/10] docs: xlexample.pvhlinux: Add commented maxmem setting Elliott Mitchell
2021-01-09 20:08 ` [PATCH 06/10] docs: xlexample.hvm: Add reference to nographic option Elliott Mitchell
2021-01-09 20:11 ` [PATCH 07/10] docs: xlexample.pvhlinux: Make disk setting consistent with other examples Elliott Mitchell
2021-01-09 20:13 ` [PATCH 08/10] docs: xlexample.hvm: Fix grammmer Elliott Mitchell
2021-01-09 20:16 ` [PATCH 09/10] docs: xlexample.pvlinux: Add "type" setting Elliott Mitchell
2021-01-09 20:20 ` [PATCH 10/10] docs: xlexample.pvhlinux: Use similar text to other examples Elliott Mitchell
2021-01-09 22:44 ` [PATCH 05/10] docs: xlexample.hvm: Fix maxmem value Elliott Mitchell
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=cover.1650420617.git.ehem+xen@m5p.com \
--to=ehem+xen@m5p.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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.