On Thu, Mar 23, 2023 at 07:51:05PM +0900, Kyungsan Kim wrote: > One problem we experienced was occured in the combination of hot-remove and kerelspace allocation usecases. > ZONE_NORMAL allows kernel context allocation, but it does not allow hot-remove because kernel resides all the time. > ZONE_MOVABLE allows hot-remove due to the page migration, but it only allows userspace allocation. No, that's not true. You can allocate kernel memory from ZONE_MOVABLE. You have to be careful when you do that, but eg filesystems put symlinks and directories in ZONE_MOVABLE, and zswap allocates memory from ZONE_MOVABLE. Of course, then you have to be careful that the kernel doesn't try to move it while you're accessing it. That's the tradeoff. > Alternatively, we allocated a kernel context out of ZONE_MOVABLE by adding GFP_MOVABLE flag. > In case, oops and system hang has occasionally occured because ZONE_MOVABLE can be swapped. I think you mean "migrated". It can't be swapped unless you put the page on the LRU list, inviting the kernel to swap it. > We resolved the issue using ZONE_EXMEM by allowing seletively choice of the two usecases. This sounds dangerously confused. Do you want the EXMEM to be removable or not? If you do, then allocations from it have to be movable. If you don't, why go to all this trouble?
