On Mon, 2023-07-10 at 22:43 +0000, Chuck Lever III wrote: > > > On Jul 10, 2023, at 6:30 PM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > > > On Tue, 2023-07-11 at 08:18 +1000, NeilBrown wrote: > > > On Tue, 11 Jul 2023, Chuck Lever wrote: > > > > > > > > Actually... Lorenzo reminded me that we need to retain a mechanism > > > > that can iterate through all the threads in a pool. The xarray > > > > replaces the "all_threads" list in this regard. > > > > > > > > > > For what purpose? > > > > > > > He's working on a project to add a rpc status procfile which shows in- > > flight requests: > > > > https://bugzilla.linux-nfs.org/show_bug.cgi?id=366 > > Essentially, we want a lightweight mechanism for detecting > unresponsive nfsd threads. > ...and personally, it would also be nice to have a "nfstop" program or something that could repeatedly poll this file and display information about active nfsd threads. I could also see this being useful for admins who want quick visibility into nfsd's activity, without having to sniff traffic. -- Jeff Layton <jlayton@xxxxxxxxxx>
