> -----Original Message----- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > Subject: Re: [PATCH 2/2] Ad IB_MTU_1500|9000 enums. > > On Apr 4, 2013, at 1:57 PM, "Weiny, Ira" <ira.we...@intel.com> wrote: > > >> 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. > > > Agreed, but changing to an int would seem to have some fairly serious > backwards compatibility issues. > > What is the right way to move forward here? > > Just to re-state: our issue is that there does not seem to be any other way to > get the max UD message size without knowing the actual MTU (are we > incorrect about that?). Hence, using the IB-defined values is not really > sufficient.
I guess I am confused. Is this patch trying to support RoCE or a VNIC? 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
