On Tue, Sep 03, 2024 at 06:25:52PM GMT, John Hubbard wrote: > On 9/3/24 11:19 AM, Suren Baghdasaryan wrote: > > On Sun, Sep 1, 2024 at 10:16 PM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > On Sun, 1 Sep 2024 21:41:28 -0700 Suren Baghdasaryan <surenb@xxxxxxxxxx> wrote: > ... > > > We shouldn't be offering things like this to our users. If we cannot decide, how > > > can they? > > > > Thinking about the ease of use, the CONFIG_PGALLOC_TAG_REF_BITS is the > > hardest one to set. The user does not know how many page allocations > > are there. I think I can simplify this by trying to use all unused > > page flag bits for addressing the tags. Then, after compilation we can > > follow the rules I mentioned before: > > - If the available bits are not enough to address all kernel page > > allocations, we issue an error. The user should disable > > CONFIG_PGALLOC_TAG_USE_PAGEFLAGS. > > - If there are enough unused bits but we have to push last_cpupid out > > of page flags, we issue a warning and continue. The user can disable > > CONFIG_PGALLOC_TAG_USE_PAGEFLAGS if last_cpupid has to stay in page > > flags. > > - If we run out of addressing space during module loading, we disable > > allocation tagging and continue. The user should disable > > CONFIG_PGALLOC_TAG_USE_PAGEFLAGS. > > If the computer already knows what to do, it should do it, rather than > prompting the user to disable a deeply mystifying config parameter. > > > > > This leaves one outstanding case: > > - If we run out of addressing space during module loading but we would > > not run out of space if we pushed last_cpupid out of page flags during > > compilation. > > In this case I would want the user to have an option to request a > > larger addressing space for page allocation tags at compile time. > > Maybe I can keep CONFIG_PGALLOC_TAG_REF_BITS for such explicit > > requests for a larger space? This would limit the use of > > CONFIG_PGALLOC_TAG_REF_BITS to this case only. In all other cases the > > number of bits would be set automatically. WDYT? > > Manually dealing with something like this is just not going to work. > > The more I read this story, the clearer it becomes that this should be > entirely done by the build system: set it, or don't set it, automatically. The difficulty is that we don't know how many modules are going to be loaded, and an allyesconfig or allmodconfig is going to require quite a few bits - it's not something we can really predict or calculate. So there is some genuine trickyness here.
