On Mon, Nov 30, 2009 at 02:01:45PM -0600, Todd Rimmer wrote:
>
> If a given architecture rounds sizeof(transport) up to 16 bits or 32 bits,
> then the replacement field should be uint16_t or uint32_t respectively,
> otherwise existing binary applications which fetch transport will fetch
> additional undefined bytes which follow it in the new structure.
>
> The big question is whether all presently supported architectures use the
> same size for enum?
>
> I did a quicky test program and on SLES10 x86_64 sizeof(an enum) is 32 bits.
> Hence uint8_t would break binary compatibility on that platform.
>
You probably refer to binary compatibility between defferent versions
of the RDMAoE libibverbs (e.g. the one with enum and the one with
uint8_t). I think this is not a big issue and recompiling should solve
that.
--
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
