On 06/14/2017 10:02 PM, Sebastian Herbszt wrote: > Hannes Reinecke wrote: >> On 06/13/2017 01:08 AM, James Smart wrote: > > [snip] > >>> Questions: >>> a) How best to deal with overlapping pci id's ? E.g. if we do (1) >>> and we have an initiator and target driver, there is a lot of >>> adapters that are fully functional for target operation, but were >>> sold as primarily an initiator adapter. How could we manage target >>> mode enablement without code mod or hard pci id partitioning ? I >>> know individual pci unbind/bind could work, but its been frowned >>> upon as a long term option. Same thing goes for module parameters >>> to select which ports do what role. >> That indeed is a problem. >> >> Ideally we should be able to set the required mode on a per-port base; >> having it per PCI device might be too coarse. Unless you represent >> each port as a PCI function; not sure if that's the case, though. > > It seems to be the case. > At least a dual port FC HBA (SLI-3) has two PCI functions. > >> If we were to allow to set the mode on a per-port base we could easily >> implement kernel parameters like fctarget=WWPN and/or >> fcinitiator=WWPN; NVMe could be treated similarly. >> And have a config option specifying if the default FC mode should be >> initiator or target. > > The old lpfc+lpfc_scst combination and also qla2xxx+tcm_qla2xxx allow > simultaneous initiator and target mode on the same port. I guess this > won't be possible with a split driver. > Which was kinda the point of this entire conversation ... Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage hare@xxxxxxxx +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg)
