From: Christoph Hellwig <hch@infradead.org>
To: Breno Leitao <leitao@debian.org>
Cc: Jens Axboe <axboe@kernel.dk>,
kernel-team@meta.com,
"open list:BLOCK LAYER" <linux-block@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] elevator: do not request_module if elevator exists
Date: Fri, 11 Oct 2024 01:24:15 -0700 [thread overview]
Message-ID: <ZwjgrwSw2vUVP2cp@infradead.org> (raw)
In-Reply-To: <20241010141509.4028059-1-leitao@debian.org>
On Thu, Oct 10, 2024 at 07:15:08AM -0700, Breno Leitao wrote:
> Whenever an I/O elevator is changed, the system attempts to load a
> module for the new elevator. This occurs regardless of whether the
> elevator is already loaded or built directly into the kernel. This
> behavior introduces unnecessary overhead and potential issues.
>
> This makes the operation slower, and more error-prone. For instance,
> making the problem fixed by [1] visible for users that doesn't even rely
> on modules being available through modules.
>
> Do not try to load the ioscheduler if it is already visible.
>
> This change brings two main benefits: it improves the performance of
> elevator changes, and it reduces the likelihood of errors occurring
> during this process.
>
> [1] Commit e3accac1a976 ("block: Fix elv_iosched_local_module handling of "none" scheduler")
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> block/elevator.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/block/elevator.c b/block/elevator.c
> index 4122026b11f1..1904e217505a 100644
> --- a/block/elevator.c
> +++ b/block/elevator.c
> @@ -709,13 +709,16 @@ int elv_iosched_load_module(struct gendisk *disk, const char *buf,
> size_t count)
> {
> char elevator_name[ELV_NAME_MAX];
> + const char *name;
>
> if (!elv_support_iosched(disk->queue))
> return -EOPNOTSUPP;
>
> strscpy(elevator_name, buf, sizeof(elevator_name));
> + name = strstrip(elevator_name);
>
> - request_module("%s-iosched", strstrip(elevator_name));
> + if (!__elevator_find(name))
__elevator_find needs to be called with elv_list_lock.
next prev parent reply other threads:[~2024-10-11 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 14:15 [PATCH] elevator: do not request_module if elevator exists Breno Leitao
2024-10-10 16:40 ` Jens Axboe
2024-10-11 8:24 ` Christoph Hellwig [this message]
2024-10-11 12:37 ` Breno Leitao
2024-10-11 13:12 ` Jens Axboe
2024-10-11 13:17 ` Breno Leitao
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=ZwjgrwSw2vUVP2cp@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox