On Mon, Nov 14, 2022 at 05:36:29PM -0600, Kalra, Ashish wrote:
> But there is still added complexity of handling hugepages as part of
> reclamation failures (both HugeTLB and transparent hugepages) and that
Why?
You want to offline pfns of 4K pages. What hugepages?
> means calling more static functions in mm/memory_failure.c
>
> There is probably a more appropriate handler in mm/memory-failure.c:
>
> soft_offline_page() - this will mark the page as HWPoisoned and also has
> handling for hugepages. And we can avoid adding a new page flag too.
So if some other code wants to dump the amount of all hwpoisoned pages,
it'll dump those too.
Don't you see what is wrong with this picture?
And btw, reusing the hwpoison flag
PG_offlimits = PG_hwpoison
like previously suggested doesn't help here either.
IOW, I really don't like this lumping of semantics together. ;-\
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
