Just a perhaps crazy idea. - Add new page volumes - drain all old page vlumes to stop adding new data there - for each Linux, one at a time change the reserved memory to the same as memsize (for this to work, z/VM now must restore all paged memory into real memory) - wait until this is done (hehe, have no clue here about the time or how to check it out, sorry) - remove that reserved memory (or is it dedicated?) - and all new paging will we on the new page volumes
Any chance this can work anyone ? :) Cordialement / Vriendelijke Groeten / Best Regards / Med Vänliga Hälsningar Tore Agblad ________________________________________________ Tore Agblad System programmer, Volvo IT certified IT Architect Volvo Information Technology Infrastructure Mainframe Design & Development, Linux servers Dept 4352 DA1S SE-405 08, Gothenburg Sweden Telephone: +46-31-3233569 E-mail: [email protected] http://www.volvo.com/volvoit/global/en-gb/ ________________________________________ From: Linux on 390 Port [[email protected]] On Behalf Of Mauro Souza [[email protected]] Sent: Tuesday, June 21, 2011 15:20 To: [email protected] Subject: Re: z/VM page space Just a idea, but what if we put the "back link" on the DASD page (I don't know much about the structure of the page, but I think there's a header there somewhere), not on central memory? We would only have to read the back link on the page header on DASD and we would know where the page is, migrate it and release the disk. Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Tue, Jun 21, 2011 at 2:09 AM, Alan Altmark <[email protected]>wrote: > On Monday, 06/20/2011 at 08:56 EDT, Clovis Pereira <[email protected]> > wrote: > > At least, we seeded the idea. > > The requirement to provide this function has been on the books and on VM > Development's collective conscience since 1990. :-( *Everyone* runs > into a dasd migration/reclamation project at some point that forces an > IPL. (IBMers, too, btw.) > > The good news is that this conversation has re-focused the Eye of Sauron > once again upon the requirement. (In this case, that's a Good Thing.) > > If anyone would like to express their support for this requirement, > contact the Support Center or your rep/BP and ask to have your name added > to the Interested Parties list of requirement MR00025368, which covers > both spooling and paging. > > Alan Altmark > > Senior Managing z/VM and Linux on System z Consultant > IBM System Lab Services and Training > ibm.com/systems/services/labservices > office: 607.429.3323 > mobile; 607.321.7556 > [email protected] > IBM Endicott > > ---------------------------------------------------------------------- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
