From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>,
Bart Van Assche <bvanassche@acm.org>,
Christoph Hellwig <hch@lst.de>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Zoned storage and BLK_STS_RESOURCE
Date: Tue, 17 Dec 2024 11:37:31 -0800 [thread overview]
Message-ID: <5fb36d77-44cc-4ad7-8d64-b819bc7ae42a@kernel.org> (raw)
In-Reply-To: <548e98ee-b46e-476a-9d4a-05a60c78b068@kernel.dk>
On 2024/12/17 11:33, Jens Axboe wrote:
> On 12/17/24 12:28 PM, Damien Le Moal wrote:
>> On 2024/12/17 11:25, Bart Van Assche wrote:
>>> On 12/17/24 11:20 AM, Damien Le Moal wrote:
>>>> For a simple fio "--zonemode=zbd --rw=randwrite --numjobs=X" for X > 1
>>>
>>> Please note that this e-mail thread started by discussing a testcase
>>> with --numjobs=1.
>>
>> I missed that. Then io_uring should be fine and behave the same way as libaio.
>> Since it seems to not be working, we may have a bug beyond the recently fixed
>> REQ_NOWAIT handling I think. That needs to be looked at.
>
> Inflight collision, yes that's what I was getting at - there seems to be
> another bug here, and misunderstandings on how io_uring works is causing
> it to be ignored and/or not understood.
OK. Will dig into this because I definitely do not fully understand where the
issue is.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-12-17 19:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 19:24 Zoned storage and BLK_STS_RESOURCE Bart Van Assche
2024-12-16 20:23 ` Damien Le Moal
2024-12-16 20:42 ` Bart Van Assche
2024-12-16 20:54 ` Damien Le Moal
2024-12-16 21:22 ` Bart Van Assche
2024-12-16 22:49 ` Damien Le Moal
2024-12-17 14:56 ` Damien Le Moal
2024-12-19 5:55 ` Christoph Hellwig
2024-12-19 17:07 ` Bart Van Assche
2024-12-17 4:15 ` Christoph Hellwig
2024-12-17 15:04 ` Damien Le Moal
2024-12-17 18:38 ` Bart Van Assche
2024-12-17 18:46 ` Jens Axboe
2024-12-17 18:51 ` Damien Le Moal
2024-12-17 19:07 ` Jens Axboe
2024-12-17 19:20 ` Damien Le Moal
2024-12-17 19:25 ` Bart Van Assche
2024-12-17 19:28 ` Damien Le Moal
2024-12-17 19:33 ` Jens Axboe
2024-12-17 19:37 ` Damien Le Moal [this message]
2024-12-17 19:41 ` Jens Axboe
2024-12-17 19:48 ` Damien Le Moal
2024-12-17 19:54 ` Jens Axboe
2024-12-17 19:58 ` Jens Axboe
2024-12-17 20:59 ` Damien Le Moal
2024-12-17 21:25 ` Jens Axboe
2024-12-18 6:58 ` Christoph Hellwig
2024-12-19 18:04 ` Bart Van Assche
2024-12-21 8:10 ` Christoph Hellwig
2025-01-06 18:54 ` Bart Van Assche
2024-12-19 6:00 ` Christoph Hellwig
2024-12-19 14:50 ` Jens Axboe
2024-12-19 17:12 ` Bart Van Assche
2024-12-19 23:10 ` Damien Le Moal
2025-01-06 20:14 ` Bart Van Assche
2024-12-21 8:13 ` Christoph Hellwig
2024-12-17 19:32 ` Jens Axboe
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=5fb36d77-44cc-4ad7-8d64-b819bc7ae42a@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@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.