From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: Alex Markuze <amarkuze@redhat.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Cc: Viacheslav Dubeyko <vdubeyko@redhat.com>,
"idryomov@gmail.com" <idryomov@gmail.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 0/3] ceph: add subvolume metrics reporting support
Date: Mon, 1 Dec 2025 20:14:40 +0000 [thread overview]
Message-ID: <2711e9a7e3f01502e122b8d8f38b9b6ae4930e7e.camel@ibm.com> (raw)
In-Reply-To: <20251127134620.2035796-1-amarkuze@redhat.com>
On Thu, 2025-11-27 at 13:46 +0000, Alex Markuze wrote:
> This patch series adds support for per-subvolume I/O metrics collection
> and reporting to the MDS. This enables administrators to monitor I/O
> patterns at the subvolume granularity, which is useful for multi-tenant
> CephFS deployments where different subvolumes may be allocated to
> different users or applications.
>
> The implementation requires protocol changes to receive the subvolume_id
> from the MDS (InodeStat v9), and introduces a new metrics type
> (CLIENT_METRIC_TYPE_SUBVOLUME_METRICS) for reporting aggregated I/O
> statistics back to the MDS.
>
> Patch 1 adds forward-compatible handling for InodeStat v8. The MDS v8
> encoding added a versioned optmetadata field containing optional inode
What is "optmetadata"? Do you mean "opt metadata" here? Does it exact name of
the field?
Thanks,
Slava.
> metadata such as charmap (for case-insensitive/case-preserving file
> systems). The kernel client does not currently support case-insensitive
> lookups, so this field is skipped rather than parsed. This ensures
> forward compatibility with newer MDS servers without requiring the
> full case-insensitivity feature implementation.
>
> Patch 2 adds support for parsing the subvolume_id field from InodeStat
> v9 and storing it in the inode structure for later use.
>
> Patch 3 adds the complete subvolume metrics infrastructure:
> - CEPHFS_FEATURE_SUBVOLUME_METRICS feature flag for MDS negotiation
> - Red-black tree based metrics tracker for efficient per-subvolume
> aggregation
> - Wire format encoding matching the MDS C++ AggregatedIOMetrics struct
> - Integration with the existing CLIENT_METRICS message
> - Recording of I/O operations from file read/write and writeback paths
> - Debugfs interfaces for monitoring
>
> Metrics tracked per subvolume include:
> - Read/write operation counts
> - Read/write byte counts
> - Read/write latency sums (for average calculation)
>
> The metrics are periodically sent to the MDS as part of the existing
> metrics reporting infrastructure when the MDS advertises support for
> the SUBVOLUME_METRICS feature.
>
> Debugfs additions in Patch 3:
> - metrics/subvolumes: displays last sent and pending subvolume metrics
> - metrics/metric_features: displays MDS session feature negotiation
> status, showing which metric-related features are enabled (including
> METRIC_COLLECT and SUBVOLUME_METRICS)
>
> Alex Markuze (3):
> ceph: handle InodeStat v8 versioned field in reply parsing
> ceph: parse subvolume_id from InodeStat v9 and store in inode
> ceph: add subvolume metrics collection and reporting
>
> fs/ceph/Makefile | 2 +-
> fs/ceph/addr.c | 10 +
> fs/ceph/debugfs.c | 153 ++++++++++++++
> fs/ceph/file.c | 58 ++++-
> fs/ceph/inode.c | 19 ++
> fs/ceph/mds_client.c | 89 ++++++--
> fs/ceph/mds_client.h | 14 +-
> fs/ceph/metric.c | 172 ++++++++++++++-
> fs/ceph/metric.h | 27 ++-
> fs/ceph/subvolume_metrics.c | 407 ++++++++++++++++++++++++++++++++++++
> fs/ceph/subvolume_metrics.h | 68 ++++++
> fs/ceph/super.c | 1 +
> fs/ceph/super.h | 3 +
> 13 files changed, 997 insertions(+), 26 deletions(-)
> create mode 100644 fs/ceph/subvolume_metrics.c
> create mode 100644 fs/ceph/subvolume_metrics.h
prev parent reply other threads:[~2025-12-01 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 13:46 [PATCH 0/3] ceph: add subvolume metrics reporting support Alex Markuze
2025-11-27 13:46 ` [PATCH 1/3] ceph: handle InodeStat v8 versioned field in reply parsing Alex Markuze
2025-11-28 1:48 ` kernel test robot
2025-12-01 20:20 ` Viacheslav Dubeyko
2025-12-02 10:39 ` Alex Markuze
2025-11-27 13:46 ` [PATCH 2/3] ceph: parse subvolume_id from InodeStat v9 and store in inode Alex Markuze
2025-12-01 23:27 ` Viacheslav Dubeyko
2025-11-27 13:46 ` [PATCH 3/3] ceph: add subvolume metrics collection and reporting Alex Markuze
2025-11-29 16:51 ` Dan Carpenter
2025-12-01 20:14 ` Viacheslav Dubeyko [this message]
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=2711e9a7e3f01502e122b8d8f38b9b6ae4930e7e.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=vdubeyko@redhat.com \
/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).