From: Danny Al-Gaaf <danny.al-gaaf@bisect.de>
To: Haomai Wang <haomaiwang@gmail.com>,
Mark Nelson <mark.nelson@inktank.com>
Cc: Samuel Just <sam.just@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Marc Koderer <marckoderer@gmail.com>
Subject: Re: osd systemtap initial steps
Date: Sat, 07 Jun 2014 14:24:08 +0200 [thread overview]
Message-ID: <53930468.6030203@bisect.de> (raw)
In-Reply-To: <CACJqLybMfGkEtTwP9Yz64992CqHFSj2TuubW1j4-_SJONvvPDQ@mail.gmail.com>
Hi,
I will take a look at it and push the stuff I have already to a git
branch. We can then add more hooks.
Danny
Am 07.06.2014 14:15, schrieb Haomai Wang:
> May I asked the status of this bp?
>
> Maybe we can push this further
>
> On Thu, May 1, 2014 at 5:18 AM, Mark Nelson <mark.nelson@inktank.com> wrote:
>> Have I mentioned how exciting that is?
>>
>> Mark
>>
>>
>> On 04/30/2014 04:14 PM, Samuel Just wrote:
>>>
>>> Cool. Looks like we read the same guide on the autotools bit :P. I'm
>>> focusing on instrumenting the OSD op life cycle.
>>> -Sam
>>>
>>> On Wed, Apr 30, 2014 at 6:19 AM, Danny Al-Gaaf <danny.al-gaaf@bisect.de>
>>> wrote:
>>>>
>>>> Am 30.04.2014 04:21, schrieb Haomai Wang:
>>>>>
>>>>> So cool!
>>>>>
>>>>> I remember a telekomcloud guy is also worked for it since last summit.
>>>>
>>>>
>>>> Correct ... our initial version is/was this:
>>>> https://github.com/dalgaaf/ceph/commits/wip-master-bp-systemtap
>>>>
>>>> Danny
>>>>
>>>>> On Wed, Apr 30, 2014 at 6:17 AM, Samuel Just <sam.just@inktank.com>
>>>>> wrote:
>>>>>>
>>>>>> I'm starting on adding systemtap trace points to the osd.
>>>>>>
>>>>>> https://github.com/athanatos/ceph/tree/wip-osd-stap
>>>>>>
>>>>>> has some initial build changes and a single tracepoint in
>>>>>> OSD::handle_op.
>>>>>>
>>>>>> I'll ping the list when I've got more.
>>>>>> -Sam
>>>>
>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
>
>
>
prev parent reply other threads:[~2014-06-07 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 22:17 osd systemtap initial steps Samuel Just
2014-04-30 2:21 ` Haomai Wang
2014-04-30 13:19 ` Danny Al-Gaaf
2014-04-30 21:14 ` Samuel Just
2014-04-30 21:18 ` Mark Nelson
2014-06-07 12:15 ` Haomai Wang
2014-06-07 12:24 ` Danny Al-Gaaf [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=53930468.6030203@bisect.de \
--to=danny.al-gaaf@bisect.de \
--cc=ceph-devel@vger.kernel.org \
--cc=haomaiwang@gmail.com \
--cc=marckoderer@gmail.com \
--cc=mark.nelson@inktank.com \
--cc=sam.just@inktank.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 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.