There is a tool to write an access control table to
the adapter. This ACT specifies which virtual adapter
can access which ports and FCP LUNs ...
That's totally broken. most FC sans have zoning and access control,
but this is by no way a feature of the HBA. Your feature is totally
Doug,
Providing udev names is great. Makes it more user-frendly.
Btw., what do you think about this idea:
If lsscsi was enhanced to provide certain transport specific attributes, as
well,
then a user could easily look up the Linux device name of a logical unit
that he otherwise knows by its
James,
both Heiko and Andreas aren't available for several days.
Let me try to answer your questions.
You're look to be breaking the simplicity rules. Object lifetimes are
very tricky things to manage, so what I want you to explain is why you
have to make this more difficult buy making
Yes, the done() function needs to be wrapped (this isn't so much because
it
actually needs it as it is that you are calling mid layer code and you
need to
adhere to what it tells you locking semantics are, which in this case is
always hold the io_request_lock because that's how I keep myself
There is a patch for 2.2 at
http://open-projects.linuxcare.com/t3/index.html
I think, it only partly solves this multipathing issue.
I would like to see multipathing as one major requirement for a
restructered SCSI stack in 2.5.
Mit freundlichen Grüßen / with kind regards
Martin Peschke
IBM
5 matches
Mail list logo