From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Dave Chinner <david@fromorbit.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH v3 0/6] Generic per-sb io stats
Date: Tue, 1 Mar 2022 20:42:15 +0200 [thread overview]
Message-ID: <20220301184221.371853-1-amir73il@gmail.com> (raw)
Miklos,
Following your feedback on v2 [1], I moved the iostats to per-sb.
Thanks,
Amir.
[1] https://lore.kernel.org/linux-unionfs/20220228113910.1727819-1-amir73il@gmail.com/
Changes since v2:
- Change from per-mount to per-sb io stats (szeredi)
- Avoid percpu loop when reading mountstats (dchinner)
Changes since v1:
- Opt-in for per-mount io stats for overlayfs and fuse
Amir Goldstein (6):
lib/percpu_counter: add helpers for arrays of counters
fs: add optional iostats counters to struct super_block
fs: collect per-sb io stats
fs: report per-sb io stats
ovl: opt-in for per-sb io stats
fuse: opt-in for per-sb io stats
fs/Kconfig | 8 +++
fs/fuse/inode.c | 5 ++
fs/nfsd/export.c | 7 +-
fs/nfsd/nfscache.c | 5 +-
fs/nfsd/stats.c | 37 +---------
fs/nfsd/stats.h | 3 -
fs/overlayfs/super.c | 5 ++
fs/proc_namespace.c | 16 +++++
fs/read_write.c | 88 ++++++++++++++++-------
fs/super.c | 2 +
include/linux/fs.h | 10 ++-
include/linux/fs_iostats.h | 127 +++++++++++++++++++++++++++++++++
include/linux/percpu_counter.h | 28 ++++++++
lib/percpu_counter.c | 27 +++++++
14 files changed, 300 insertions(+), 68 deletions(-)
create mode 100644 include/linux/fs_iostats.h
--
2.25.1
next reply other threads:[~2022-03-01 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 18:42 Amir Goldstein [this message]
2022-03-01 18:42 ` [PATCH v3 1/6] lib/percpu_counter: add helpers for arrays of counters Amir Goldstein
2022-03-01 18:42 ` [PATCH v3 2/6] fs: add optional iostats counters to struct super_block Amir Goldstein
2022-03-01 18:42 ` [PATCH v3 3/6] fs: collect per-sb io stats Amir Goldstein
2022-03-01 18:42 ` [PATCH v3 4/6] fs: report " Amir Goldstein
2022-03-01 18:42 ` [PATCH v3 5/6] ovl: opt-in for " Amir Goldstein
2022-03-01 18:42 ` [PATCH v3 6/6] fuse: " Amir Goldstein
2022-03-02 6:59 ` [PATCH v3 0/6] Generic " Dave Chinner
2022-03-02 7:43 ` Amir Goldstein
2022-03-02 8:26 ` Dave Chinner
2022-03-02 8:34 ` Amir Goldstein
2022-03-02 16:59 ` Amir Goldstein
2022-03-02 21:12 ` Dave Chinner
2022-03-03 6:50 ` 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=20220301184221.371853-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=david@fromorbit.com \
--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).