On Linux this limits the number of maps per mm struct.
We don't limit mappings, return a suitable large value.
Details
Details
- Reviewers
emaste - Group Reviewers
Linux Emulation - Commits
- rGb3c809b96f77: linprocfs: Add /proc/vm/max_map_count
rG7e2a45111937: linprocfs: Add /proc/vm/max_map_count
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 45767 Build 42655: arc lint + arc unit
Event Timeline
Comment Actions
Seems fine to me. Does Linux have a default high value equivalent to "no limit?" I'd be slightly worried that applications would be unprepared to handle extremely large values but I imagine INT32_MAX is unlikely to be a problem.
Comment Actions
Linux limits it to 65530 due to Linux coredump method restrictions, described here https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/mm.h?h=v5.17
I don't think the number matters here, we can return USHORT_MAX-5 as in the Linux, also Illumos also limits it to some high value