From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Christoph Hellwig <hch@lst.de>, Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: [PATCH] block: Submit flush requests to the I/O scheduler
Date: Sun, 14 Aug 2022 10:13:16 -0700 [thread overview]
Message-ID: <f4e10a9a-313d-ce24-c610-f4e8d072d4f4@opensource.wdc.com> (raw)
In-Reply-To: <20220813064142.GA10753@lst.de>
On 2022/08/12 23:41, Christoph Hellwig wrote:
> On Fri, Aug 12, 2022 at 02:03:55PM -0700, Bart Van Assche wrote:
>> When submitting a REQ_OP_WRITE | REQ_FUA request to a zoned storage
>> device, these requests must be passed to the (mq-deadline) I/O scheduler
>> to ensure that these happen at the write pointer.
>
> Yes.
>
> But maybe I'm stupid, but how is the patch related to fixing that?
> blk_mq_plug_issue_direct is called from blk_mq_flush_plug_list for
> only the !has_elevator case. How does that change a thing?
And writes to zoned drives never get plugged in the first place, scheduler
present or not.
>
> Also please include a description of why these changes are otherwise
> good and won't regress other cases.
>
>> + blk_mq_sched_insert_request(rq, /*at_head=*/false,
>> + /*run_queue=*/last, /*async=*/false);
>
> I find thise comment style very hard to read. Yes, maybe the three
> bools here should become flags, but this is even worse than just
> passing the arguments.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-08-14 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 21:03 [PATCH] block: Submit flush requests to the I/O scheduler Bart Van Assche
2022-08-13 6:41 ` Christoph Hellwig
2022-08-14 17:13 ` Damien Le Moal [this message]
2022-08-14 23:44 ` Bart Van Assche
2022-08-15 9:06 ` Pankaj Raghav
2022-08-15 16:31 ` 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=f4e10a9a-313d-ce24-c610-f4e8d072d4f4@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@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