All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: Jim Schutt <jaschut@sandia.gov>
Cc: elder@dreamhost.com, ceph-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] Ceph tracepoints
Date: Thu, 10 May 2012 10:39:36 -0500	[thread overview]
Message-ID: <4FABE138.6030809@inktank.com> (raw)
In-Reply-To: <1336660556-6943-1-git-send-email-jaschut@sandia.gov>

On 05/10/2012 09:35 AM, Jim Schutt wrote:
> Hi Alex,
>
> I ran across tracker #2374 today - I've been carrying these two
> tracepoint patches for a while.  Perhaps you'll find them useful.

GREAT!

I haven't looked at them but I will as soon as I get the chance.
I don't expect there's any reason not to use this as the foundation
I was looking for.

Thanks a lot.

					-Alex

> Jim Schutt (2):
>    ceph: add tracepoints for message submission on read/write requests
>    ceph: add tracepoints for message send queueing and completion, reply
>      handling
>
>   fs/ceph/addr.c              |    8 +++
>   fs/ceph/file.c              |    6 ++
>   include/trace/events/ceph.h |  144 +++++++++++++++++++++++++++++++++++++++++++
>   net/ceph/messenger.c        |    9 +++-
>   net/ceph/osd_client.c       |    8 +++
>   5 files changed, 174 insertions(+), 1 deletions(-)
>   create mode 100644 include/trace/events/ceph.h
>


      parent reply	other threads:[~2012-05-10 15:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 14:35 [PATCH 0/2] Ceph tracepoints Jim Schutt
2012-05-10 14:35 ` [PATCH 1/2] ceph: add tracepoints for message submission on read/write requests Jim Schutt
2012-05-10 14:35 ` [PATCH 2/2] ceph: add tracepoints for message send queueing and completion, reply handling Jim Schutt
2012-05-10 15:39 ` Alex Elder [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=4FABE138.6030809@inktank.com \
    --to=elder@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=elder@dreamhost.com \
    --cc=jaschut@sandia.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.