Our reason for not using it is the really high pressure of a very standardized server farm. In order to get this costeffective and useful you should have perhaps only three versions of readonly root filesystems used by all servers. It would be only three systems to upgrade, maximum.
Since it is XIP and already in memory, you will get fast boot/reboot and no essential module/lib will ever be paged out, so response time will also be better. As you say, it should be same technology as USB-sticks or memorycards, and it should be std to have that option when installing. We would like to use it, but we have some more standardization to fix first. /Tore ________________________________________________ Tore Agblad System programmer, Volvo IT certified IT Architect Volvo Information Technology IMO Mainframe Databases & zOpen Gothenburg E-mail: tore.agb...@volvo.com http://www.volvo.com/volvoit/global/en-gb/ -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of David Boyes Sent: den 12 februari 2013 15:54 To: LINUX-390@VM.MARIST.EDU Subject: Re: Who's using execute in place? > a few years ago we've introduced execute in place, which can be used to > save some memory by using z/VM DCSS segments. Since the size of main > memory for virtual servers has increased much faster than the size of binary > executables and libraries since, this technique has become less attractive. > Andrew Morton, the leading maintainer for the memory manager in Linux, > has raised the question if this is still needed. Tolerating that increase in bloat is another problem, but not what you're asking. 8-) That's kinda odd, since it shares a lot of concepts with the code that allows mapping filesystems to PROMs on Intel and ARM. I'm surprised the embedded Linux folks aren't screaming their heads off. > Who's using execute in place in their environment today? What are your > plans of future use? Can we discontinue the technology or shall we keep it > around? We don't use it due to the difficulty of creating and maintaining the DCSS from Linux over time. Since neither of the major distros on Z integrated it into the system management tooling, I suspect that it never got used much and no one would miss it. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
