> You'll still be required to convert it to/from enum when > building/parsing CM messages, for example. > Also, why should it be an int if only specific values are allowed? The enum values are IB specification specific, and are incomplete (note the lack of Ethernet mtu sizes). Let the IB centric code deal with the conversion, and let the rest of the API be reasonable. The IB CM uses the mtu value in the path record, which is fine. Then maybe someday userspace can get access to the real mtu sizes as well... -- 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
