From: Kevin Wolf <kwolf@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] block: align bounce buffers to page
Date: Mon, 16 Feb 2015 11:59:42 +0100 [thread overview]
Message-ID: <20150216105942.GH4079@noname.str.redhat.com> (raw)
In-Reply-To: <1423244272-24887-3-git-send-email-den@openvz.org>
Am 06.02.2015 um 18:37 hat Denis V. Lunev geschrieben:
> The following sequence
> int fd = open(argv[1], O_RDWR | O_CREAT | O_DIRECT, 0644);
> for (i = 0; i < 100000; i++)
> write(fd, buf, 4096);
> performs 5% better if buf is aligned to 4096 bytes.
>
> The difference is quite reliable.
>
> On the other hand we do not want at the moment to enforce bounce
> buffering if guest request is aligned to 512 bytes.
>
> The patch introduces new concept: minimal memory alignment for bounce
> buffers. Original so called "optimal" value is actually minimal required
> value for aligment. Optimal should be set to page size by default.
> There is no driver which should change this default at the moment.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Paolo Bonzini <pbonzini@redhat.com>
> CC: Kevin Wolf <kwolf@redhat.com>
I don't think the subject lines describes the patch correctly. IIUC,
patch 1 introduces a hard enforcement of page size alignment, and this
patch only loosens it again.
Perhaps the order of patches should be changed so that min_mem_alignment
is introduced first (without changes in the behaviour), and only then
opt_mem_alignment is increased.
Kevin
next prev parent reply other threads:[~2015-02-16 10:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 17:37 [Qemu-devel] [PATCH v4 0/1] block: enforce minimal 4096 alignment in qemu_blockalign Denis V. Lunev
2015-02-06 17:37 ` [Qemu-devel] [PATCH 1/2] block, raw-posix: replace 512/4096 constants with proper macros/values Denis V. Lunev
2015-02-16 10:32 ` Kevin Wolf
2015-02-16 10:34 ` Denis V. Lunev
2015-02-06 17:37 ` [Qemu-devel] [PATCH 2/2] block: align bounce buffers to page Denis V. Lunev
2015-02-16 10:59 ` Kevin Wolf [this message]
2015-02-16 11:14 ` Denis V. Lunev
2015-02-13 7:52 ` [Qemu-devel] [PATCH v4 0/1] block: enforce minimal 4096 alignment in qemu_blockalign Denis V. Lunev
-- strict thread matches above, loose matches on Subject: below --
2015-05-04 13:42 [Qemu-devel] [PATCH v5 0/2] " Denis V. Lunev
2015-05-04 13:42 ` [Qemu-devel] [PATCH 2/2] block: align bounce buffers to page Denis V. Lunev
2015-05-12 5:47 [Qemu-devel] [PATCH v6 0/2] block: enforce minimal 4096 alignment in qemu_blockalign Denis V. Lunev
2015-05-12 5:47 ` [Qemu-devel] [PATCH 2/2] block: align bounce buffers to page Denis V. Lunev
2015-05-12 10:27 ` Kevin Wolf
2015-05-12 10:50 ` Paolo Bonzini
2015-05-12 13:40 [Qemu-devel] [PATCH v7 0/2] block: enforce minimal 4096 alignment in qemu_blockalign Denis V. Lunev
2015-05-12 13:41 ` [Qemu-devel] [PATCH 2/2] block: align bounce buffers to page Denis V. Lunev
2015-05-12 14:08 ` Kevin Wolf
2015-05-12 14:20 ` Denis V. Lunev
2015-05-12 14:26 ` Kevin Wolf
2015-05-12 14:26 ` Denis V. Lunev
2015-05-12 14:30 [Qemu-devel] [PATCH v8 0/2] block: enforce minimal 4096 alignment in qemu_blockalign Denis V. Lunev
2015-05-12 14:30 ` [Qemu-devel] [PATCH 2/2] block: align bounce buffers to page Denis V. Lunev
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=20150216105942.GH4079@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=pbonzini@redhat.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).