From: Damien Le Moal <dlemoal@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v18 05/12] blk-zoned: Add an argument to blk_zone_plug_bio()
Date: Thu, 26 Jun 2025 09:15:10 +0900 [thread overview]
Message-ID: <92be4ac8-df7c-440f-af6c-df611ecddb76@kernel.org> (raw)
In-Reply-To: <20250616223312.1607638-6-bvanassche@acm.org>
On 6/17/25 07:33, Bart Van Assche wrote:
> Prepare for preserving the order of pipelined zoned writes per zone.
I do not understand why that is needed. And the commit message does not explain
anything.
I suspect it is to handle the case where a submitter changes CPU when issuing
writes to a zone. But if that is the case, you should be able to hide that
explicit CPU choice within the blk-zoned code instead of exposing it through the
API. E.g.: plug the bio and schedule the BIO work to run on the CPU you want.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-06-26 0:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 22:33 [PATCH v18 00/12] Improve write performance for zoned UFS devices Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 01/12] block: Support block drivers that preserve the order of write requests Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 02/12] block: Rework request allocation in blk_mq_submit_bio() Bart Van Assche
2025-06-26 0:00 ` Damien Le Moal
2025-06-26 17:25 ` Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 03/12] block: Support allocating from a specific software queue Bart Van Assche
2025-06-26 0:04 ` Damien Le Moal
2025-06-26 17:17 ` Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 04/12] blk-mq: Restore the zoned write order when requeuing Bart Van Assche
2025-06-26 0:11 ` Damien Le Moal
2025-06-26 19:42 ` Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 05/12] blk-zoned: Add an argument to blk_zone_plug_bio() Bart Van Assche
2025-06-17 12:49 ` kernel test robot
2025-06-26 0:15 ` Damien Le Moal [this message]
2025-06-26 17:16 ` Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 06/12] blk-zoned: Support pipelining of zoned writes Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 07/12] null_blk: Add the preserves_write_order attribute Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 08/12] scsi: core: Retry unaligned zoned writes Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 09/12] scsi: sd: Increase retry count for " Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 10/12] scsi: scsi_debug: Add the preserves_write_order module parameter Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 11/12] scsi: scsi_debug: Support injecting unaligned write errors Bart Van Assche
2025-06-16 22:33 ` [PATCH v18 12/12] scsi: ufs: Inform the block layer about write ordering Bart Van Assche
2025-06-17 6:58 ` Avri Altman
2025-06-19 12:49 ` Peter Wang (王信友)
2025-06-19 16:38 ` Bart Van Assche
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=92be4ac8-df7c-440f-af6c-df611ecddb76@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@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.