On 06/12/16 09:38 AM, Jason Gunthorpe wrote:
>> I'm not opposed to mapping /dev/nvmeX. However, the
lookup is trivial
>> to accomplish in sysfs through /sys/dev/char to find the sysfs path of the
>> device-dax instance under the nvme device, or if you already have the nvme
>> sysfs path the dax instance(s) will appear under the "dax"
> Personally I think mapping the dax resource in the sysfs tree is a nice
> way to do this and a bit more intuitive than mapping a /dev/nvmeX.
It is still not at all clear to me what userpsace is supposed to do
with this on nvme.. How is the CMB usable from userspace?
The flow is pretty simple. For example to write to NVMe from an RDMA device:
1) Obtain a chunk of the CMB to use as a buffer(either by mmaping
/dev/nvmx, the device dax char device or through a block layer interface
(which sounds like a good suggestion from Christoph, but I'm not really
sure how it would look).
2) Create an MR with the buffer and use an RDMA function to fill it with
data from a remote host. This will cause the RDMA hardware to write
directly to the memory in the NVMe card.
3) Using O_DIRECT, write the buffer to a file on the NVMe filesystem.
When the address reaches hardware the NVMe will recognize it as local
memory and copy it directly there.
Thus we are able to transfer data to any file on an NVMe device without
going through system memory. This has benefits on systems with lots of
activity in system memory but step 3 is likely to be slowish due to the
need to pin/unpin the memory for every transaction.