> > the management app, there is no getting around knowing HCTL
> mapping.
> > The app must know the HCTL quad of a logical drive.
>
> Actually, if that's all you're trying to do, what about
>
> echo '- - -' > /sys/class/scsi_host/host<n>/scan
>
> That'll trigger a rescan of the entire card and the device
> will be found and added?
For this to happen, the applications must at lease know 'n' in host<n>,
otherwise it will have to trigger a rescan on all controllers. Which would
be an overkill. How about publishing the adapter class attribute as well?
This would allow applications to correlate the adapter handle with the class
attribute.
>
> Then, if you simply publish your LD number as an extra
> parameter of the device, you can look through /sys to find it.
Taken
Apologize for the late post, we were evaluating your feedback. It looks
good, thanks!
--------
Atul Mukker
Architect, Drivers and BIOS
LSI Logic Corporation
On Thu, 2005-01-06 at 09:20 -0500, Mukker, Atul wrote:
> For this to happen, the applications must at lease know 'n' in host<n>,
> otherwise it will have to trigger a rescan on all controllers. Which would
> be an overkill. How about publishing the adapter class attribute as well?
> This would allow applications to correlate the adapter handle with the class
> attribute.
I don't see why not ... it's your driver, you can publish whatever extra
information you need as scsi_device attributes; that was one of the
designs of the extensible attribute system.
> Apologize for the late post, we were evaluating your feedback. It looks
> good, thanks!
Great ... so the problem is now solved and just needs to be implemented.
James