Hi Chandra, > > I think it's very heavy to move all pages, which are mapped to removing > > regions, to new classes every time. It always happens when doing exec() > > or exit(), while munmap and closing file don't. > > Pages associating with libc.so or text of shells might move around > > the all classes. > > > > IMHO, it would be enough to just leave them as they are. > > These pages would be released a little later if no class touch them, > > or they might be accessed from another class to migrate another > > class, or they might reused in the same class. > > No, it will be incorrect, as the class that is using the page doesn't need > these pages anymore, we should not be charging them for those pages. > > May be we should do something light while keeping the accounting proper. > Any ideas ?
I understand your intention. But I don't think it's always proper. It wouldn't be bad idea to leave pages for perl scripts launched by Apache, as they may be reused soon. Each class may tend to re-execute the same programs. OTOH, pages as a cache of closed file may not be reused by the same class again, though they're counted as valid pages for the class. I guess both of them are in gray area. > > I feel it's not needed to move these pages in hurry. > > I prefer the implementation light. > > What do you think? > > > > > > BTW, the memory controller would be a good new to video streaming > > guys, I guess. Thanks, Hirokazu Takahashi. ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
