From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [RFC PATCH V7 4/7] nvme: trace: support for fabrics commands in host-side
Date: Sat, 8 Jun 2019 10:37:01 +0900 [thread overview]
Message-ID: <20190608013701.GD1276@minwooim-desktop> (raw)
In-Reply-To: <20190607165156.GG7307@lst.de>
On 19-06-07 18:51:56, Christoph Hellwig wrote:
>
> > +#define parse_nvme_cmd(qid, opcode, fctype, cdw10) \
> > + ((opcode != nvme_fabrics_command) ? \
> > + (qid ? \
> > + nvme_trace_parse_nvm_cmd(p, opcode, cdw10) : \
> > + nvme_trace_parse_admin_cmd(p, opcode, cdw10)) : \
> > + nvme_trace_parse_fabrics_cmd(p, fctype, cdw10))
>
> The indentation and use of braces looks a little odd here, how about:
>
> #define parse_nvme_cmd(qid, opcode, fctype, cdw10) \
> ((opcode) == nvme_fabrics_command ? \
> nvme_trace_parse_fabrics_cmd(p, fctype, cdw10) : \
> ((qid) ? \
> nvme_trace_parse_nvm_cmd(p, opcode, cdw10) : \
> nvme_trace_parse_admin_cmd(p, opcode, cdw10)))
>
>
> > +/*
> > + * If not fabrics command, fctype will be ignored.
> > + */
> > +#define show_opcode_name(qid, opcode, fctype) \
> > + ((opcode != nvme_fabrics_command) ? \
> > + (qid ? \
> > + show_nvm_opcode_name(opcode) : \
> > + show_admin_opcode_name(opcode)) : \
> > + show_fabrics_type_name(fctype))
> > +
>
> and:
>
> #define show_opcode_name(qid, opcode, fctype) \
> ((opcode) == nvme_fabrics_command ? \
> show_fabrics_type_name(fctype) : \
> ((qid) ? \
> show_nvm_opcode_name(opcode) : \
> show_admin_opcode_name(opcode)))
I'm actually fine with both. I was trying to make some depth from the
previous comparisons. But, Okay, will fix this up in next series.
> Otherwise looks good:
>
> Reviewed-by: Christoph Hellwig <hch at lst.de>
Thanks for your review, Christoph.
Thanks,
next prev parent reply other threads:[~2019-06-08 1:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 19:45 [RFC PATCH V7 0/7] nvme-trace: Add support for fabrics command Minwoo Im
2019-06-06 19:45 ` [RFC PATCH V7 1/7] nvme: trace: do not EXPORT_SYMBOL for a trace function Minwoo Im
2019-06-06 19:45 ` [RFC PATCH V7 2/7] nvme: trace: move opcode symbol print to nvme.h Minwoo Im
2019-06-07 16:46 ` Christoph Hellwig
2019-06-08 1:57 ` Minwoo Im
2019-06-06 19:45 ` [RFC PATCH V7 3/7] nvme: trace: put cid with le16_to_cpu() Minwoo Im
2019-06-07 16:47 ` Christoph Hellwig
2019-06-08 1:35 ` Minwoo Im
2019-06-06 19:45 ` [RFC PATCH V7 4/7] nvme: trace: support for fabrics commands in host-side Minwoo Im
2019-06-07 16:51 ` Christoph Hellwig
2019-06-08 1:37 ` Minwoo Im [this message]
2019-06-06 19:45 ` [RFC PATCH V7 5/7] nvme: trace: filter out unnecessary fields for fabrics Minwoo Im
2019-06-07 16:52 ` Christoph Hellwig
2019-06-08 1:38 ` Minwoo Im
2019-06-06 19:45 ` [RFC PATCH V7 6/7] nvme: trace: print result and status in hex format Minwoo Im
2019-06-07 16:53 ` Christoph Hellwig
2019-06-06 19:45 ` [RFC PATCH V7 7/7] nvmet: introduce target-side trace Minwoo Im
2019-06-07 16:54 ` Christoph Hellwig
2019-06-08 1:49 ` 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=20190608013701.GD1276@minwooim-desktop \
--to=minwoo.im.dev@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox