lkml.org 
[lkml]   [2007]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC] Documentation about unaligned memory access
    From
    Date

    > Sidenote: in the above example, you may wish to reorder the fields in the
    > above structure so that the overall structure uses less memory. For example,
    > moving field3 to sit inbetween field1 and field2 (where the padding is
    > inserted) would shrink the overall structure by 1 byte:
    >
    > struct foo {
    > u16 field1;
    > u8 field3;
    > u32 field2;
    > };

    You can reorder to u32, u16, u8 order and save another byte :)

    A reference to pahole could be appropriate here, and probably a small
    note that some large existing structures like netdev have deliberate
    holes to achieve cache alignment.

    johannes
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2007-11-26 16:51    [W:9.400 / U:0.084 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site