We try to reduce the amount of virtual storage in a Linux machine as much as possible
because Linux was created to use as much storage (memory) as possible as a cache for
disk blocks. We don't want that to happen on System z because that's a waste of
storage. CMM helps by fooling Linux into thinking it actually has the storage, but
allowing VM to use it for other things when Linux isn't using it. When Linux needs it,
it will get it back. I don't know what or where you saw that CMM is related to TCP/IP,
it isn't.
עופר ברוך wrote:
Hi all,
I have been reading a lot about Linux storage management and I saw a couple
of recommendations for over committing storage in z/VM :
1. Give your Linux as little storage as possible and use a VDISK for
the first swap device.
2. Use CMM to manage Linux storage.
The first one looks very hard to manage and monitor.
The second I just heard about today… I read something about it using tcpip.
That just seems strange, should I relay on my TCPIP machine for storage
management?
I am using a VSWITCH for that reason exactly… I don’t want my Linux machines
to depend on the TCPIP machine.
Anyone here using CMM for over committing? It sounds great! is it working
great as well?
Thanks,
Offer Baruch.
----------------------------------------------------------------------
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
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009
----------------------------------------------------------------------
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
