* Query on metadata formatted NVMe Drive
@ 2017-06-28 15:56 Adhrit P
2017-06-28 17:00 ` Keith Busch
0 siblings, 1 reply; 2+ messages in thread
From: Adhrit P @ 2017-06-28 15:56 UTC (permalink / raw)
Hi all,
As i understand, current NVMe driver can support working with
different metadata (extended/separate) size formatted drive and the
same can be verified using IOCTL path with user metadata.
Is there any way to verify the same (all metadata sizes with
extended/separate buffer) through block layer/kernel IO path using
fio or any other application ?
thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Query on metadata formatted NVMe Drive
2017-06-28 15:56 Query on metadata formatted NVMe Drive Adhrit P
@ 2017-06-28 17:00 ` Keith Busch
0 siblings, 0 replies; 2+ messages in thread
From: Keith Busch @ 2017-06-28 17:00 UTC (permalink / raw)
On Wed, Jun 28, 2017@09:26:06PM +0530, Adhrit P wrote:
>
> As i understand, current NVMe driver can support working with
> different metadata (extended/separate) size formatted drive and the
> same can be verified using IOCTL path with user metadata.
> Is there any way to verify the same (all metadata sizes with
> extended/separate buffer) through block layer/kernel IO path using
> fio or any other application ?
Metadata through the block layer is for kernel use, and only if
separate. Extended is not supported through this layer.
If you need to access these regions from user sapce, the NVME_SUBMIT_IO
ioctl is the only way to do that, which can work with both separate
and extended.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-06-28 17:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-28 15:56 Query on metadata formatted NVMe Drive Adhrit P
2017-06-28 17:00 ` Keith Busch
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.