From: "Chuck Lever" <cel@kernel.org>
To: "Benjamin Coddington" <ben.coddington@hammerspace.com>
Cc: "Jeff Layton" <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
linux-nfs@vger.kernel.org, "Daire Byrne" <daire@dneg.com>
Subject: Re: [PATCH RFC 0/2] SUNRPC: dispatch ready transports round-robin across clients
Date: Mon, 05 Oct 2026 13:21:23 -0400 [thread overview]
Message-ID: <347a4b4f-8860-48c4-9d21-9f2a0c7ca229@app.fastmail.com> (raw)
In-Reply-To: <05C0FB93-B5F1-41C7-9559-C4E6554CE8A7@hammerspace.com>
On Mon, Oct 5, 2026, at 10:46 AM, Benjamin Coddington wrote:
> I know all three of you said no tunables in June. I'd put this closer to
> exports than to a tunable: it tells the server who is who. Neil floated
> an export flag for marking clients on the first thread. I'd do it through
> the nfsd netlink interface so it's per-net and not a module parameter.
I'm not sure how an admin would set such a tunable for a workload that
has to handle more than one of the fairness behaviors.
Scheduling, like getting old, is hard.
> It does raise the bar on the cost question. If nothing is configured then
> everyone pays for the two-level queue and gets nothing for it, so the
> answer on your "alone" numbers has to be zero, not small.
>
> Would you take something like that? I'd rather ask before I build it.
The "take/reject" question is answered by looking at patches and test
results, neither of which exist before a prototype is built. The best I
can do a priori is to say "that looks promising or that might suck."
I'll try to think about it more.
--
Chuck Lever (Come to NFS bake-a-thon! https://nfsv4bat.org)
next prev parent reply other threads:[~2026-10-05 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 16:42 [PATCH RFC 0/2] SUNRPC: dispatch ready transports round-robin across clients Benjamin Coddington
2026-10-02 16:42 ` [PATCH RFC 1/2] SUNRPC: track service clients by peer address Benjamin Coddington
2026-10-02 16:42 ` [PATCH RFC 2/2] SUNRPC: dispatch ready transports round-robin across clients Benjamin Coddington
2026-10-04 20:48 ` [PATCH RFC 0/2] " Chuck Lever
2026-10-05 14:46 ` Benjamin Coddington
2026-10-05 17:21 ` Chuck Lever [this message]
2026-10-06 18:07 ` Benjamin Coddington
2026-10-07 14:15 ` Chuck Lever
2026-10-07 14:30 ` Benjamin Coddington
2026-10-05 12:18 ` Daire Byrne
2026-10-05 14:39 ` Benjamin Coddington
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=347a4b4f-8860-48c4-9d21-9f2a0c7ca229@app.fastmail.com \
--to=cel@kernel.org \
--cc=ben.coddington@hammerspace.com \
--cc=daire@dneg.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
/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