mm: disable `vm.max_map_count' sysctl limit
Quoted 1 line
vm.max_map_count
I always thought it is some kind of algorithmic complexity limiter and kernel memory limiter. VMAs are under SLAB_ACCOUNT nowadays but ->mmap list stays:
$ chgrep -e 'for.*vma = vma->vm_next' | wc -l 41
In particular readdir on /proc/*/map_files .
I'm saying you can not simply remove this sysctl.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
[resent because I can't type]
Quoted 1 line
vm.max_map_count
I always thought it is some kind of algorithmic complexity limiter and kernel memory limiter. VMAs are under SLAB_ACCOUNT nowadays but ->mmap list stays:
$ chgrep -e 'for.*vma = vma->vm_next' | wc -l 41
In particular readdir on /proc/*/map_files .
I'm saying you can not simply remove this sysctl.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>