On 04/22/2013 02:00 PM, Jeff Squyres (jsquyres) wrote: > 2. Change all instances of ib_mtu/ibv_mtu to an int. Code such as > "switch(mtu) case IBV_MTU_1024: ..." will need to be updated to > "switch(mtu) case 1024: ...". > > PRO: solves the problem for all MTU values > PRO: eliminates the num-to-int translation functions > CON: much driver code will need to be updated per above, and also > update logic checking for out-of-bounds MTU calues > CON: similarly, userspace apps will need to be updated; it might be > worthwhile to bump libibverbs to 2.x, and then intentionally change > the MTU field names in ibv_port_attr and ibv_qp_attr so that apps > using those fields will fail to compile with libibverbs 2.x > (and therefore forcibly realize they need to adapt to the new > int MTU values)
I was actually thinking that an ibverbs API version 2.0 might be an interesting way to go. The proliferation of non-IB link layers providing the verbs API make some of the original assumptions of IB link layer in the original API obsolete. But, if we were to do that, I'd take some time to really think the issue over and try to catch all of the needed updates in one go. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
