> -----Original Message----- > From: Hefty, Sean > > > Even with a map I think having IB_MTU_1500 will cause some confusion > > as this is not an "IB" MTU. It seems an alternate enum name like > RDMA_MTU_1500 is better. > > Couldn't these be usable MTU's for RoCE?
I guess so, I don't have much experience with RoCE. If that is the case the RoCE annex might look at reserving these values in the spec? > > In hindsight, the user space API never should have exposed the mtu as an > enum... > > Since an enum is an int, and we're never going to have anything with an mtu > <= 5 bytes, couldn't we just store all new mtu values directly as their byte > value? That seems like a pretty good idea. Ira -- 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
