* Usama Arif <usamaarif642@xxxxxxxxx> [250519 18:34]: > This series allows to change the THP policy of a process, according to the > value set in arg2, all of which will be inherited during fork+exec: > - PR_DEFAULT_MADV_HUGEPAGE: This will set VM_HUGEPAGE and clear VM_NOHUGEPAGE > for the default VMA flags. It will also iterate through every VMA in the > process and call hugepage_madvise on it, with MADV_HUGEPAGE policy. > This effectively allows setting MADV_HUGEPAGE on the entire process. > In an environment where different types of workloads are run on the > same machine, this will allow workloads that benefit from always having > hugepages to do so, without regressing those that don't. > - PR_DEFAULT_MADV_NOHUGEPAGE: This will set VM_NOHUGEPAGE and clear VM_HUGEPAGE > for the default VMA flags. It will also iterate through every VMA in the > process and call hugepage_madvise on it, with MADV_NOHUGEPAGE policy. > This effectively allows setting MADV_NOHUGEPAGE on the entire process. > In an environment where different types of workloads are run on the > same machine,this will allow workloads that benefit from having > hugepages on an madvise basis only to do so, without regressing those > that benefit from having hugepages always. > - PR_THP_POLICY_SYSTEM: This will reset (clear) both VM_HUGEPAGE and > VM_NOHUGEPAGE process for the default flags. > Subject seems outdated now? PR_DEFAULT_ vs PR_SET/GET_THP ? On that note, doesn't it make sense to change the default mm flag under PR_SET_MM? PR_SET_MM_FLAG maybe? Thanks, Liam
