Date: Mon, 7 Feb 2022 16:24:45 -0800 From: John Baldwin <jhb@FreeBSD.org> To: Ken Merry <ken@kdm.org>, Alexander Motin <mav@FreeBSD.org>, =?UTF-8?Q?Edward_Tomasz_Napiera=c5=82a?= <trasz@freebsd.org> Cc: scsi@FreeBSD.org Subject: NVMeoF and ctl Message-ID: <694eabe2-e796-ebdc-b3f1-eff8f8fc1b24@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
One of the things I will be working on in the near future is NVMe over fabrics support, and specifically over TCP as Chelsio NICs include NVMe offload support (I think PDU encap/decap similar to the cxgbei driver for iSCSI offload). A question I have about this is if it makes sense for NVMeoF target support to make use of ctl? From what I can see, the code in ctl today seems to be very SCSI specific including both in the kernel and in the userland ctld unlike the Linux target code which appears to support both NVMeoF and iSCSI in its ctld equivalent. Is the intention for there to be a cleaner separation here, and if so do you have any thoughts on what the design would be like? Or should NVMeoF just be its own thing separate from ctl and ctld? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?694eabe2-e796-ebdc-b3f1-eff8f8fc1b24>