From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] block: byte-based blocking read/write
Date: Thu, 26 Apr 2018 08:43:02 -0500 [thread overview]
Message-ID: <20180426134305.642080-1-eblake@redhat.com> (raw)
A logical followup to my other recent cleanups. The only remaining
mention of sectors in block.h APIs is in bdrv_nb_sectors()
(converting those callers to bdrv_getlength() not only requires more
work, but would be our opportunity to see if we could quit rounding
block sizes to sector boundaries for byte-based protocols that can
actually report an exact unaligned size) and for computing geometries
(where it actually makes sense).
Based-on: <20180424192506.149089-1-eblake@redhat.com>
([PATCH v2 0/6] block: byte-based AIO read/write)
Based-on: <20180426025129.621969-1-eblake@redhat.com>
([PATCH v6 0/6] minor qcow2 compression improvements)
Eric Blake (3):
vdi: Switch to byte-based calls
vvfat: Switch to byte-based calls
block: Removed unused sector-based blocking I/O
include/block/block.h | 4 ----
block/io.c | 48 ++++++++----------------------------------------
block/vdi.c | 14 +++++++-------
block/vvfat.c | 20 +++++++++++---------
4 files changed, 26 insertions(+), 60 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-26 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 13:43 Eric Blake [this message]
2018-04-26 13:43 ` [Qemu-devel] [PATCH 1/3] vdi: Switch to byte-based calls Eric Blake
2018-04-27 13:52 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-04-26 13:43 ` [Qemu-devel] [PATCH 2/3] vvfat: " Eric Blake
2018-04-27 13:59 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-04-26 13:43 ` [Qemu-devel] [PATCH 3/3] block: Removed unused sector-based blocking I/O Eric Blake
2018-04-27 14:01 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-04-27 15:43 ` Eric Blake
2018-05-03 13:36 ` Alberto Garcia
2018-11-14 17:30 ` Eric Blake
2018-05-08 12:45 ` Stefan Hajnoczi
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=20180426134305.642080-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@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).