On Mon, 2010-04-12 at 13:06 -0500, micha...@cs.wisc.edu wrote:
> From: Mike Christie <micha...@cs.wisc.edu>
>
> Not all iscsi drivers support ibft. For drivers like be2iscsi
> that do not but are bootable through a vendor firmware specific
> format/process this patch moves the sysfs interface from the ibft code
> to a lib module. This then allows userspace tools to search for iscsi boot
> info in a common place and in a common format.
>
> ibft iscsi boot info is exported in the same place as it was
> before: /sys/firmware/ibft.
>
> vendor/fw boot info gets export in /sys/firmware/iscsi_bootX, where X is the
> scsi host number of the HBA. Underneath these parent dirs, the
> target, ethernet, and initiator dirs are the same as they were before.
> ...
===8<---- snip
> +#endif
> --
> 1.6.6.1
>
Mike,
To be clear, this patch will put ibft data into /var/firmware/ibft only
for those devices that actually have it, but not create a tree for say
NICs that do not currently support it? Wondering if this is a universal
gizmo that will always populate the tree that I can rely on from
userspace during boot.
Thanks,
-C
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
