Displaying 5 results from an estimated 5 matches for "kcompactd".
2019 Oct 02
0
DANGER WILL ROBINSON, DANGER
...rget anon VMA, but I guess this breaks the VMA. Is this recommended?
The mirror vma should not be an anon vma.
>
> Then, mapping anon pages from one VMA to another without fixing the
> refcount and the mapcount breaks the daemons that think they're working
> on a pure anon VMA (kcompactd, khugepaged).
Note here the target vma ie the mirroring one is a mmap of device file
and thus is skip by all of the above (kcompactd, khugepaged, ...) it is
fully ignore by core mm.
Thus you do not need to fix the refcount in any way. If any of the core
mm try to reclaim memory from the original...
2019 Oct 02
2
DANGER WILL ROBINSON, DANGER
...s breaks the VMA. Is this recommended?
>
> The mirror vma should not be an anon vma.
>
>>
>> Then, mapping anon pages from one VMA to another without fixing the
>> refcount and the mapcount breaks the daemons that think they're working
>> on a pure anon VMA (kcompactd, khugepaged).
>
> Note here the target vma ie the mirroring one is a mmap of device file
> and thus is skip by all of the above (kcompactd, khugepaged, ...) it is
> fully ignore by core mm.
>
> Thus you do not need to fix the refcount in any way. If any of the core
> mm try t...
2019 Oct 02
2
DANGER WILL ROBINSON, DANGER
...s breaks the VMA. Is this recommended?
>
> The mirror vma should not be an anon vma.
>
>>
>> Then, mapping anon pages from one VMA to another without fixing the
>> refcount and the mapcount breaks the daemons that think they're working
>> on a pure anon VMA (kcompactd, khugepaged).
>
> Note here the target vma ie the mirroring one is a mmap of device file
> and thus is skip by all of the above (kcompactd, khugepaged, ...) it is
> fully ignore by core mm.
>
> Thus you do not need to fix the refcount in any way. If any of the core
> mm try t...
2025 May 07
4
[Bug 3822] New: --with-linux-memlock-onfault causes segfaults with some combinations of PAM modules
...rwarding packets and shouldn't be doing anything like as much memory
allocation as it does while establishing a connection. It's perhaps
not quite as good for the stated rationale of
6c49e5f7dcaf886b4a702a6c003cae9dca04d3ea (always being able to connect
even while the system is under heavy kcompactd load), but it should
still help with established connections.
For now I'm just going to disable --with-linux-memlock-onfault, but I
thought I should let you know in case you have any other ideas.
--
You are receiving this mail because:
You are watching the assignee of the bug.
2019 Aug 09
6
[RFC PATCH v6 71/92] mm: add support for remote mapping
From: Mircea C?rjaliu <mcirjaliu at bitdefender.com>
The following two new mm exports are introduced:
* mm_remote_map(struct mm_struct *req_mm,
unsigned long req_hva,
unsigned long map_hva)
* mm_remote_unmap(unsigned long map_hva)
* mm_remote_reset(void)
* rmap_walk_remote(struct page *page,
struct rmap_walk_control *rwc)
This patch