[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6c8f80f9-bf7e-4d74-865a-86c9dd7025aa@oracle.com>
Date: Fri, 13 Sep 2024 15:08:41 +0100
From: John Garry <john.g.garry@...cle.com>
To: Daniel Gomez <da.gomez@...sung.com>
Cc: Jens Axboe <axboe@...nel.dk>, Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, gost.dev@...sung.com,
Luis Chamberlain <mcgrof@...nel.org>,
Pankaj Raghav <p.raghav@...sung.com>,
Dave Chinner <dchinner@...hat.com>, Daniel Gomez <d@...ces.com>
Subject: Re: [PATCH RFC] block: trace: add block alignment information
On 13/09/2024 14:57, Daniel Gomez wrote:
>> I am just saying that the information already present in the block trace
>> point can be used to get this "alignment" info, right? And userspace can do
>> the work of reading those trace events to find this "alignment" info.
> So, maybe this is better to have integrated in blktrace tool?
Sure, or whatever tool which can process this information. I just don't
see why the kernel should be burdened with this.
Thanks,
John
Powered by blists - more mailing lists