On 04/16/18 10:05, Bean Huo (beanhuo) wrote:
On Mon, 2018-04-16 at 09:41 -0700, Rajat Jain wrote:
On Mon, Apr 16, 2018 at 8:28 AM, Steven Rostedt <rostedt@xxxxxxxxxxx>
wrote:
On Mon, 16 Apr 2018 14:31:49 +0000
"Bean Huo (beanhuo)" <beanhuo@xxxxxxxxxx> wrote:
Print the request tag along with other information while tracing a
command.
Signed-off-by: Bean Huo <beanhuo@xxxxxxxxxx>
Acked-by: Rajat Jain <rajatja@xxxxxxxxxx>
This patch is not acceptable because it adds support for tag tracing to the
legacy block layer only. Any patch that adds a new feature to the legacy block
layer must also add it to blk-mq.
To be honest, I don't understand your point, can you give me more explanation?
The legacy block layer will be removed as soon as blk-mq provides all
the functionality of the legacy block layer and as soon as it performs
at least as well as the legacy block layer for all use cases. If new
features are added to the legacy block layer but not to blk-mq that
prevents removal of the legacy block layer. Hence the requirement I
explained in my previous e-mail.
Bart.
