[PATCH 02/13] mpt3sas: SGL to PRP Translation for I/Os to NVMe devices
keith.busch at intel.com
Tue Jul 11 17:04:02 PDT 2017
On Tue, Jul 11, 2017 at 01:55:02AM -0700, Suganath Prabu S wrote:
> + * _base_check_pcie_native_sgl - This function is called for PCIe end devices to
> + * determine if the driver needs to build a native SGL. If so, that native
> + * SGL is built in the special contiguous buffers allocated especially for
> + * PCIe SGL creation. If the driver will not build a native SGL, return
> + * TRUE and a normal IEEE SGL will be built. Currently this routine
> + * supports NVMe.
> + * @ioc: per adapter object
> + * @mpi_request: mf request pointer
> + * @smid: system request message index
> + * @scmd: scsi command
> + * @pcie_device: points to the PCIe device's info
> + *
> + * Returns 0 if native SGL was built, 1 if no SGL was built
> + */
> +static int
> +_base_check_pcie_native_sgl(struct MPT3SAS_ADAPTER *ioc,
> + Mpi25SCSIIORequest_t *mpi_request, u16 smid, struct scsi_cmnd *scmd,
> + struct _pcie_device *pcie_device)
> + /* Return 0, indicating we built a native SGL. */
> + return 1;
This function doesn't return 0 ever. Not sure why it's here.
Curious about your device, though, if a nvme native SGL can *not* be
built, does the HBA firmware then buffer it in its local memory before
sending/receiving to/from the host?
And if a native SGL can be built, does the NVMe target DMA directly
to/from host memory, giving a performance boost?
More information about the Linux-nvme