On Fri, 30 May 2008, Mike Travis wrote: > > No there is no limit. It just wastes lots of space (pointer arrays, > > alignment etc) that we could use to configure sufficiently large per cpu > > areas. > > Is there any reason why the per_cpu area couldn't be made extensible? Maybe > a simple linked list of available areas? (And use a config variable and/or > boot param for initial size and increment size?) [Ignoring the problem of > reclaiming the space...] cpu alloc v2 had an extendable per cpu space. You have the patches. We could put this on top of this patchset if necessary. But then it not so nice and simple anymore. Maybe we can rstrict the use of cpu alloc instead to users with objects < cache_line_size() or so? -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
