From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [PATCH v2 0/6] block: block-status cache for data regions
Date: Wed, 23 Jun 2021 17:01:37 +0200 [thread overview]
Message-ID: <20210623150143.188184-1-mreitz@redhat.com> (raw)
Hi,
See the cover letter from v1 for the general idea:
https://lists.nongnu.org/archive/html/qemu-block/2021-06/msg00843.html
The biggest change here in v2 is that instead of having a common CoMutex
protect the block-status cache, we’re using RCU now. So to read from
the cache, or even to invalidate it, no lock is needed, only to update
it with new data.
Disclaimer: I have no experience with RCU in practice so far, neither in
qemu nor anywhere else. So I hope I’ve used it correctly...
Differences to v1 in detail:
- Patch 2:
- Moved BdrvBlockStatusCache.lock up to BDS, it is now the RCU writer
lock
- BDS.block_status_cache is now a pointer, so it can be replaced with
RCU
- Moved all cache access functionality into helper functions
(bdrv_bsc_is_data(), bdrv_bsc_invalidate_range(), bdrv_bsc_fill())
in block.c
- Guard BSC accesses with RCU
(BSC.valid is to be accessed atomically, which allows resetting it
without taking an RCU write lock)
- Check QLIST_EMPTY(&bs->children) not just when reading from the
cache, but when filling it, too (so we don’t need an RCU update when
it won’t make sense)
- Patch 3: Added
- Dropped the block/nbd patch (because it would make NBD query a larger
range; the patch’s intent was to get more information for free, which
this would not be)
git-backport-diff against v1:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/6:[----] [--] 'block: Drop BDS comment regarding bdrv_append()'
002/6:[0169] [FC] 'block: block-status cache for data regions'
003/6:[down] 'block: Clarify that @bytes is no limit on *pnum'
004/6:[----] [--] 'block/file-posix: Do not force-cap *pnum'
005/6:[----] [--] 'block/gluster: Do not force-cap *pnum'
006/6:[----] [--] 'block/iscsi: Do not force-cap *pnum'
Max Reitz (6):
block: Drop BDS comment regarding bdrv_append()
block: block-status cache for data regions
block: Clarify that @bytes is no limit on *pnum
block/file-posix: Do not force-cap *pnum
block/gluster: Do not force-cap *pnum
block/iscsi: Do not force-cap *pnum
include/block/block_int.h | 54 +++++++++++++++++++++++--
block.c | 84 +++++++++++++++++++++++++++++++++++++++
block/file-posix.c | 7 ++--
block/gluster.c | 7 ++--
block/io.c | 61 ++++++++++++++++++++++++++--
block/iscsi.c | 3 --
6 files changed, 200 insertions(+), 16 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-23 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 15:01 Max Reitz [this message]
2021-06-23 15:01 ` [PATCH v2 1/6] block: Drop BDS comment regarding bdrv_append() Max Reitz
2021-06-23 15:01 ` [PATCH v2 2/6] block: block-status cache for data regions Max Reitz
2021-06-24 10:05 ` Vladimir Sementsov-Ogievskiy
2021-06-24 11:11 ` Max Reitz
2021-07-06 17:04 ` Kevin Wolf
2021-07-12 7:45 ` Max Reitz
2021-06-23 15:01 ` [PATCH v2 3/6] block: Clarify that @bytes is no limit on *pnum Max Reitz
2021-06-24 9:15 ` Vladimir Sementsov-Ogievskiy
2021-06-24 10:16 ` Max Reitz
2021-06-24 10:25 ` Vladimir Sementsov-Ogievskiy
2021-06-24 11:12 ` Max Reitz
2021-06-28 19:10 ` Eric Blake
2021-07-12 7:47 ` Max Reitz
2021-06-23 15:01 ` [PATCH v2 4/6] block/file-posix: Do not force-cap *pnum Max Reitz
2021-06-23 15:01 ` [PATCH v2 5/6] block/gluster: " Max Reitz
2021-06-23 15:01 ` [PATCH v2 6/6] block/iscsi: " Max Reitz
2021-07-06 17:06 ` [PATCH v2 0/6] block: block-status cache for data regions 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=20210623150143.188184-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).