Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

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 >>>

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

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

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On 06/13/2017 01:08 AM, James Smart wrote: > On 5/16/2017 12:59 PM, Roland Dreier wrote: >> On Sun, Mar 5, 2017 at 8:35 AM, Sebastian Herbszt wrote: >>> Just like Hannes I do favour integration. I guess it could be >>> comparable to qla2xxx + tcm_qla2xxx, lpfc + lpfc_scst and >>>

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

James, > To start this effort, I'd like a bcmlpfc directory to be made within > the drivers staging tree. The directory would be populated with the > efct driver and a copy of the existing lpfc driver. Work can then > commence on refactoring lpfc and creating the libraries and > integrating the

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On 06/13/2017 01:08 AM, James Smart wrote: > Here's what I'd like to propose for a direction: > 1) Create an initiator driver and a target driver. For now, initiator > would support both SCSI and NVME initiator. Target would support SCSI > and NVME target. > 2) SLI3 support would be contained

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

Hi James, I like the plan except for one bit: The staging tree will be a major pain due to the rules for applying to it and all the whitespace cleanup junk you'll get. I would storngly recommend to you to do this with a non-mainline tree instead. I'd be happy to help you maintaining it if you

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On 5/16/2017 12:59 PM, Roland Dreier wrote: On Sun, Mar 5, 2017 at 8:35 AM, Sebastian Herbszt wrote: Just like Hannes I do favour integration. I guess it could be comparable to qla2xxx + tcm_qla2xxx, lpfc + lpfc_scst and lpfc + tcm_lpfc. That approach might even help Bart with

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On Sun, Mar 5, 2017 at 8:35 AM, Sebastian Herbszt wrote: > Just like Hannes I do favour integration. I guess it could be > comparable to qla2xxx + tcm_qla2xxx, lpfc + lpfc_scst and > lpfc + tcm_lpfc. That approach might even help Bart with his > target driver unification if he

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On Mon, 2017-02-27 at 15:28 -0800, James Smart wrote: > I'd like to announce the availability of the Broadcom (Emulex) FC Target > driver - efct. Hello James, Sorry but I have not yet had the time to do a full review. But I would like to already share the following feedback: *

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On Sun, 2017-03-05 at 17:35 +0100, Sebastian Herbszt wrote: > Just like Hannes I do favour integration. I guess it could be > comparable to qla2xxx + tcm_qla2xxx, lpfc + lpfc_scst and > lpfc + tcm_lpfc. That approach might even help Bart with his > target driver unification if he didn't give up on

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

Nicholas A. Bellinger wrote: > Hi James & Co, > > Adding target-devel and Sebastian CC' > > On Mon, 2017-02-27 at 15:28 -0800, James Smart wrote: > > I'd like to announce the availability of the Broadcom (Emulex) FC > > Target driver - efct. > > This driver has been part of the Emulex OneCore

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

Hi James & Co, Adding target-devel and Sebastian CC' On Mon, 2017-02-27 at 15:28 -0800, James Smart wrote: > I'd like to announce the availability of the Broadcom (Emulex) FC Target > driver - efct. > This driver has been part of the Emulex OneCore Storage SDK tool kit for > Emulex > SLI-4

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On 02/28/2017 07:14 PM, James Smart wrote: > > On 2/28/2017 8:34 AM, Hannes Reinecke wrote: >> Can you clarify these? >> Are these 'just' resource allocation problems or something else, too? > > Most are resource allocation - buffer pools, dma pools, pages for > resources, and hw resource

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

On 2/28/2017 8:34 AM, Hannes Reinecke wrote: Can you clarify these? Are these 'just' resource allocation problems or something else, too? Most are resource allocation - buffer pools, dma pools, pages for resources, and hw resource allocation splits. However, async receive RQ policies are a

Re: [ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

Hi James, On 02/28/2017 12:28 AM, James Smart wrote: > I'd like to announce the availability of the Broadcom (Emulex) FC Target > driver - efct. > This driver has been part of the Emulex OneCore Storage SDK tool kit for > Emulex > SLI-4 adapters. The SLI-4 adapters support 16Gb/s and higher

[ANNOUNCE]: Broadcom (Emulex) FC Target driver - efct

I'd like to announce the availability of the Broadcom (Emulex) FC Target driver - efct. This driver has been part of the Emulex OneCore Storage SDK tool kit for Emulex SLI-4 adapters. The SLI-4 adapters support 16Gb/s and higher adapters. Although this kit has supported FCoE in the past, it is