CEPH filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: Venky Shankar <vshankar@redhat.com>, idryomov@gmail.com
Cc: xiubli@redhat.com, ceph-devel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] ceph: forward average read/write/metadata latency
Date: Tue, 08 Mar 2022 10:58:22 -0500	[thread overview]
Message-ID: <4e82e2ac560baad2ab51d0b92ffb6fdfcadf48aa.camel@redhat.com> (raw)
In-Reply-To: <20220308124219.771527-1-vshankar@redhat.com>

On Tue, 2022-03-08 at 07:42 -0500, Venky Shankar wrote:
> v2
>   - rename to_ceph_timespec() to ktime_to_ceph_timespec()
>   - use ceph_encode_timespec64() helper
> 
> Jeff,
> 
> To apply these, please drop commit range f4bf256..840d9f0 from testing branch.
> 
> Right now, cumulative read/write/metadata latencies are tracked
> and are periodically forwarded to the MDS. These meterics are not
> particularly useful. A much more useful metric is the average latency
> and standard deviation (stdev) which is what this series of patches
> aims to do.
> 
> The userspace (libcephfs+tool) changes are here::
> 
>           https://github.com/ceph/ceph/pull/41397
> 
> Note that the cumulative latencies are still forwarded to the MDS but
> the tool (cephfs-top) ignores it altogether.
> 
> Latency standard deviation is calculated in `cephfs-top` tool.
> 
> Venky Shankar (4):
>   ceph: use ktime_to_timespec64() rather than jiffies_to_timespec64()
>   ceph: track average r/w/m latency
>   ceph: include average/stdev r/w/m latency in mds metrics
>   ceph: use tracked average r/w/m latencies to display metrics in
>     debugfs
> 
>  fs/ceph/debugfs.c |  5 ++--
>  fs/ceph/metric.c  | 63 +++++++++++++++++++++++++++--------------------
>  fs/ceph/metric.h  | 63 ++++++++++++++++++++++++++++++-----------------
>  3 files changed, 79 insertions(+), 52 deletions(-)
> 

Thanks Venky. New version is now merged into testing.
-- 
Jeff Layton <jlayton@redhat.com>


  parent reply	other threads:[~2022-03-08 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 12:42 [PATCH v2 0/4] ceph: forward average read/write/metadata latency Venky Shankar
2022-03-08 12:42 ` [PATCH v2 1/4] ceph: use ktime_to_timespec64() rather than jiffies_to_timespec64() Venky Shankar
2022-03-08 12:42 ` [PATCH v2 2/4] ceph: track average r/w/m latency Venky Shankar
2022-03-08 12:42 ` [PATCH v2 3/4] ceph: include average/stdev r/w/m latency in mds metrics Venky Shankar
2022-03-08 12:42 ` [PATCH v2 4/4] ceph: use tracked average r/w/m latencies to display metrics in debugfs Venky Shankar
2022-03-08 12:57 ` [PATCH v2 0/4] ceph: forward average read/write/metadata latency Xiubo Li
2022-03-08 15:58 ` Jeff Layton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-14  8:48 Venky Shankar

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=4e82e2ac560baad2ab51d0b92ffb6fdfcadf48aa.camel@redhat.com \
    --to=jlayton@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=vshankar@redhat.com \
    --cc=xiubli@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