On Sat, Mar 04, 2023 at 07:34:33AM +0000, Matthew Wilcox wrote: > The hard part is plugging your ears to the screams of the MM people > who are convinced that fragmentation will make it impossible to mount > your filesystem. One doesn't just need to plug your ears, one can also be prepared for that, should that actually end up being true, because frankly we don't have the evidence yet. And it's something I have slowly started to think about -- because -- why not be ready? In fact let's say the inverse is true, having the tooling to proove them wrong is also a desirable outcome and that begs the question of proper tooling to measure this, etc. Something probably more for an MM track. What would satifsy proof and what tooling / metrics used? It is *not* something that only is implicated by storage IO controllers and so what we're looking at a generic device issue / concern for memory fragmentation. *If* the generalization of huge page uses for something like bpf-prog-pack ends up materializing and we end up using it for even *all* module .text, *then* I *think* it something similar be a way to address that concern for devices with huge pages for CMA. This is one area where I think device hints for large IO might come in handy, we can limit such dedicated pools to only devices with hints and limit the amount of huge pages used for this purpose. But ask me 2 kernel releases from now again. Luis
