The case of the overly anonymous anon_vma
The case of the overly anonymous anon_vma
Posted Apr 23, 2010 13:41 UTC (Fri) by rilder (guest, #59804)In reply to: The case of the overly anonymous anon_vma by i3839
Parent article: The case of the overly anonymous anon_vma
Even I feel the same. The scenario "In a workload with 1000 child processes and a VMA with 1000 anonymous pages per process that get COWed," -- may not arise in a normal desktop workload. In such as case won't this introduce additional overhead, unless this feature is introduced as a CONFIG variable which I don't think it is.
Posted Apr 23, 2010 16:17 UTC (Fri)
by i3839 (guest, #31386)
[Link]
In addition to that, anon_vma apparently didn't solve the problem well, but instead of replacing it with something that does, more kludges are added on top of it. I got the feeling that there's some much more elegant solution waiting for someone to find it.
The case of the overly anonymous anon_vma
Not only that, if the anon_vma isn't used for file caches, but only for anonymous pages then the whole thing seems dubious when swap is disabled.