From: Jeff Layton <jlayton@kernel.org>
To: Patrick Donnelly <pdonnell@redhat.com>
Cc: "Luís Henriques" <lhenriques@suse.de>,
"Ilya Dryomov" <idryomov@gmail.com>,
"Ceph Development" <ceph-devel@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ceph: add remote object copy counter to fs client
Date: Thu, 21 Oct 2021 11:43:55 -0400 [thread overview]
Message-ID: <99209198dd9d8634245f153a90e4091851635a16.camel@kernel.org> (raw)
In-Reply-To: <CA+2bHPbqeH_rmmxcnQ9gq0K8gqtE4q69a8cFnherSJCxSwXV5Q@mail.gmail.com>
On Thu, 2021-10-21 at 09:52 -0400, Patrick Donnelly wrote:
> On Wed, Oct 20, 2021 at 12:27 PM Jeff Layton <jlayton@kernel.org> wrote:
> >
> > On Wed, 2021-10-20 at 15:37 +0100, Luís Henriques wrote:
> > > This counter will keep track of the number of remote object copies done on
> > > copy_file_range syscalls. This counter will be filesystem per-client, and
> > > can be accessed from the client debugfs directory.
> > >
> > > Cc: Patrick Donnelly <pdonnell@redhat.com>
> > > Signed-off-by: Luís Henriques <lhenriques@suse.de>
> > > ---
> > > This is an RFC to reply to Patrick's request in [0]. Note that I'm not
> > > 100% sure about the usefulness of this patch, or if this is the best way
> > > to provide the functionality Patrick requested. Anyway, this is just to
> > > get some feedback, hence the RFC.
> > >
> > > Cheers,
> > > --
> > > Luís
> > >
> > > [0] https://github.com/ceph/ceph/pull/42720
> > >
> >
> > I think this would be better integrated into the stats infrastructure.
> >
> > Maybe you could add a new set of "copy" stats to struct
> > ceph_client_metric that tracks the total copy operations done, their
> > size and latency (similar to read and write ops)?
>
> I think it's a good idea to integrate this into "stats" but I think a
> local debugfs file for some counters is still useful. The "stats"
> module is immature at this time and I'd rather not build any qa tests
> (yet) that rely on it.
>
> Can we generalize this patch-set to a file named "op_counters" or
> similar and additionally add other OSD ops performed by the kclient?
>
Tracking this sort of thing is the main purpose of the stats code. I'm
really not keen on adding a whole separate set of files for reporting
this.
What's the specific problem with relying on the data in debugfs
"metrics" file?
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2021-10-21 15:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 14:37 Luís Henriques
2021-10-20 16:27 ` Jeff Layton
2021-10-20 16:58 ` Luís Henriques
2021-10-21 13:52 ` Patrick Donnelly
2021-10-21 15:43 ` Jeff Layton [this message]
2021-10-21 16:18 ` Patrick Donnelly
2021-10-21 16:35 ` Jeff Layton
2021-10-21 17:30 ` Patrick Donnelly
2021-10-21 17:33 ` Jeff Layton
2021-10-26 3:05 ` Xiubo Li
2021-10-26 11:40 ` Jeff Layton
2021-10-26 15:31 ` Luís Henriques
2021-10-27 6:46 ` Xiubo Li
2021-10-27 10:01 ` [PATCH] ceph: split 'metric' debugfs file into several files Luís Henriques
2021-10-27 11:53 ` Jeff Layton
2021-10-27 12:00 ` Xiubo Li
2021-10-27 4:52 ` [RFC PATCH] ceph: add remote object copy counter to fs client Xiubo Li
2021-10-25 10:12 ` Luís Henriques
2021-10-25 10:20 ` Jeff Layton
2021-10-25 10:52 ` Luís Henriques
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=99209198dd9d8634245f153a90e4091851635a16.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=lhenriques@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pdonnell@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
all inboxes | Powered by JetHome®