From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH] nvme-cli: update show_registers_cc() to use nvme.h
Date: Fri, 1 Dec 2017 00:49:17 +0900 [thread overview]
Message-ID: <1512056957-17841-1-git-send-email-minwoo.im.dev@gmail.com> (raw)
Replace constants for shift in show_register_cc() with macros defined.
Also clean up a small typo (IOSQES to IOCQES).
Signed-off-by: Minwoo Im <minwoo.im.dev at gmail.com>
---
nvme-print.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/nvme-print.c b/nvme-print.c
index db11dd7..e84c73f 100644
--- a/nvme-print.c
+++ b/nvme-print.c
@@ -1923,11 +1923,11 @@ static void show_registers_cc_shn (__u8 shn)
static void show_registers_cc(__u32 cc)
{
- printf("\tI/O Completion Queue Entry Size (IOSQES): %u bytes\n", 1 << ((cc & 0x00f00000) >> 20));
- printf("\tI/O Submission Queue Entry Size (IOSQES): %u bytes\n", 1 << ((cc & 0x000f0000) >> 16));
- show_registers_cc_shn((cc & 0x0000c000) >> 14);
- show_registers_cc_ams((cc & 0x00003800) >> 11);
- printf("\tMemory Page Size (MPS): %u bytes\n", 1 << (12 + ((cc & 0x00000780) >> 7)));
+ printf("\tI/O Completion Queue Entry Size (IOCQES): %u bytes\n", 1 << ((cc & 0x00f00000) >> NVME_CC_IOCQES_SHIFT));
+ printf("\tI/O Submission Queue Entry Size (IOSQES): %u bytes\n", 1 << ((cc & 0x000f0000) >> NVME_CC_IOSQES_SHIFT));
+ show_registers_cc_shn((cc & 0x0000c000) >> NVME_CC_SHN_SHIFT);
+ show_registers_cc_ams((cc & 0x00003800) >> NVME_CC_AMS_SHIFT);
+ printf("\tMemory Page Size (MPS): %u bytes\n", 1 << (12 + ((cc & 0x00000780) >> NVME_CC_MPS_SHIFT)));
printf("\tI/O Command Sets Selected (CSS): %s\n", (cc & 0x00000070) ? "Reserved":"NVM Command Set");
printf("\tEnable (EN): %s\n\n", (cc & 0x00000001) ? "Yes":"No");
}
--
2.7.4
next reply other threads:[~2017-11-30 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 15:49 Minwoo Im [this message]
2017-11-30 21:40 ` [PATCH] nvme-cli: update show_registers_cc() to use nvme.h Keith Busch
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=1512056957-17841-1-git-send-email-minwoo.im.dev@gmail.com \
--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