On Thu, Dec 10, 2015 at 02:26:11PM +0200, Haggai Eran wrote:
On 07/12/2015 22:43, Dennis Dalessandro wrote:
+ /*
+ * Drivers will need to support a number of notifications to rvt in
+ * accordance with certain events. This structure should contain a mask
+ * of the supported events. Such events that the rvt may need to know
+ * about include:
+ * port errors
+ * port active
+ * lid change
+ * sm change
+ * client reregister
+ * pkey change
Where are the event values defined?
They aren't really yet. A lot of the comments like this were put in and made
available on GitHub for an early look into the design. This will all get
cleaned up as the code continues to come together.
+ *
+ * There may also be other events that the rvt layers needs to know
+ * about this is not an exhaustive list. Some events though rvt does not
+ * need to rely on the driver for such as completion queue error.
+ */
+ int rvt_signal_supported;
What will rvt do if it learns that the device doesn't support some of
the events?
Good question. I don't really have a great answer right now. Mostly it sort
of depends on what events we end up. If it's something critical rdmavt will
have to check during the registration and fail the call. This is not yet
implemented in the two patch sets posted.
-Denny
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
