From: Jens Axboe <axboe@kernel.dk>
To: Breno Leitao <leitao@debian.org>,
hch@infradead.org, Damien Le Moal <dlemoal@kernel.org>
Cc: kernel-team@meta.com,
"open list:BLOCK LAYER" <linux-block@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] elevator: do not request_module if elevator exists
Date: Fri, 11 Oct 2024 10:02:13 -0600 [thread overview]
Message-ID: <b63b487a-09fc-4519-ae5b-dabf1fcf05b1@kernel.dk> (raw)
In-Reply-To: <20241011154959.3198364-1-leitao@debian.org>
On 10/11/24 9:49 AM, 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")
> Fixes: 734e1a860312 ("block: Prevent deadlocks when switching elevators")
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> Changelog:
> v2:
> * Protecet __elevator_find() by elv_list_lock (Christoph Hellwig)
> v1:
> * https://lore.kernel.org/all/20241010141509.4028059-1-leitao@debian.org/
>
> block/elevator.c | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/block/elevator.c b/block/elevator.c
> index 565807f0b1c7..1ac9be3e47d1 100644
> --- a/block/elevator.c
> +++ b/block/elevator.c
> @@ -106,6 +106,17 @@ static struct elevator_type *__elevator_find(const char *name)
> return NULL;
> }
>
> +static struct elevator_type *elevator_find(const char *name)
> +{
> + struct elevator_type *e;
> +
> + spin_lock(&elv_list_lock);
> + e = __elevator_find(name);
> + spin_unlock(&elv_list_lock);
> +
> + return e;
> +}
Probably just drop this helper. If it's only used in one spot, then we
don't need to add a helper for it.
--
Jens Axboe
next prev parent reply other threads:[~2024-10-11 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 15:49 Breno Leitao
2024-10-11 16:02 ` Jens Axboe [this message]
2024-10-11 16:30 ` 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=b63b487a-09fc-4519-ae5b-dabf1fcf05b1@kernel.dk \
--to=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@infradead.org \
--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
all inboxes | Powered by JetHome®