Re: [Qemu-devel] [PATCH v9 36/37] RFC: qapi: Adjust layout of FooList types

2016-01-29 Thread Markus Armbruster
Eric Blake writes: > On 01/28/2016 08:34 AM, Markus Armbruster wrote: >> Eric Blake writes: >> >>> By sticking the next pointer first, we don't need a union with >>> 64-bit padding for smaller types. On 32-bit platforms, this >>> can reduce the size of

Re: [Qemu-devel] [PATCH v9 36/37] RFC: qapi: Adjust layout of FooList types

2016-01-28 Thread Markus Armbruster
Eric Blake writes: > By sticking the next pointer first, we don't need a union with > 64-bit padding for smaller types. On 32-bit platforms, this > can reduce the size of uint8List from 16 bytes (or 12, depending > on whether 64-bit ints can tolerate 4-byte alignment) down to

Re: [Qemu-devel] [PATCH v9 36/37] RFC: qapi: Adjust layout of FooList types

2016-01-28 Thread Eric Blake
On 01/28/2016 08:34 AM, Markus Armbruster wrote: > Eric Blake writes: > >> By sticking the next pointer first, we don't need a union with >> 64-bit padding for smaller types. On 32-bit platforms, this >> can reduce the size of uint8List from 16 bytes (or 12, depending >> on

[Qemu-devel] [PATCH v9 36/37] RFC: qapi: Adjust layout of FooList types

2016-01-19 Thread Eric Blake
By sticking the next pointer first, we don't need a union with 64-bit padding for smaller types. On 32-bit platforms, this can reduce the size of uint8List from 16 bytes (or 12, depending on whether 64-bit ints can tolerate 4-byte alignment) down to 8. It has no effect on 64-bit platforms (where