In addition to this, it seems that 'Execute In Place' technology would also deliver memory savings in a z/VM environment. I attended an excellent session on this at the Share conference. Basically you create a xip2 partition and move commonly executed programs there. The xip2 file system maps the files to DCSS to deliver memory savings. The programs are pre-loaded in the DCSS and when Linux needs to load a page upon page fault, it is given a reference to the page in DCSS. Seems neat! __________________________________________ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840
Adam Thornton <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 03/04/2005 12:49 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: Shared file systems and conversion pain..... On Mar 4, 2005, at 2:31 PM, James Melin wrote: > My boss is asking me what parts of a Linux file system can be shared. > > My somewhat generic answer was 'The parts that can be guaranteed to > only > ever be read only'. > > He countered that he read it could be done. I said that if we > designing > for that from the word go, it would be significantly easier to do > than to > retrofit it into a dozen guests. > > So the question is, whom on the list has had experience with trying to > share as much of the file system as is possible, and what did you > choose to > share? Was it worth the hassle of backfitting it or did you go forward > with > that design in mind. If you retrofitted it, what did you learn, and > what > should we avoid should we choose to do this? > Sharing /usr is easy and gets you 80% of the benefit. Using basevol/guestvol overlays gets you the rest of the way but is significantly more complicated. The hard part is applying service in a consistent manner across guests. Adam ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
