[resending to reply-all, sorry Jeff] On Mon, Jul 8, 2013 at 9:26 AM, Jeff Squyres (jsquyres) <[email protected]> wrote: >> So what happens if I have an old application binary, and I run against >> a new libibverbs without recompiling?
>> Also it seems that I'm forced to change my source code to be able to >> compile against new libibverbs? > I previously sent an ABI-preserving version of this patch, but it was hated > by Doug Ledford and (eventually) Jason Gunthorpe. > After long discussion (see thread starting here: > http://www.spinics.net/lists/linux-rdma/msg15951.html), they decided that > they wanted a clean break that forces both source code and ABI changes, which > resulted in this patch. > I personally don't care which way this goes; I just want the ability to have > non-enum MTU values. So I guess I need to go back and read all of that thread carefully, but I don't think that silently breaking old binaries and also breaking sources is the right way to go. What about preserving the behavior of the existing API / ABI and then adding a new function to return the size of the maximum datagram for a device? - R. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
