That thought occurred to me, but I thought it might be easier for the app developer if the api explicitly broke up the generic concepts of traps and notices into specific types.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Hefty, Sean Sent: Tuesday, August 10, 2010 3:43 PM To: Mike Heinz; [email protected]; Jason Gunthorpe Subject: RE: API for Proposal for adding ib_usa to the Linux Infiniband Subsystem > enum ibv_event_type { > ... > + IBV_EVENT_GID > ... > struct ibv_async_event { > union { > + struct ibv_gid_event *gid_event; > ... > + int ibv_reg_gid_event(struct ibv_context *context, uint8_t port_num); We need to get Roland's thoughts on this, since he maintains libibverbs. As just a thought, I think you can still use a more generic API with kernel checks to verify that an application has permission to register for certain types of events. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
