Linux NFS development
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-nfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/2] Make nfs and nfsd stats visible in network ns
Date: Wed, 24 Jan 2024 14:36:58 -0500	[thread overview]
Message-ID: <cover.1706124811.git.josef@toxicpanda.com> (raw)

Hello,

We're currently deploying NFS internally and have run into some oddities with
our usage of containers.  All of the services that mount and export NFS volumes
run inside of containers, specifically all the namespaces including network
namespaces.  Our monitoring is done on a per-container basis, so we need access
to the nfs and nfsd stats that are under /proc/net/sunrpc.  However these are
only tied to the init_net, which makes them invisible to containers in a
different network namespace.

Fix this so that these files are tied to the network namespace.  This allows us
to avoid the hack of bind mounting the hosts /proc into the container in order
to do proper monitoring.  Thanks,

Josef

Josef Bacik (2):
  nfs: expose /proc/net/sunrpc/nfs in net namespaces
  nfsd: expose /proc/net/sunrpc/nfsd in net namespaces

 fs/nfs/inode.c   |  6 ++----
 fs/nfsd/nfsctl.c |  8 +++++---
 fs/nfsd/stats.c  | 21 ++++++---------------
 fs/nfsd/stats.h  |  6 ++++--
 4 files changed, 17 insertions(+), 24 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-01-24 19:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 19:36 Josef Bacik [this message]
2024-01-24 19:36 ` [PATCH 1/2] nfs: expose /proc/net/sunrpc/nfs in net namespaces Josef Bacik
2024-01-24 19:37 ` [PATCH 2/2] nfsd: expose /proc/net/sunrpc/nfsd " Josef Bacik
2024-01-24 20:32   ` Chuck Lever
2024-01-24 21:05     ` Josef Bacik
2024-01-24 22:12     ` Josef Bacik
2024-01-24 22:57       ` Jeff Layton
2024-01-24 23:18         ` Josef Bacik
2024-01-24 23:41           ` Jeff Layton
2024-01-24 23:47             ` Chuck Lever
2024-01-25  0:06               ` Jeff Layton
2024-01-25  1:54                 ` Chuck Lever III
2024-01-25 10:25                   ` Jeff Layton

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=cover.1706124811.git.josef@toxicpanda.com \
    --to=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --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