mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prashant Singh <singhpra@juniper.net>
To: Ard Biesheuvel <ardb@kernel.org>, 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 09:50:35 -0700	[thread overview]
Message-ID: <20260917165035.15187-1-singhpra@juniper.net> (raw)
In-Reply-To: <60d0b7a5-cc1f-4841-b4f2-754e1b921794@app.fastmail.com>

On Thu, 17 Sep 2026, at 10:36, Ard Biesheuvel wrote:
> 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.

Will do. I'll add a bool mount option (e.g. statfs_capacity) that, when
disabled, skips QueryVariableInfo() in statfs() and reports 0
used/available, defaulting to disabled under CONFIG_PREEMPT_RT.

If you'd rather df still show numbers without the per-statfs firmware
call, I could instead prime the value once at mount and serve that
(stale but non-zero) as a "cached" mode -- i.e. a tri-state option:

  statfs_capacity=live|cached|off
    live   - current behaviour: rate-limited QueryVariableInfo() on statfs()
    cached - prime once at mount, serve the static value (no per-statfs call)
    off    - report 0 used/available (no firmware call at all)

  default: live on non-RT, off on CONFIG_PREEMPT_RT

Happy either way.

Thanks,
Prashant

      reply	other threads:[~2026-09-17 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  7:16 Prashant Singh
2026-09-17  8:36 ` Ard Biesheuvel
2026-09-17 16:50   ` Prashant Singh [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=20260917165035.15187-1-singhpra@juniper.net \
    --to=singhpra@juniper.net \
    --cc=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 \
    /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®