[SERVER-24133] Memory policy update from the mongod process Created: 12/May/16  Updated: 02/Aug/23  Resolved: 02/Aug/23

Status: Closed
Project: Core Server
Component/s: Admin, Internal Code
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor - P4
Reporter: Ricardo Lorenzo Assignee: Irwin Dolobowsky
Resolution: Won't Do Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-18763 Use get_mempolicy() or /proc/zoneinfo... Backlog
Sprint: Execution Team 2020-11-16, Execution Team 2020-11-30
Participants:
Case:

 Description   

As per the Linux kernel documentation, there are three different system calls to control the memory policy. These calls always affect only the calling task, the calling task's address space, or some shared object mapped into the calling task's address space.

The MPOL_INTERLEAVED mode specifies that page allocations be interleaved, on a page granularity, across the nodes specified in the policy. As mentioned before, those calls always affect only the calling task, so there is no way to invoke them outside of the specific process.

The numactl tool is packaged with the run-time version of the library containing the memory policy system call wrappers. This tool is convenient and flexible in order to run mongod and modify the memory policy for the process.

However, is there any chance for mongod to use the API calls to set the policy without requiring numactl? It will be easier for the users if this can be done in a transparent way.


Generated at Thu Feb 08 04:05:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.