> > #define IB_NL_DATA_TYPE_INVALID 0x0000 > > #define IB_NL_DATA_TYPE_NAME 0x0001 > > #define IB_NL_DATA_TYPE_ADDRESS_IP 0x0002 > > #define IB_NL_DATA_TYPE_ADDRESS_IP6 0x0003 > > #define IB_NL_DATA_TYPE_PATH_RECORD 0x0004 > > #define IB_NL_DATA_TYPE_USER_PATH_REC 0x0005 > > Do we need both PATH_RECORD and USER_PATH_REC? > > I'm having trouble determining when the OP == QUERY_PATH and the DATA_TYPE > != > PATH_RECORD. > > Why don't we remove "QUERY_PATH" above and allow OP == RESOLVE and > DATA_TYPE == > PATH_RECORD be a "query for path record"? I agree with Ira. Conceptually, there are at least 2 pieces of information that need to be provided. The format/type of the input data and the desired output data. It looks like Kaike is using the ibacm protocol as a base. I *think* the QUERY_PATH operation for ibacm forced an SA query. (It is used for testing purposes. That, or I'm remembering something else and associating it with QUERY_PATH.) The desired output data can either be encoded as part of the operation or separated into its own field. -- 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
