From: Eric Blake <eblake@redhat.com>
To: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Cc: p.fedin@samsung.com
Subject: Re: [Qemu-devel] [PATCH] doc: document ivshmem & hugepages
Date: Wed, 7 Oct 2015 09:12:35 -0600 [thread overview]
Message-ID: <56153663.6020606@redhat.com> (raw)
In-Reply-To: <1444228339-18636-1-git-send-email-marcandre.lureau@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On 10/07/2015 08:32 AM, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Document and give some examples of hugepages support with ivshmem device
> and server.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> qemu-doc.texi | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/qemu-doc.texi b/qemu-doc.texi
> index afa2263..b15c14c 100644
> --- a/qemu-doc.texi
> +++ b/qemu-doc.texi
> @@ -1293,6 +1293,19 @@ copy the shared memory on migration to the destination host. With
> With the @option{peer} case, the device should be detached and then reattached
> after migration using the PCI hotplug support.
>
> +@subsubsection ivshmem & hugepages
s/&/and/ (documentation looks a bit too casual if you don't spell out
conjunctions)
> +
> +Instead of specifying the <shm size> using POSIX shm, you may specify
> +a memory backend, that has hugepage support:
s/backend,/backend/
With those two fixes, the grammar is:
Reviewed-by: Eric Blake <eblake@redhat.com>
I don't know if it is technically accurate, though.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-10-07 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 14:32 [Qemu-devel] [PATCH] doc: document ivshmem & hugepages marcandre.lureau
2015-10-07 15:12 ` Eric Blake [this message]
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=56153663.6020606@redhat.com \
--to=eblake@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=p.fedin@samsung.com \
--cc=qemu-devel@nongnu.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).