> > I've left the question of whether or not > > the value should be the number of randomized bits (current situation) > > or the size of the address space chunk affected up to akpm@. > > Does it matter much? It can always be changed later if it proves to be > a problem. Motivation for the suggestions was to get rid of the page size consideration in setting default min/max Kconfig values to reduce line count, otherwise both options are about equivalent. > > Please let me know what else should be done in v6 to keep these in. > > It sounds like all we need to do at present is to fix this build error? My apologies, I thought this was the one related to CONFIG_MMU=n. I've reproduced locally and will look into this on Monday. Thank You, Dan On Fri, Dec 4, 2015 at 5:01 PM, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, 4 Dec 2015 16:56:19 -0800 Daniel Cashman <dcashman@xxxxxxxxxx> wrote: > >> I've left the question of whether or not >> the value should be the number of randomized bits (current situation) >> or the size of the address space chunk affected up to akpm@. > > Does it matter much? It can always be changed later if it proves to be > a problem. > >> Please let me know what else should be done in v6 to keep these in. > > It sounds like all we need to do at present is to fix this build error? -- Dan Cashman -- 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>