From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-unionfs@vger.kernel.org, containers@lists.linux.dev,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 5/6] ovl: opt-in for per-mount io stats
Date: Mon, 28 Feb 2022 13:39:09 +0200 [thread overview]
Message-ID: <20220228113910.1727819-6-amir73il@gmail.com> (raw)
In-Reply-To: <20220228113910.1727819-1-amir73il@gmail.com>
Traditionally, system administrators have used the iostat utility
to track the amount of io performed to a local disk filesystem.
Similar functionality is provided for NFS mounts via the nfsstat
utility that reads the NFS client's stats from /proc/pid/mountstats.
There is currently no good way for a system administrator or a
monitoring application inside a container to track the amount of io
performed via overlayfs.
Opt-in for generic io stats via /proc/pid/mountstats to provide
that functionality.
This feature depends on CONFIG_MOUNT_IO_STATS.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
fs/overlayfs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index 7bb0a47cb615..802e4ed567cc 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -2165,7 +2165,7 @@ static struct dentry *ovl_mount(struct file_system_type *fs_type, int flags,
static struct file_system_type ovl_fs_type = {
.owner = THIS_MODULE,
.name = "overlay",
- .fs_flags = FS_USERNS_MOUNT,
+ .fs_flags = FS_USERNS_MOUNT | FS_MOUNT_STATS,
.mount = ovl_mount,
.kill_sb = kill_anon_super,
};
--
2.25.1
next prev parent reply other threads:[~2022-02-28 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 11:39 [PATCH v2 0/6] Generic per-mount io stats Amir Goldstein
2022-02-28 11:39 ` [PATCH v2 1/6] fs: add iostats counters to struct mount Amir Goldstein
2022-02-28 11:39 ` [PATCH v2 2/6] fs: tidy up fs_flags definitions Amir Goldstein
2022-02-28 11:39 ` [PATCH v2 3/6] fs: collect per-mount io stats Amir Goldstein
2022-02-28 11:39 ` [PATCH v2 4/6] fs: report " Amir Goldstein
2022-02-28 15:06 ` Miklos Szeredi
2022-02-28 16:18 ` Amir Goldstein
2022-02-28 16:31 ` Miklos Szeredi
2022-02-28 17:06 ` Amir Goldstein
2022-02-28 21:11 ` Dave Chinner
2022-02-28 21:57 ` Amir Goldstein
2022-03-01 9:46 ` Dave Chinner
2022-03-01 10:56 ` Amir Goldstein
2022-02-28 11:39 ` Amir Goldstein [this message]
2022-02-28 11:39 ` [PATCH v2 6/6] fuse: opt-in for " Amir Goldstein
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=20220228113910.1727819-6-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=containers@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).