diff options
| author | James Smart <jsmart2021@gmail.com> | 2017-03-08 14:36:01 -0800 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2017-03-15 13:37:18 -0400 |
| commit | 7d7080335f8d93a51e8238b6e85be8af4ba452b6 (patch) | |
| tree | c93ca817a5d6b00f7a3920f75c59f3f83c2dc0dd /lib/syscall.c | |
| parent | 949d7fa158b2b1af533bdb1af0dda8ab103ac58d (diff) | |
scsi: lpfc: Finalize Kconfig options for nvme
Reviewing the result of what was just added for Kconfig, we made a poor
choice. It worked well for full kernel builds, but not so much for how
it would be deployed on a distro.
Here's the final result:
- lpfc will compile in NVME initiator and/or NVME target support based
on whether the kernel has the corresponding subsystem support.
Kconfig is not used to drive this specifically for lpfc.
- There is a module parameter, lpfc_enable_fc4_type, that indicates
whether the ports will do FCP-only or FCP & NVME (NVME-only not yet
possible due to dependency on fc transport). As FCP & NVME divvys up
exchange resources, and given NVME will not be often initially, the
default is changed to FCP only.
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <james.smart@broadcom.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'lib/syscall.c')
0 files changed, 0 insertions, 0 deletions