From: "J . Bruce Fields" <bfields@fieldses.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jeff Layton <jlayton@poochiereds.net>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] nfsd: protect concurrent access to nfsd stats counters
Date: Mon, 4 Jan 2021 17:34:13 -0500 [thread overview]
Message-ID: <20210104223413.GB27763@fieldses.org> (raw)
In-Reply-To: <CAOQ4uxg_ZMPp_Huh3RS=bmFzoNtLicFdkoOQfZni9g_o+CBhDg@mail.gmail.com>
On Tue, Jan 05, 2021 at 12:22:27AM +0200, Amir Goldstein wrote:
> On Mon, Jan 4, 2021 at 11:55 PM J . Bruce Fields <bfields@fieldses.org> wrote:
> >
> > Thanks for looking at this, it's long overdue!
> >
> > On Mon, Dec 28, 2020 at 07:03:43PM +0200, Amir Goldstein wrote:
> > > nfsd stats counters can be updated by concurrent nfsd threads without any
> > > protection.
> > >
> > > Convert some nfsd_stats and nfsd_net struct members to use percpu counters.
> > >
> > > There are several members of struct nfsd_stats that are reported in file
> > > /proc/net/rpc/nfsd by never updated. Those have been left untouched.
> >
> > Looking through the history, the code that updated fh_lookup, for
> > example, was removed in 2002.
> >
> > I'd be OK with removing those entirely, maybe just leave a /* deprecated
> > field */ comment where we printk the hard-coded 0's. If somebody wants
> > to know more they can still find the answers in git.
> >
>
> Sure. I can send a followup patch.
>
> > > The longest_chain* members of struct nfsd_net remain unprotected.
> > >
> > > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > > ---
> > > fs/nfsd/netns.h | 20 +++++++----
> > > fs/nfsd/nfs4proc.c | 2 +-
> > > fs/nfsd/nfscache.c | 52 +++++++++++++++++++--------
> > > fs/nfsd/nfsctl.c | 5 ++-
> > > fs/nfsd/nfsfh.c | 2 +-
> > > fs/nfsd/stats.c | 87 ++++++++++++++++++++++++++++++++++++----------
> > > fs/nfsd/stats.h | 42 +++++++++++++++-------
> > > fs/nfsd/vfs.c | 4 +--
> > > 8 files changed, 156 insertions(+), 58 deletions(-)
> > >
> > > diff --git a/fs/nfsd/netns.h b/fs/nfsd/netns.h
> > > index 7346acda9d76..080c5389b2e7 100644
> > > --- a/fs/nfsd/netns.h
> > > +++ b/fs/nfsd/netns.h
> > > @@ -10,6 +10,7 @@
> > >
> > > #include <net/net_namespace.h>
> > > #include <net/netns/generic.h>
> > > +#include <linux/percpu_counter.h>
> > >
> > > /* Hash tables for nfs4_clientid state */
> > > #define CLIENT_HASH_BITS 4
> > > @@ -149,20 +150,25 @@ struct nfsd_net {
> > >
> > > /*
> > > * Stats and other tracking of on the duplicate reply cache.
> > > - * These fields and the "rc" fields in nfsdstats are modified
> > > - * with only the per-bucket cache lock, which isn't really safe
> > > - * and should be fixed if we want the statistics to be
> > > - * completely accurate.
> > > + * The longest_chain* fields are modified with only the per-bucket
> > > + * cache lock, which isn't really safe and should be fixed if we want
> > > + * these statistics to be completely accurate.
> > > */
> > >
> > > /* total number of entries */
> > > atomic_t num_drc_entries;
> > >
> > > + /* Reference to below counters as array for init/destroy */
> > > + struct percpu_counter counters[0];
> >
> > This feels slightly too clever for its own good, but.... OK, I see
> > there's a bunch of initializations to do in the nfsdstats case, and you
> > don't want to open code all that (and its error handling). I guess I
>
> Yeh, look at ceph_metric_init() and imagine what nfsdstats init
> would look like.
>
> > don't have a better idea. Is this a common pattern elsewhere?
> >
>
> Sort of. Inspired by xfsstats and related macros (fs/xfs/xfs_stats.h).
> I have tried several approaches and this one ended up being the
> cleanest and smallest patch.
>
> The cleaner way would be an actual percpu_counter array and
> convert all callers to use enum index to array like the dqstats counters
> (include/linux/quota.h), but IMO current patch is enough.
OK, I can live with that.
--b.
next prev parent reply other threads:[~2021-01-04 22:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 17:03 [PATCH 0/2] Improvements to nfsd stats Amir Goldstein
2020-12-28 17:03 ` [PATCH 1/2] nfsd: protect concurrent access to nfsd stats counters Amir Goldstein
2020-12-28 19:53 ` Chuck Lever
2021-01-04 21:55 ` J . Bruce Fields
2021-01-04 22:22 ` Amir Goldstein
2021-01-04 22:34 ` J . Bruce Fields [this message]
2021-01-05 2:12 ` Chuck Lever
2021-01-05 6:29 ` Amir Goldstein
2020-12-28 17:03 ` [PATCH 2/2] nfsd: report per-export stats Amir Goldstein
2021-01-04 22:49 ` J . Bruce Fields
2021-01-05 6:42 ` Amir Goldstein
2021-01-05 15:34 ` J . Bruce Fields
2021-01-05 15:45 ` Amir Goldstein
2021-01-05 18:32 ` J . Bruce Fields
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=20210104223413.GB27763@fieldses.org \
--to=bfields@fieldses.org \
--cc=amir73il@gmail.com \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@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