From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, fam@euphon.net, vsementsov@virtuozzo.com,
mreitz@redhat.com, stefanha@redhat.com, den@openvz.org,
jsnow@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/3] block: BDRV_REQ_PREFETCH
Date: Tue, 18 Jun 2019 18:41:59 +0300 [thread overview]
Message-ID: <20190618154202.89107-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Here is small new read flag: BDRV_REQ_PREFETCH, which in combination with
BDRV_REQ_COPY_ON_READ does copy-on-read without
extra buffer for read data. This means that only parts that needs COR
will be actually read and only corresponding buffers allocated, no more.
This allows to improve a bit block-stream and NBD_CMD_CACHE
v2: change interface to be just one flag BDRV_REQ_PREFETCH
v1 was "[PATCH 0/3] block: blk_co_pcache"
https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg01047.html
Vladimir Sementsov-Ogievskiy (3):
block: implement BDRV_REQ_PREFETCH
block/stream: use BDRV_REQ_PREFETCH
nbd: improve CMD_CACHE: use blk_co_pcache
include/block/block.h | 8 +++++++-
block/io.c | 18 ++++++++++++------
block/stream.c | 20 +++++++-------------
nbd/server.c | 43 +++++++++++++++++++++++++++++++++++--------
4 files changed, 61 insertions(+), 28 deletions(-)
--
2.18.0
next reply other threads:[~2019-06-18 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 15:41 Vladimir Sementsov-Ogievskiy [this message]
2019-06-18 15:42 ` [Qemu-devel] [PATCH v2 1/3] block: implement BDRV_REQ_PREFETCH Vladimir Sementsov-Ogievskiy
2019-06-18 15:42 ` [Qemu-devel] [PATCH v2 2/3] block/stream: use BDRV_REQ_PREFETCH Vladimir Sementsov-Ogievskiy
2019-06-18 15:42 ` [Qemu-devel] [PATCH v2 3/3] nbd: improve CMD_CACHE: use blk_co_pcache Vladimir Sementsov-Ogievskiy
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=20190618154202.89107-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@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).