Jeff Garzik wrote:
Fair enough, though I definitely lean towards some use of sysfs / device
model for AN-style events specifically. The media change events are
generated by the device, not the transport, and we should definitely
have an object in the device model that represents the device (
James Smart wrote:
For FC, we have several async events, and allow for LLDDs to send their own
data or augment the generic transport event w/ additional LLDD-data. The
infrastructure is implemented generically within the scsi midlayer.
We are using Netlink w/ broadcasts to deliver the events rath
could support any number of tools concurrently listening
for
change events. To date, this has worked very well. You may want to consider
this,
especially if the types of events is expected to grow beyond the simple "change"
notification.
-- james s
>List: linux-kernel
>Subject:
Kristen Carlson Accardi wrote:
When we get an SDB FIS with the 'N' bit set, we should send
an event to user space to indicate that there has been a
media change. The ahci host controller will send the
event via KOBJ_CHANGE uevent.
Signed-off-by: Kristen Carlson Accardi <[EMAIL PROTECTED]>
+st
When we get an SDB FIS with the 'N' bit set, we should send
an event to user space to indicate that there has been a
media change. The ahci host controller will send the
event via KOBJ_CHANGE uevent.
Signed-off-by: Kristen Carlson Accardi <[EMAIL PROTECTED]>
Index: 2.6-mm/drivers/ata/ahci.c
=
5 matches
Mail list logo
