From: Bart Van Assche <bvanassche@acm.org>
To: Damien Le Moal <dlemoal@kernel.org>, Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] block: Do not merge if merging is disabled
Date: Fri, 7 Jul 2023 06:50:59 -0700 [thread overview]
Message-ID: <cd79cb6c-8bd1-8289-5e96-24003a3159b0@acm.org> (raw)
In-Reply-To: <30620d8b-066f-7357-1d4c-2657d445e286@kernel.org>
On 7/6/23 20:34, Damien Le Moal wrote:
> Ming's point still stands I think: blk_queue_nomerges(q) is the first
> thing checked in elv_attempt_insert_merge(). So your patch should be a
> no-op and disabling merging through sysfs should still be effective. Why
> is your patch changing anything ?
>
> Moving blk_mq_sched_try_insert_merge() call to rq_mergeable(rq) inside
> elv_attempt_insert_merge() would also make a lot of sense I think. With
> that, blk_mq_sched_try_insert_merge() would be reduced to calling only
> elv_attempt_insert_merge(), which means that elv_attempt_insert_merge()
> could go away.
Let's drop this patch. Since this patch was developed against an older
kernel version, let me check whether this patch is perhaps only needed
for the kernel version it was developed against.
Thanks,
Bart.
prev parent reply other threads:[~2023-07-07 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 20:14 [PATCH] block: Do not merge if merging is disabled Bart Van Assche
2023-07-06 23:43 ` Damien Le Moal
2023-07-07 0:38 ` Ming Lei
2023-07-07 1:50 ` Bart Van Assche
2023-07-07 3:34 ` Damien Le Moal
2023-07-07 13:50 ` Bart Van Assche [this message]
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=cd79cb6c-8bd1-8289-5e96-24003a3159b0@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--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