diff options
| author | David Hildenbrand <david@redhat.com> | 2024-05-02 11:52:59 +0300 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2024-05-07 20:36:58 +0300 |
| commit | b8a2528835b31718286e7436529917e1f521bf6f (patch) | |
| tree | a34bf516f8b77c9e5cfa8a498ef440a15c21bdb6 /Kbuild | |
| parent | 4bf6a4ebc59201bcd12c932f25edda4c3e36e5df (diff) | |
| download | linux-b8a2528835b31718286e7436529917e1f521bf6f.tar.xz | |
mm/hugetlb: document why hugetlb uses folio_mapcount() for COW reuse decisions
Let's document why hugetlb still uses folio_mapcount() and is prone to
leaking memory between processes, for example using vmsplice() that still
uses FOLL_GET.
More details can be found in [1], especially around how hugetlb pages
cannot really be overcommitted, and why we don't particularly care about
these vmsplice() leaks for hugetlb -- in contrast to ordinary memory.
[1] https://lore.kernel.org/all/8b42a24d-caf0-46ef-9e15-0f88d47d2f21@redhat.com/
Link: https://lkml.kernel.org/r/20240502085259.103784-3-david@redhat.com
Signed-off-by: David Hildenbrand <david@redhat.com>
Suggested-by: Peter Xu <peterx@redhat.com>
Cc: Muchun Song <muchun.song@linux.dev>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions