On Fri, 2011-07-08 at 09:52 +0530, Subranshu Patel - ERS, HCL Tech
wrote:
> Thanks for the clarification.
> 
> > The target is still evolving and as some point we may have some target
> > specific code in fcoe-utils, it's just not the case right now.
> 
> From the SCST site (http://scst.sourceforge.net), it seems that FCST 
> directory (under SCST repository) is the fcoe target.
> Is this FCST implementation different from the old target present in 
> Open-FCoE code archives (git).
> 
I did very little inspection, so I could be wrong, but I believe that
what is in the SCST repository would be Fibre Channel code that the SCST
infrastructure needs. That code then plugs into the libfc FC4 provider
hooks implemented by Joe, or at least it did at one point.

libfc's FC4 provider interface is upstream and is also used by TCM.
Since TCM is upstream we're (mostly) guaranteed that TCM will always at
least compile against libfc. Since SCST is not upstream it isn't as easy
to ensure that it keeps up with any changes. That being said, I can't
think of how the interface has changed at all since it was committed, so
I'd guess that it would still work with SCST.

> Both of them are SCST based implementation.
> In the future, will FCST will get merged into open-fcoe?
> 
I wouldn't think of "open-fcoe" as anything really. I keep a kernel tree
so that I can coordinate changes and push them to linux-scsi, where
they'll be collected and pushed to Linus' tree. We have the fcoe-utils,
libhbalinux and hbaapi_build repositories, which contain user space
libraries and utilities that work with the Linux kernel modules (libfc,
libfcoe and fcoe). It's the combination of the kernel and the user space
utilities that allows the user to do SW FCoE. I think your question
should be rephrased to, "When will FCST get merged into the upstream
kernel?" Unfortunately, this is really a question for the core kernel
maintainers and SCST team.

Hope this helps, //Rob
_______________________________________________
devel mailing list
[email protected]
https://lists.open-fcoe.org/mailman/listinfo/devel

Reply via email to