On 09/13/05 05:23, Douglas Gilbert wrote: > Luben Tuikov wrote: >>The questiong is _what_ to do on this event. This is a complex >>answer and I'd rather have a _SES_ layer (or at least a logical >>module/library) to handle those as storage vendors want this, >>_right now_. > > > Simple answer: generate a hotplug event and let a > user application that cares worry about it. No > need for a SES layer in the kernel. Well, that sounds ok, but it maybe the case that the SES device wants to say something about the SAS devices on the same level. So even if userspace gets it, it would have nothing to do with it, because of the _type_ of SES device/event/etc. (User space can be notified anyway, which is perfectly fine). >>In fact, I've some patches to submit regarding SES devices >>on the domain, but I wanted to _trim *down*_ the politics, >>_not_ escalate them. > > > Oh no, not a sysfs representation of SES abstractions :-) No, not that. Luben - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
