From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Prashant Singh" <singhpra@juniper.net>, "Jeremy Kerr" <jk@ozlabs.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jonathan Corbet" <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] efivarfs: avoid slow QueryVariableInfo() in statfs()
Date: Thu, 17 Sep 2026 10:36:26 +0200 [thread overview]
Message-ID: <60d0b7a5-cc1f-4841-b4f2-754e1b921794@app.fastmail.com> (raw)
In-Reply-To: <20260917071600.5587-1-singhpra@juniper.net>
Hello Prashant,
On Thu, 17 Sep 2026, at 09:16, Prashant Singh wrote:
> QueryVariableInfo() is an EFI runtime service that, on some platforms,
> takes tens of milliseconds and runs with preemption disabled, freezing
> the CPU that services it for the whole call. efivarfs_statfs() issued
> this call on every statfs(2) (e.g. every "df"), which produced large
> latency spikes for unrelated latency-sensitive workloads pinned to the
> same CPU.
>
> Commit b2326338dc68 ("efivarfs: Rate limit statfs() handler") already
> bounds the firmware call to twice per second. That helps against a
> statfs() flood, but on a real-time / dataplane system even the residual
> 2 calls/s x ~40ms = up to ~80ms/s of preempt-disabled CPU time is
> unacceptable: any unprivileged process (or a periodic monitoring "df")
> can still inject ~40ms stalls into a co-located latency-sensitive task.
>
Could we instead introduce a mount option that disables used/available
reporting entirely? Feel free to set the default to 'disabled' when
CONFIG_PREEMPT_RT is set.
next prev parent reply other threads:[~2026-09-17 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 7:16 [PATCH] efivarfs: avoid slow QueryVariableInfo() in statfs() Prashant Singh
2026-09-17 8:36 ` Ard Biesheuvel [this message]
2026-09-17 16:50 ` Prashant Singh
2026-09-18 7:40 ` Ard Biesheuvel
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=60d0b7a5-cc1f-4841-b4f2-754e1b921794@app.fastmail.com \
--to=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=jk@ozlabs.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=singhpra@juniper.net \
/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.