ceph-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Xiubo Li <xiubli@redhat.com>, Ilya Dryomov <idryomov@gmail.com>
Cc: Patrick Donnelly <pdonnell@redhat.com>,
	"Yan, Zheng" <ukernel@gmail.com>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] ceph: send io size metrics to mds daemon
Date: Sat, 22 May 2021 08:15:41 -0400	[thread overview]
Message-ID: <e1d3be523b2571ddd1cea354be525b596938bad1.camel@kernel.org> (raw)
In-Reply-To: <04b4b11c-0411-cacd-9504-36be3437169c@redhat.com>

On Tue, 2021-05-18 at 09:00 +0800, Xiubo Li wrote:
> On 5/17/21 11:46 PM, Jeff Layton wrote:
> > On Fri, 2021-05-14 at 17:14 +0800, Xiubo Li wrote:
> > > On 5/14/21 4:57 PM, Ilya Dryomov wrote:
> > > > On Fri, May 14, 2021 at 2:47 AM Xiubo Li <xiubli@redhat.com> wrote:
> > > > > On 5/13/21 7:30 PM, Jeff Layton wrote:
> > > > > > On Thu, 2021-05-13 at 09:40 +0800, xiubli@redhat.com wrote:
> > > > > > > From: Xiubo Li <xiubli@redhat.com>
> > > > > > > 
> > > > > > > V2:
> > > > > > > - change the patch order
> > > > > > > - replace the fixed 10 with sizeof(struct ceph_metric_header)
> > > > > > > 
> > > > > > > Xiubo Li (2):
> > > > > > >      ceph: simplify the metrics struct
> > > > > > >      ceph: send the read/write io size metrics to mds
> > > > > > > 
> > > > > > >     fs/ceph/metric.c | 90 ++++++++++++++++++++++++++++++------------------
> > > > > > >     fs/ceph/metric.h | 79 +++++++++++++++++-------------------------
> > > > > > >     2 files changed, 89 insertions(+), 80 deletions(-)
> > > > > > > 
> > > > > > Thanks Xiubo,
> > > > > > 
> > > > > > These look good. I'll do some testing with them and plan to merge these
> > > > > > into the testing branch later today.
> > > > > Sure, take your time.
> > > > FYI I squashed "ceph: send the read/write io size metrics to mds" into
> > > > "ceph: add IO size metrics support".
> > I've dropped this combined patch for now, as it was triggering an MDS
> > assertion that was hampering testing [1]. I'll plan to add it back once
> > that problem is resolved in the MDS.
> > 
> > [1]: https://github.com/ceph/ceph/pull/41357
> > 
> > Cheers,
> 
> Ack. Thanks.
> 
> 

Patrick mentioned that the problem with the MDS has now been resolved,
so I've gone ahead and merged this patch back into testing branch. Let
me know if you see any more issues.

Thanks!
-- 
Jeff Layton <jlayton@kernel.org>


      reply	other threads:[~2021-05-22 12:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13  1:40 [PATCH v2 0/2] ceph: send io size metrics to mds daemon xiubli
2021-05-13  1:40 ` [PATCH v2 1/2] ceph: simplify the metrics struct xiubli
2021-05-13  1:40 ` [PATCH v2 2/2] ceph: send the read/write io size metrics to mds xiubli
2021-05-13 11:30 ` [PATCH v2 0/2] ceph: send io size metrics to mds daemon Jeff Layton
2021-05-14  0:47   ` Xiubo Li
2021-05-14  8:57     ` Ilya Dryomov
2021-05-14  9:14       ` Xiubo Li
2021-05-17 15:46         ` Jeff Layton
2021-05-18  1:00           ` Xiubo Li
2021-05-22 12:15             ` Jeff Layton [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=e1d3be523b2571ddd1cea354be525b596938bad1.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=pdonnell@redhat.com \
    --cc=ukernel@gmail.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;
as well as URLs for NNTP newsgroup(s).