Re: [RFC 7/8] nvmet/admin-cmd: Hookup T10-PI to ID_NS.ms + ID_NS.dps feature bits

2016-06-09 Thread Nicholas A. Bellinger
On Thu, 2016-06-09 at 15:52 +0200, Christoph Hellwig wrote: > FYI: NVMf requires metadata to be interleaved in the data, and you > need to indicate that in the Identify data. Note that this is only > a requirement for the on the wire format and for the way the Namespaces are > exposed at the proto

Re: [RFC 7/8] nvmet/admin-cmd: Hookup T10-PI to ID_NS.ms + ID_NS.dps feature bits

2016-06-09 Thread Christoph Hellwig
FYI: NVMf requires metadata to be interleaved in the data, and you need to indicate that in the Identify data. Note that this is only a requirement for the on the wire format and for the way the Namespaces are exposed at the protocol level as RDMA HCA and FB HBAs should still be able to handle our

[RFC 7/8] nvmet/admin-cmd: Hookup T10-PI to ID_NS.ms + ID_NS.dps feature bits

2016-06-06 Thread Nicholas A. Bellinger
From: Nicholas Bellinger This patch updates nvmet_execute_identify_ns() to report target-core backend T10-PI related feature bits to the NVMe host controller. Note this assumes support for NVME_NS_DPC_PI_TYPE1 and NVME_NS_DPC_PI_TYPE3 as reported by backend drivers via /sys/kernel/config/target/