From: Jens Axboe <jens.axboe@oracle.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
jack@suse.cz, chris.mason@oracle.com
Subject: Re: writeback tracing
Date: Tue, 3 Nov 2009 19:35:27 +0100 [thread overview]
Message-ID: <20091103183527.GE8742@kernel.dk> (raw)
In-Reply-To: <20091103141159.GA13442@localhost>
On Tue, Nov 03 2009, Wu Fengguang wrote:
> Hi Jens,
>
> Thanks, it's a very good step. I'll take advantage of it for writeback
> testing/debugging and watch how things work :)
Yep, it's interesting :-)
> However you didn't plan to submit it soon? Because tracepoints are
> expected to be relatively stable, and you know that writeback is
> somehow a hot topic now, hehe.
No, I don't have submission plans yet. Just wanted to throw this out
there and see if we can agree on some decent trace points for a
potential future submission. But so far I just wanted to play around and
have others do the same.
--
Jens Axboe
prev parent reply other threads:[~2009-11-03 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 8:55 writeback tracing Jens Axboe
2009-11-03 14:11 ` Wu Fengguang
2009-11-03 18:35 ` Jens Axboe [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=20091103183527.GE8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=chris.mason@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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.