On Wed, 20 Dec 2017 07:55:50 -0800 Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > From: Matthew Wilcox <mawilcox@xxxxxxxxxxxxx> > > Neither of these values get even close to 256; compound_dtor is > currently at a maximum of 3, and compound_order can't be over 64. > No machine has inefficient access to bytes since EV5, and while > those are still supported, we don't optimise for them any more. So we couild fit compound_dtor and compound_order into a single byte if desperate? > This does not shrink struct page, but it removes an ifdef and > frees up 2-6 bytes for future use. Can we add a little comment telling readers "hey there's a gap here!"? -- 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>
