An absolute prereq, not just a safety one. If it is not already draining, then there would be nothing to prevent new pages from being written on the device. It will still be somewhat tricky because the page may already be in storage, in use by a virtual machine. Also, it may be part of a DCSS, in which case, only your private copy (resulting from your changing the page) will be paged out by your activity; others will still be referencing the original page.
Regards, Richard Schuh > > This might not be as hard as I thought. If the volume is > already drained for new traffic (probably a safety prereq for > this to happen), then determining pages on those volumes and > forcing page-in/page-out is probably safer than previously > thought. CP can maintain the appropriate interlocks if we > force CP to fault the page in, touch the page in a way that > forces CP to consider the page as dirty, and then allow the > normal page-out logic to determine the new location. It would > cause a fairly large burst in paging activity while running, > but that's probably not an big issue for the few times this > would get activated. > > Scratch, scratch, scratch... There's an itch in here somewhere. > > -- db >
