Cooperative Memory Management and Collaborative Memory Management are different things.
Cooperative Memory Management does indeed need the CMM module loaded in Linux, whereas Collaborative Memory Management does not. Q MEMASSIST is telling you the status of Collaborative Memory Management. "ACTIVE" in the response tells you that the Linux guest has issued the ESSA instruction, which is how Collaboratie Memory Management is implemented. "SIMULATED" in the response tells you that the assist is not installed on the hardware and that it is being simulated by CP. Brian Nielsen On Tue, 11 Dec 2007 17:31:21 +0930, Fred Schmidt <[EMAIL PROTECTED]> wrote: >Hi, > >I'm having a play with VMRM Cooperative Memory Management, now I have z/ VM >5.3 and SLES 10.1 installed. However, I'm not sure that it is working >correctly. > >From z/VM, I see.... > > q memassist for user vmlxtst5 >ALL USERS SET - ON > >USER SETTING STATUS >VMLXTST5 ON ACTIVE,SIMULATED > >... with the "SIMULATED" meaning that assist is not installed, but is >being simulated by CP, according to the HELP info. I take that to mean >that Linux is not set up correctly. Or am I barking up the wrong tree >here? > > >From Linux, I have specified the following in /etc/zipl.conf and run zip l >-V .... > > parameters = "dasd=150-15F root=/dev/dasda1 cmm.sender=VMRMS VM >TERM=dumb" > >I have also issued... > >modprobe cmm sender=VMRMSVM > >... and lsmod confirms that cmm is loaded. > >cat /proc/sys/vm/cmm_pages shows values that match those recorded in >VMRMSVM's log file for the SMSG entries for the same time period, so it >seems that z/VM is telling Linux to reduce memory. > >But is Linux taking any notice? How do I confirm that it is? I don't se e >any corresponding reduction in memory usage using top in Linux, or PERFK IT >in z/VM. > >Regards, >Fred Schmidt >Department of Corporate and Information Services (DCIS) >Data Centre Services (DCS) >Northern Territory Government, Australia
