From: Alexey Dobriyan <adobriyan@gmail.com>
To: axboe@kernel.dk
Cc: fio@vger.kernel.org, Damien.LeMoal@wdc.com
Subject: [PATCH v2] fio: fix interaction between offset/size limited threads and "max_open_zones"
Date: Wed, 25 Mar 2020 20:52:48 +0300 [thread overview]
Message-ID: <20200325175248.GA18527@avx2> (raw)
In-Reply-To: <CO2PR04MB234395285948F0249B2485F0E7F10@CO2PR04MB2343.namprd04.prod.outlook.com>
If thread bumps into "max_open_zones" limit, it tries to close/reopen some
other zone before issuing IO. This scan is done over full list of block device's
opened zones. It means that a zone which doesn't belong to thread's working
area can be altered or IO can be retargeted at such zone.
If IO is retargeted, then it will be dropped by "is_valid_offset()" check.
What happens with null block device testing is that one thread monopolises
IO and others thread do basically nothing.
This config will reliably succeed now:
[global]
zonemode=zbd
zonesize=1M
rw=randwrite
...
thread
numjobs=2
offset_increment=128M
[j]
max_open_zones=2
size=2M
Starting 2 threads
zbd 7991 /dev/nullb0: zbd model string: host-managed
zbd 7991 Device /dev/nullb0 has 1024 zones of size 1024 KB
zbd 8009 /dev/nullb0: examining zones 0 .. 2
zbd 8010 /dev/nullb0: examining zones 128 .. 130
zbd 8009 /dev/nullb0: opening zone 0
zbd 8010 /dev/nullb0: opening zone 128
zbd 8009 /dev/nullb0: queued I/O (0, 4096) for zone 0
zbd 8009 zbd_convert_to_open_zone(/dev/nullb0): starting from zone 128 (offset 1552384, buflen 4096)
retargeted for other thread's zone (zone 0 => zone 128)
zbd 8010 /dev/nullb0: queued I/O (134217728, 4096) for zone 128
zbd 8009 zbd_convert_to_open_zone(/dev/nullb0): returning zone 128
zbd 8009 Dropped request with offset 134221824
and dropped
Signed-off-by: Alexey Dobriyan (SK hynix) <adobriyan@gmail.com>
---
zbd.c | 35 ++++++++++++++++++++++++++++++-----
1 file changed, 30 insertions(+), 5 deletions(-)
--- a/zbd.c
+++ b/zbd.c
@@ -969,9 +969,8 @@ static struct fio_zone_info *zbd_convert_to_open_zone(struct thread_data *td,
* This statement accesses f->zbd_info->open_zones[] on purpose
* without locking.
*/
- zone_idx = f->zbd_info->open_zones[(io_u->offset -
- f->file_offset) *
- f->zbd_info->num_open_zones / f->io_size];
+ uint32_t tmp = io_u->offset * f->zbd_info->num_open_zones / f->real_file_size;
+ zone_idx = f->zbd_info->open_zones[tmp];
} else {
zone_idx = zbd_zone_idx(f, io_u->offset);
}
@@ -985,6 +984,8 @@ static struct fio_zone_info *zbd_convert_to_open_zone(struct thread_data *td,
* has been obtained. Hence the loop.
*/
for (;;) {
+ uint32_t tmp;
+
z = &f->zbd_info->zone_info[zone_idx];
zone_lock(td, z);
@@ -998,9 +999,33 @@ static struct fio_zone_info *zbd_convert_to_open_zone(struct thread_data *td,
__func__, f->file_name);
return NULL;
}
- open_zone_idx = (io_u->offset - f->file_offset) *
- f->zbd_info->num_open_zones / f->io_size;
+
+ /*
+ * List of opened zones is per-device, shared across all threads.
+ * Start with quasi-random candidate zone.
+ * Ignore zones which don't belong to thread's offset/size area.
+ */
+ open_zone_idx = io_u->offset * f->zbd_info->num_open_zones / f->real_file_size;
assert(open_zone_idx < f->zbd_info->num_open_zones);
+ for (tmp = open_zone_idx, i = 0; i < f->zbd_info->num_open_zones; i++, tmp++) {
+ uint32_t tmpz;
+
+ if (tmp >= f->zbd_info->num_open_zones)
+ tmp = 0;
+ tmpz = f->zbd_info->open_zones[tmp];
+
+ if (is_valid_offset(f, f->zbd_info->zone_info[tmpz].start)) {
+ open_zone_idx = tmp;
+ goto found_candidate_zone;
+ }
+
+ }
+
+ dprint(FD_ZBD, "%s(%s): no candidate zone\n",
+ __func__, f->file_name);
+ return NULL;
+
+found_candidate_zone:
new_zone_idx = f->zbd_info->open_zones[open_zone_idx];
if (new_zone_idx == zone_idx)
break;
next prev parent reply other threads:[~2020-03-25 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 18:06 [PATCH] fio: fix interaction between offset/size limited threads and "max_open_zones" Alexey Dobriyan
2020-03-24 1:00 ` Damien Le Moal
2020-03-25 17:52 ` Alexey Dobriyan [this message]
2020-03-28 8:34 ` [PATCH v2] " Damien Le Moal
2020-03-31 8:07 ` Damien Le Moal
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=20200325175248.GA18527@avx2 \
--to=adobriyan@gmail.com \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.