qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, jcody@redhat.com, famz@redhat.com,
	stefanha@redhat.com, mreitz@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/8] block: more byte-based cleanups: vectored I/O
Date: Fri, 29 Jun 2018 10:09:25 +0200	[thread overview]
Message-ID: <20180629080925.GB15588@localhost.localdomain> (raw)
In-Reply-To: <20180628201525.281787-1-eblake@redhat.com>

Am 28.06.2018 um 22:15 hat Eric Blake geschrieben:
> My quest continues.  I spent some time pruning sector-based usage
> out of qcow as far as possible (and was dismayed at how long it
> took to prove no iotests regressions); so for the other drivers, I
> did the bare minimum to get rid of an interface, but will leave it
> to those file owners if they want to get rid of further pointless
> sector manipulations in their files.

Thanks, applied to the block branch.

Kevin

      parent reply	other threads:[~2018-06-29  8:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 20:15 [Qemu-devel] [PATCH v3 0/8] block: more byte-based cleanups: vectored I/O Eric Blake
2018-06-28 20:15 ` [Qemu-devel] [PATCH v3 1/8] parallels: Switch to byte-based calls Eric Blake
2018-06-28 20:15 ` [Qemu-devel] [PATCH v3 2/8] qcow: Switch get_cluster_offset to be byte-based Eric Blake
2018-06-28 20:15 ` [Qemu-devel] [PATCH v3 3/8] qcow: Switch qcow_co_readv to byte-based calls Eric Blake
2018-06-28 20:15 ` [Qemu-devel] [PATCH v3 4/8] qcow: Switch qcow_co_writev " Eric Blake
2018-06-28 20:15 ` [Qemu-devel] [PATCH v3 5/8] qcow: Switch to a byte-based driver Eric Blake
2018-06-28 20:15 ` [Qemu-devel] [PATCH v3 6/8] replication: Switch to byte-based calls Eric Blake
2018-06-28 20:15 ` [Qemu-devel] [PATCH v3 7/8] vhdx: " Eric Blake
2018-06-28 20:15 ` [Qemu-devel] [PATCH v3 8/8] block: Remove unused sector-based vectored I/O Eric Blake
2018-06-29  8:09 ` Kevin Wolf [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=20180629080925.GB15588@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).