From: Jens Axboe <axboe@fb.com>
To: Baolin Wang <baolin.wang@linaro.org>,
ulf.hansson@linaro.org, rostedt@goodmis.org, mingo@redhat.com
Cc: adrian.hunter@intel.com, yangbo.lu@freescale.com,
akpm@linux-foundation.org, JBottomley@Odin.com,
lporzio@micron.com, jonathanh@nvidia.com, grundler@chromium.org,
fabf@skynet.be, yunpeng.gao@intel.com, dan.j.williams@intel.com,
rabin.vincent@axis.com, chuanxiao.dong@intel.com,
shawn.lin@rock-chips.com, heiko@sntech.de, dianders@chromium.org,
david@protonic.nl, broonie@kernel.org, linus.walleij@linaro.org,
takahiro.akashi@linaro.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: Provide tracepoints for request processing
Date: Thu, 24 Mar 2016 08:08:53 -0600 [thread overview]
Message-ID: <56F3F4F5.8050200@fb.com> (raw)
In-Reply-To: <05d6338bddae751c1755e7825d4179658e78cc71.1458819912.git.baolin.wang@linaro.org>
On 03/24/2016 05:54 AM, Baolin Wang wrote:
> This patch provides some tracepoints for the lifecycle of a request from
> fetching to completion to help with performance analysis of MMC subsystem.
Most of these already exist as block layer trace points, why do we need
mmc specific ones?
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@fb.com>
To: Baolin Wang <baolin.wang@linaro.org>, <ulf.hansson@linaro.org>,
<rostedt@goodmis.org>, <mingo@redhat.com>
Cc: <adrian.hunter@intel.com>, <yangbo.lu@freescale.com>,
<akpm@linux-foundation.org>, <JBottomley@Odin.com>,
<lporzio@micron.com>, <jonathanh@nvidia.com>,
<grundler@chromium.org>, <fabf@skynet.be>,
<yunpeng.gao@intel.com>, <dan.j.williams@intel.com>,
<rabin.vincent@axis.com>, <chuanxiao.dong@intel.com>,
<shawn.lin@rock-chips.com>, <heiko@sntech.de>,
<dianders@chromium.org>, <david@protonic.nl>,
<broonie@kernel.org>, <linus.walleij@linaro.org>,
<takahiro.akashi@linaro.org>, <linux-kernel@vger.kernel.org>,
<linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: Provide tracepoints for request processing
Date: Thu, 24 Mar 2016 08:08:53 -0600 [thread overview]
Message-ID: <56F3F4F5.8050200@fb.com> (raw)
In-Reply-To: <05d6338bddae751c1755e7825d4179658e78cc71.1458819912.git.baolin.wang@linaro.org>
On 03/24/2016 05:54 AM, Baolin Wang wrote:
> This patch provides some tracepoints for the lifecycle of a request from
> fetching to completion to help with performance analysis of MMC subsystem.
Most of these already exist as block layer trace points, why do we need
mmc specific ones?
--
Jens Axboe
next prev parent reply other threads:[~2016-03-24 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 11:54 [PATCH] mmc: Provide tracepoints for request processing Baolin Wang
2016-03-24 14:02 ` kbuild test robot
2016-03-24 14:02 ` kbuild test robot
2016-03-24 14:08 ` Jens Axboe [this message]
2016-03-24 14:08 ` Jens Axboe
2016-03-25 7:32 ` Baolin Wang
2016-03-25 14:07 ` Jens Axboe
2016-03-25 14:07 ` Jens Axboe
2016-03-28 4:55 ` Baolin Wang
2016-03-24 14:53 ` kbuild test robot
2016-03-24 14:53 ` kbuild test robot
2016-03-24 15:13 ` Steven Rostedt
2016-03-25 7:58 ` Baolin Wang
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=56F3F4F5.8050200@fb.com \
--to=axboe@fb.com \
--cc=JBottomley@Odin.com \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=chuanxiao.dong@intel.com \
--cc=dan.j.williams@intel.com \
--cc=david@protonic.nl \
--cc=dianders@chromium.org \
--cc=fabf@skynet.be \
--cc=grundler@chromium.org \
--cc=heiko@sntech.de \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lporzio@micron.com \
--cc=mingo@redhat.com \
--cc=rabin.vincent@axis.com \
--cc=rostedt@goodmis.org \
--cc=shawn.lin@rock-chips.com \
--cc=takahiro.akashi@linaro.org \
--cc=ulf.hansson@linaro.org \
--cc=yangbo.lu@freescale.com \
--cc=yunpeng.gao@intel.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.