|
From: Greg P. <gp...@us...> - 2005-09-11 03:44:21
|
Julian Seward writes: > The new manager also has the concept of a reservation segment. Such a > segment is not mapped, and so is similar to a free-space segment, but > with the difference that it will not attempt to allocate anything in > that space. This is perfect for Mac OS X's special "shared regions". Basically, this is a chunk of address space reserved for mapping some system shared libraries, if the process uses them. You don't want to try to put anything else there - either the kernel won't let you, or you'll really confuse the system if a library gets loaded later. > I think the real issue re spontaneous mappings is to have a > reliable way to know they have happened, and where the new mapping > is. On Linux that comes down to rescanning /proc/self/maps > after any event which might create such a mapping. I haven't seen any truly spontaneous mappings; there's always something in the transaction that says at least where the mapping is, even if it's unconvenient. Mac OS X has kernel API to enumerate the mappings, not unlike /proc/self/maps. > Anyway, that's the theory. Let me know ASAP if it is not what > Darwin needs. It's taken me most of this week to understand in detail > how the aspacemgr needs to be connected to the rest of system. > I hope to have something starting to work in the next couple of days. I like everything I've heard so far. -- Greg Parker gp...@ap... Runtime Wrangler |