From: Jeff Layton <jlayton@kernel.org>
To: xiubli@redhat.com
Cc: sage@redhat.com, idryomov@gmail.com, gfarnum@redhat.com,
zyan@redhat.com, pdonnell@redhat.com, ceph-devel@vger.kernel.org
Subject: Re: [PATCH v10 0/6] ceph: add perf metrics support
Date: Wed, 18 Mar 2020 12:01:02 -0400 [thread overview]
Message-ID: <ea5551cf7c7e18b5baf6ec990ae1eddedc62ddce.camel@kernel.org> (raw)
In-Reply-To: <1584540356-5885-1-git-send-email-xiubli@redhat.com>
On Wed, 2020-03-18 at 10:05 -0400, xiubli@redhat.com wrote:
> From: Xiubo Li <xiubli@redhat.com>
>
> Changed in V10:
> - rebase to the latest testing branch
> - merge all the metric related patches into one
> - [1/6] move metric helpers into a new file metric.c
> - [2/6] move metric helpers into metric.c
> - [3/6] merge the read/write patches into a signal patch and move metric helpers to metric.c
> - [4/6] move metric helpers to metric.c
> - [5/6] min/max latency support
> - [6/6] standard deviation support
>
> Changed in V9:
> - add an r_ended field to the mds request struct and use that to calculate the metric
> - fix some commit comments
>
> # cat /sys/kernel/debug/ceph/9a972bfc-68cb-4d52-a610-7cd9a9adbbdd.client52904/metrics
> item total avg_lat(us) min_lat(us) max_lat(us) stdev(us)
> -----------------------------------------------------------------------------------
> read 798 32000 4000 196000 560.3
> write 2394 588000 28000 4812000 36673.9
> metadata 7 116000 2000 707000 8282.8
>
> item total miss hit
> -------------------------------------------------
> d_lease 2 0 0
> caps 2 14 546500
>
>
>
The code all looks reasonable to me.
Ilya mentioned refactoring the set to add the infrastructure up front
first. I too think that would be nice, especially since this will
probably end up being backported to various distros and that would make
that task simpler.
It might also be nice to merge the add in the min/max/stddev support at
the same time you add each latency metric too, rather than adding them
after the fact.
>
> Xiubo Li (6):
> ceph: add dentry lease metric support
> ceph: add caps perf metric for each session
> ceph: add read/write latency metric support
Can you fold the min/max/stddev changes for read/write into the above
patch? I think that would be cleaner, rather than bolting it on after
the fact.
> ceph: add metadata perf metric support
Same here. That should just leave us with a 4 patch series, I think.
> ceph: add min/max latency support for read/write/metadata metrics
> ceph: add standard deviation support for read/write/metadata perf
> metric
>
> fs/ceph/Makefile | 2 +-
> fs/ceph/acl.c | 2 +-
> fs/ceph/addr.c | 18 ++++
> fs/ceph/caps.c | 19 ++++
> fs/ceph/debugfs.c | 116 +++++++++++++++++++++++-
> fs/ceph/dir.c | 17 +++-
> fs/ceph/file.c | 26 ++++++
> fs/ceph/inode.c | 4 +-
> fs/ceph/mds_client.c | 21 ++++-
> fs/ceph/mds_client.h | 7 +-
> fs/ceph/metric.c | 193 ++++++++++++++++++++++++++++++++++++++++
> fs/ceph/metric.h | 64 +++++++++++++
> fs/ceph/super.h | 9 +-
> fs/ceph/xattr.c | 4 +-
> include/linux/ceph/osd_client.h | 1 +
> net/ceph/osd_client.c | 2 +
> 16 files changed, 487 insertions(+), 18 deletions(-)
> create mode 100644 fs/ceph/metric.c
> create mode 100644 fs/ceph/metric.h
>
Thanks,
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2020-03-18 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 14:05 [PATCH v10 0/6] ceph: add perf metrics support xiubli
2020-03-18 14:05 ` [PATCH v10 1/6] ceph: add dentry lease metric support xiubli
2020-03-18 14:05 ` [PATCH v10 2/6] ceph: add caps perf metric for each session xiubli
2020-03-18 14:05 ` [PATCH v10 3/6] ceph: add read/write latency metric support xiubli
2020-03-18 14:05 ` [PATCH v10 4/6] ceph: add metadata perf " xiubli
2020-03-18 14:05 ` [PATCH v10 5/6] ceph: add min/max latency support for read/write/metadata metrics xiubli
2020-03-18 14:05 ` [PATCH v10 6/6] ceph: add standard deviation support for read/write/metadata perf metric xiubli
2020-03-18 16:01 ` Jeff Layton [this message]
2020-03-18 23:28 ` [PATCH v10 0/6] ceph: add perf metrics support Xiubo Li
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=ea5551cf7c7e18b5baf6ec990ae1eddedc62ddce.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.com \
--cc=idryomov@gmail.com \
--cc=pdonnell@redhat.com \
--cc=sage@redhat.com \
--cc=xiubli@redhat.com \
--cc=zyan@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