Re: [patch 3/3] libata: handle AN interrupt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 rather than kobject_uevent(). We considered using a variant of kobject events, but the general consensus was we didn't want to wrap transport events into the kobject infrastructure, and using netlink natively allowed for transport data to be sent with the event. Additionally, with the broadcast, we 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.


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 (if we don't already).

I could see transport-based events being delivered to a different endpoint, because transport events differ from device events.

	Jeff


-
To unsubscribe from this list: 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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux