[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56F3F4F5.8050200@fb.com>
Date: Thu, 24 Mar 2016 08:08:53 -0600
From: Jens Axboe <axboe@...com>
To: Baolin Wang <baolin.wang@...aro.org>, <ulf.hansson@...aro.org>,
<rostedt@...dmis.org>, <mingo@...hat.com>
CC: <adrian.hunter@...el.com>, <yangbo.lu@...escale.com>,
<akpm@...ux-foundation.org>, <JBottomley@...n.com>,
<lporzio@...ron.com>, <jonathanh@...dia.com>,
<grundler@...omium.org>, <fabf@...net.be>, <yunpeng.gao@...el.com>,
<dan.j.williams@...el.com>, <rabin.vincent@...s.com>,
<chuanxiao.dong@...el.com>, <shawn.lin@...k-chips.com>,
<heiko@...ech.de>, <dianders@...omium.org>, <david@...tonic.nl>,
<broonie@...nel.org>, <linus.walleij@...aro.org>,
<takahiro.akashi@...aro.org>, <linux-kernel@...r.kernel.org>,
<linux-mmc@...r.kernel.org>
Subject: Re: [PATCH] mmc: Provide tracepoints for request processing
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
Powered by blists - more mailing lists