From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-trace: Add fabrics command opcode name
Date: Mon, 6 May 2019 18:31:14 +0200 [thread overview]
Message-ID: <20190506163114.GA9468@lst.de> (raw)
In-Reply-To: <SN6PR04MB45270E164CBC599246428CE386300@SN6PR04MB4527.namprd04.prod.outlook.com>
On Mon, May 06, 2019@04:29:12PM +0000, Chaitanya Kulkarni wrote:
> Please do not mix admin and fabric commands.
Well, "the" fabrics command is an opcode that can show up on
admin or I/O queues. "the" because it actually is a multiplexer,
and we probably want to decode it instead of just saying fabrics
command in the traces.
next prev parent reply other threads:[~2019-05-06 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 15:22 [PATCH] nvme-trace: Add fabrics command opcode name Minwoo Im
2019-05-06 16:29 ` Chaitanya Kulkarni
2019-05-06 16:31 ` Christoph Hellwig [this message]
2019-05-06 16:35 ` Minwoo Im
2019-05-06 16:36 ` Minwoo Im
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=20190506163114.GA9468@lst.de \
--to=hch@lst.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox