Robert Love, on 01/15/2010 03:37 AM wrote: > On Thu, 2010-01-14 at 04:39 -0800, Jan Zelený wrote: >> Hi, >> I'd like to ask you about state of FCoE target code. I just tried to install >> the target on kernel 2.6.31.4 and there are some errors during compilation >> of >> open-fcoe-target. After a brief investigation I found that kernel >= 2.6.24 >> uses slightly different netdev functions than previous versions did and thus >> the code of open-fcoe-target doesn't compile. >> >> Do you guys have some plans for target code. I've read in wiki, that it is >> not >> your priority at the moment, so I'd like to know some details on this >> matter. >> Perhaps I can help you with it? >> > Hi Jan, > > You need a little background first. There are two competing SCSI > target infrastructure projects- SCST and STGT. STGT is upstream and SCST > is not. I'm not familiar enough with the SCST project to know exactly > where they are now in their upstream push, or what their plans are.
SCST is currently doing final preparations to be fully mainstream kernel ready. Then version 2.0 is going to be released, then patches for review and inclusion into mainstream kernel are going to be pushed. The delay since previous submission and review iteration was caused because, unfortunately, I and other members of the SCST community weren't able to fully dedicate us to implementing a sysfs-based interface for SCST instead of the currently used procfs-based interface. Basically, the sysfs interface is ready and fully usable now. Everybody can try it after downloading current SVN trunk as described at http://scst.sourceforge.net/downloads.html and then run "make disable_proc" in the root before build. I like new interface very much and it is a great step ahead. I'm currently adding to it few additional strokes to make it self-containing for all types of target and backend drivers. This feature will allow scstadmin[1] (as well as other similar management tools) to be implemented once and handle all current and future target and backend drivers, including implemented both in kernel and user spaces, without any internal changes. All the necessary information scstadmin will take directly from the sysfs interface. > Alternatively, Intel is in the process of refreshing the SCST based > target to a more current kernel. The intent is not to push it upstream. > We hope to publish this code in roughly 4-6 weeks. I'm not sure if the > code will be published here or on sourceforge. Great news! Vlad [1] Scstadmin is an utility, which allows doing SCST configuration using a text config file. Among other, it has the following great facilities: 1. A possibility to apply changes in the config file to currently running system. Only changes applied, so there are no any unneeded restarts and resets. 2. Generate a config file for currently running system. _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
