|
From: Julian S. <js...@ac...> - 2005-10-04 15:16:23
|
> > I think the old system mostly got away with it because there was a > > special flag for shared memory which probably stopped it merging most > > of the time. > > I've had a go at fixing this and my best scheme so far is to > create a new SkShmC segment type for shared memory segments and > then prevent the address space manager from merging those segments. > > The only problem with that is notifying aspacem that the memory is > a shared memory segment - I've stolen a bit from the mmap flags at > the moment but that is nasty so I'm thinking that adding a special > notify function to aspacem for shm segments might be better? SkShmC and a new notify function sounds good to me. Can I just check (semantics): a shared memory segment cannot also be a file or anonymous mapping, is that correct? J |