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

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:[patch 3/3] libata

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

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

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

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