On 1/19/06, Anne & Lynn Wheeler <[EMAIL PROTECTED]> wrote: > in one sense it is like extended memory on 3090 ... fast memory move > operations. however, real extended memory was real storage. dcss is > just another part of virtual memory. in theory you could achieve > similar operational characteristics just by setting up linux to have > larger virtual memory by the amount that would have gone to dcss > ... and having linux rope it off and treat that range of memory the > same way it might treat a range of dcss memory.
The experiment that I did some time ago is to carve out part of Linux "real" memory by defining a ram-disk in it, and then use that as swap device. As long as Linux does not need memory so much that it would swap for it, the ramdisk only reduces the footprint (good). When demand is higher and Linux continues to swap, you would disable that swap device and return the ramdisk to the kernel for normal use (certainly not intuitive). Unfortunately Linux will eventually also swap the ramdisk pages (ouch). But swapping to DCSS really was a side-effect of the facility. The real value should be in sharing (code and data). > one of the things i pointed out long ago and far away about running a > lru-algorithm under a lru-algorithm ... is that that things can get Yes, this is where CMM plays a significant role. Rob -- Rob van der Heij rvdheij @ gmail.com Velocity Software, Inc
