All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Damien Le Moal <dlemoal@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
	Christoph Hellwig <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>
Subject: Re: [PATCH v2 02/12] block: Send flush requests to the I/O scheduler
Date: Tue, 11 Apr 2023 08:38:12 +0200	[thread overview]
Message-ID: <20230411063812.GA19616@lst.de> (raw)
In-Reply-To: <f81541f6-2fba-3d62-bd63-6b00b5cf5f5d@acm.org>

On Mon, Apr 10, 2023 at 05:15:44PM -0700, Bart Van Assche wrote:
> Subject: [PATCH] block: Send flush requests to the I/O scheduler
>
> Send flush requests to the I/O scheduler such that I/O scheduler policies
> are applied to writes with the FUA flag set. Separate the I/O scheduler
> members from the flush members in struct request since with this patch
> applied a request may pass through both an I/O scheduler and the flush
> machinery.
>
> This change affects the statistics of I/O schedulers that track I/O
> statistics (BFQ and mq-deadline).

This looks reasonably to me, as these special cases are nasty.
But we'll need very careful testing, including performance testing
to ensure this doesn't regress.

> +		blk_mq_sched_insert_request(rq, /*at_head=*/false,
> +					    /*run_queue=*/true, /*async=*/true);

And place drop these silly comments.  If you want to do something about
this rather suboptimal interface convert the three booleans to a flags
argument with properly named flags.

> -	if ((rq->rq_flags & RQF_FLUSH_SEQ) || blk_rq_is_passthrough(rq))
> -		return true;
> -
> -	return false;
> +	return req_op(rq) == REQ_OP_FLUSH || blk_rq_is_passthrough(rq);

This just seem like an arbitrary reformatting.  While I also prefer
your new version, I don't think it belongs into this patch.

  reply	other threads:[~2023-04-11  6:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 23:58 [PATCH v2 00/12] Submit zoned writes in order Bart Van Assche
2023-04-07 23:58 ` [PATCH v2 01/12] block: Send zoned writes to the I/O scheduler Bart Van Assche
2023-04-10  7:42   ` Damien Le Moal
2023-04-10 16:35     ` Bart Van Assche
2023-04-07 23:58 ` [PATCH v2 02/12] block: Send flush requests " Bart Van Assche
2023-04-10  7:46   ` Damien Le Moal
2023-04-11  0:15     ` Bart Van Assche
2023-04-11  6:38       ` Christoph Hellwig [this message]
2023-04-11 17:13         ` Bart Van Assche
2023-04-07 23:58 ` [PATCH v2 03/12] block: Send requeued " Bart Van Assche
2023-04-10  7:53   ` Damien Le Moal
2023-04-10 16:59     ` Bart Van Assche
2023-04-11 12:38   ` Christoph Hellwig
2023-04-11 17:17     ` Bart Van Assche
2023-04-11 13:14   ` Christoph Hellwig
2023-04-07 23:58 ` [PATCH v2 04/12] block: Requeue requests if a CPU is unplugged Bart Van Assche
2023-04-10  7:54   ` Damien Le Moal
2023-04-11 12:40   ` Christoph Hellwig
2023-04-11 17:18     ` Bart Van Assche
2023-04-07 23:58 ` [PATCH v2 05/12] block: One requeue list per hctx Bart Van Assche
2023-04-10  7:58   ` Damien Le Moal
2023-04-10 17:04     ` Bart Van Assche
2023-04-07 23:58 ` [PATCH v2 06/12] block: Preserve the order of requeued requests Bart Van Assche
2023-04-10  8:01   ` Damien Le Moal
2023-04-11 12:43   ` Christoph Hellwig
2023-04-07 23:58 ` [PATCH v2 07/12] block: Make it easier to debug zoned write reordering Bart Van Assche
2023-04-10  8:06   ` Damien Le Moal
2023-04-07 23:58 ` [PATCH v2 08/12] block: mq-deadline: Simplify deadline_skip_seq_writes() Bart Van Assche
2023-04-10  8:07   ` Damien Le Moal
2023-04-07 23:58 ` [PATCH v2 09/12] block: mq-deadline: Disable head insertion for zoned writes Bart Van Assche
2023-04-10  8:10   ` Damien Le Moal
2023-04-10 17:09     ` Bart Van Assche
2023-04-11  6:44       ` Christoph Hellwig
2023-04-07 23:58 ` [PATCH v2 10/12] block: mq-deadline: Introduce a local variable Bart Van Assche
2023-04-10  8:11   ` Damien Le Moal
2023-04-07 23:58 ` [PATCH v2 11/12] block: mq-deadline: Fix a race condition related to zoned writes Bart Van Assche
2023-04-10  8:16   ` Damien Le Moal
2023-04-10 17:23     ` Bart Van Assche
2023-04-07 23:58 ` [PATCH v2 12/12] block: mq-deadline: Handle requeued requests correctly Bart Van Assche
2023-04-10  8:32   ` Damien Le Moal
2023-04-10 17:31     ` 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=20230411063812.GA19616@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=snitzer@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.