Linux-VServer example results for sharing vs. separate mappings ...
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Ethan Solomita
I suggest a variant on what Andrew says: don't change reclaim.
Instead, when referencing a page, don't mark the page as referenced if the current task is not permitted to allocate from the page's node. I'm thinking in terms of cpusets, with each task having a nodemask ofmems_allowed. This may result in a page being thrown out unnecessarily and brought back in from disk, but when memory is tight that is what happens. An optimization might be to keep track of who is referencing the page and migrate it to their memory instead of reclaiming it, but that would require reclaim to know the task/cpuset/container of the referencing task.
If you are neaar reclaim and the page from that other node hasn't been touched recently, maybe you could steal it. Off cause this is only applicable if the checks are cheap enough.
Signature · 4 lines
Funny quotes:
40. Isn't making a smoking section in a restaurant like making a peeing
section in a swimming pool?
Friß, Spammer: [email protected] [email protected]