[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <173194219548.79489.7363996743894936823.b4-ty@oracle.com>
Date: Mon, 18 Nov 2024 10:03:50 -0500
From: cel@...nel.org
To: Neil Brown <neilb@...e.de>,
Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>,
Jeff Layton <jlayton@...nel.org>
Cc: Chuck Lever <chuck.lever@...cle.com>,
Olga Kornievskaia <okorniev@...hat.com>,
linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] nfsd: allow for up to 32 callback session slots
From: Chuck Lever <chuck.lever@...cle.com>
On Mon, 18 Nov 2024 09:54:34 -0500, Jeff Layton wrote:
> nfsd currently only uses a single slot in the callback channel, which is
> proving to be a bottleneck in some cases. Widen the callback channel to
> a max of 32 slots (subject to the client's target_maxreqs value).
>
> Change the cb_holds_slot boolean to an integer that tracks the current
> slot number (with -1 meaning "unassigned"). Move the callback slot
> tracking info into the session. Add a new u32 that acts as a bitmap to
> track which slots are in use, and a u32 to track the latest callback
> target_slotid that the client reports. To protect the new fields, add
> a new per-session spinlock (the se_lock). Fix nfsd41_cb_get_slot to always
> search for the lowest slotid (using ffs()).
>
> [...]
Applied to nfsd-next for v6.13, thanks!
[1/1] nfsd: allow for up to 32 callback session slots
commit: a47e0534dc9cc3f9ee7c914cfddd6912855b5d61
--
Chuck Lever
Powered by blists - more mailing lists