From: Stefan Hajnoczi <stefanha@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, famz@redhat.com, eblake@redhat.com,
mreitz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/6] block: Enable byte granularity I/O
Date: Wed, 15 Jun 2016 10:02:51 +0100 [thread overview]
Message-ID: <20160615090251.GA25151@stefanha-x1.localdomain> (raw)
In-Reply-To: <1465911155-19002-1-git-send-email-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
On Tue, Jun 14, 2016 at 03:32:29PM +0200, Kevin Wolf wrote:
> Previous series have already converted some block drivers to byte-based rather
> than sector-based interfaces. However, the common I/O path as well as raw-posix
> still enforced a minimum alignment of 512 bytes because some sector-based logic
> was involved.
>
> This patch series removes these limitations and a sub-sector request actually
> ends up as a sub-sector syscall now.
>
> v2:
> - Updated trace-events for bdrv_co_do_copy_on_readv() [Eric]
> - Added some assertions [Eric]
> - Renamed laio_submit_co() -> laio_co_submit() and added coroutine_fn
> to its prototype [Stefan]
> - linux-aio: Include block/block.h and use BDRV_SECTOR_SIZE instead
> of 512 [Eric]
>
> Kevin Wolf (6):
> block: Byte-based bdrv_co_do_copy_on_readv()
> block: Prepare bdrv_aligned_preadv() for byte-aligned requests
> block: Prepare bdrv_aligned_pwritev() for byte-aligned requests
> raw-posix: Switch to bdrv_co_* interfaces
> raw-posix: Implement .bdrv_co_preadv/pwritev
> block: Don't enforce 512 byte minimum alignment
>
> block.c | 2 +-
> block/io.c | 128 ++++++++++++++++++++++++++------------------------
> block/linux-aio.c | 84 ++++++++++++++++++++++++---------
> block/mirror.c | 10 ++--
> block/raw-aio.h | 3 ++
> block/raw-posix.c | 62 ++++++++++++------------
> include/block/block.h | 10 ++--
> trace-events | 2 +-
> 8 files changed, 176 insertions(+), 125 deletions(-)
>
> --
> 1.8.3.1
>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-15 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 13:32 [Qemu-devel] [PATCH v2 0/6] block: Enable byte granularity I/O Kevin Wolf
2016-06-14 13:32 ` [Qemu-devel] [PATCH v2 1/6] block: Byte-based bdrv_co_do_copy_on_readv() Kevin Wolf
2016-06-14 13:32 ` [Qemu-devel] [PATCH v2 2/6] block: Prepare bdrv_aligned_preadv() for byte-aligned requests Kevin Wolf
2016-06-14 13:32 ` [Qemu-devel] [PATCH v2 3/6] block: Prepare bdrv_aligned_pwritev() " Kevin Wolf
2016-06-14 13:32 ` [Qemu-devel] [PATCH v2 4/6] raw-posix: Switch to bdrv_co_* interfaces Kevin Wolf
2016-06-14 14:10 ` Eric Blake
2016-06-14 13:32 ` [Qemu-devel] [PATCH v2 5/6] raw-posix: Implement .bdrv_co_preadv/pwritev Kevin Wolf
2016-06-14 14:15 ` Eric Blake
2016-06-14 13:32 ` [Qemu-devel] [PATCH v2 6/6] block: Don't enforce 512 byte minimum alignment Kevin Wolf
2016-06-15 9:02 ` Stefan Hajnoczi [this message]
2016-06-15 10:33 ` [Qemu-devel] [PATCH v2 0/6] block: Enable byte granularity I/O Kevin Wolf
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=20160615090251.GA25151@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).