From: Jeff Furlong <jeff.furlong@wdc.com>
To: Gnana Sekhar <kgsgnana2020@gmail.com>,
Sitsofe Wheeler <sitsofe@gmail.com>
Cc: fio <fio@vger.kernel.org>
Subject: RE: Failures noticed in FIO run
Date: Fri, 9 Feb 2018 18:39:14 +0000 [thread overview]
Message-ID: <BN3PR0401MB145712BD3095CE801F37A6AE8FF20@BN3PR0401MB1457.namprd04.prod.outlook.com> (raw)
In-Reply-To: <CAPSTwmTCDO4tn4u1=GyZB3xm5JUjB8LQyvjeFhig8uWH+-HJjA@mail.gmail.com>
> Also which of the below do you think I should use to get the LBA size on device blockdev --getbsz /dev/nvme0n1 or blockdev --getss /dev/nvme0n1
I believe getbsz will always return the physical block size, while getss will return the logical block size. Most SSDs have a 4096B physical block size, and some support emulating a 512B block size to the host, while still internally maintaining a 4096B physical block size. So if you formatted your namespace 1 for 4096B or 512B, in both cases, getbsz returns 4096B. Only if you formatted your namespace 1 to 512B will getss return 512B. And if you formatted for metadata or protection information, it will be more difficult (you might want to look at a nvme command with nvme-cli instead of using these legacy ioctls).
Regards,
Jeff
prev parent reply other threads:[~2018-02-09 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPSTwmSKtMj5yGR2Wb3AY54_CGfWbdEqoWKYy1fKDBiQ3Uo4=Q@mail.gmail.com>
2018-02-06 5:15 ` Fwd: Failures noticed in FIO run Gnana Sekhar
[not found] ` <CALjAwxhb2ozbDNv02CqiaHUzHmCFDYU6+_DNwhde2GnRT2pEcw@mail.gmail.com>
2018-02-07 0:19 ` Gnana Sekhar
2018-02-07 1:39 ` Jeff Furlong
2018-02-07 16:18 ` Sitsofe Wheeler
2018-02-07 17:33 ` Jeff Furlong
2018-02-07 16:12 ` Sitsofe Wheeler
2018-02-09 4:21 ` Gnana Sekhar
2018-02-09 10:10 ` Sitsofe Wheeler
2018-02-09 18:39 ` Jeff Furlong [this message]
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=BN3PR0401MB145712BD3095CE801F37A6AE8FF20@BN3PR0401MB1457.namprd04.prod.outlook.com \
--to=jeff.furlong@wdc.com \
--cc=fio@vger.kernel.org \
--cc=kgsgnana2020@gmail.com \
--cc=sitsofe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.