On Wed, Nov 25, 2015 at 06:31:41PM +0300, Andrey Ryabinin wrote: > > + /* scheduler bits, serialized by scheduler locks */ > > unsigned sched_reset_on_fork:1; > > unsigned sched_contributes_to_load:1; > > unsigned sched_migrated:1; > > + unsigned __padding_sched:29; > > AFAIK the order of bit fields is implementation defined, so GCC could > sort all these bits as it wants. We're relying on it doing DTRT in other places, so I'm fairly confident this'll work, otoh > You could use unnamed zero-widht bit-field to force padding: > > unsigned :0; //force aligment to the next boundary. That's a nice trick I was not aware of, thanks! -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>