On Fri, 26 Apr 2002 07:21:57 -0400, [EMAIL PROTECTED] wrote: >> > It took me a surprising amount of time to realize that /usr doesn't >> > retain any large quantities of data that would end up residing in a >> > buffer cache- R/O data is of very limited utility. I don't think >> > we're likely to be overrun by people calling up the same man page >> > across all of the systems. >> >> Binaries including shared libraries are extremely likely to be used on all >> guests. Take glibc for starters. > > Shared libraries get paged in too, just like an executable, so > they don't live in the buffer cache. There's been some talk > about making such segments shared between VMs but (IMHO) that > will take a huge quantity of code which (again, IMHO) Linus > (_and_ all his lieutenants) are unlikely to accept, considering > how specialized it is (and how inapplicable to all other > environments).
I'm was thinking about how the VM - Linux/390 environment is like a NUMA archtitecture... so problems solved here might eventually find a wider audience. Local memory is the VM address space. Shared memory would be DCSS's that need special operations to attach at a distinct memory address, reading is smooth, writing/locking need special operations. The benefit, of having a read/only DCSS glibc which everyone shares would be amazing. Same for having a shared disk cache, although management of it would be tres hirsuite. john alvord
