> > I mean there's stuff that's weirdly used for page table moving in mremap.cOK so I think we're (probably?) now agreed, I will submit a patch shortly that: a. puts everything in MEMORY MAPPING b. Drops mm/madvise.c, mm/msync.c from the list c. I commit to moving things out of the various files that truly belongs elsewhere
that should probably live in memory.c as well for instance.
Yes, and hopefully we can clearly frame what MEMORY MAPPING is supposed to contain. I tried to tackle it with "/proc/self/maps output", but that's probably not the complete story.
For example, maybe mbind() should, for example, at some point be separated out into into mbind.c (making use of mempolicy.c functionality?) and covered there as well? I really don't know, maybe it's not one of the mmap/munmap/mprotect/mremap/mseal/mlock gang after all.
-- Cheers, David / dhildenb
