I noticed on SuSE's SDB, it seems to be a part of submarine which was made available in May. Couldn't find any doc on it though.
Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Dave Jones Sent: Wednesday, July 28, 2004 13:17 To: [EMAIL PROTECTED] Subject: Re: [LINUX-390] Under what conditions will Linux start releasing Cache? Barton, where might one start to find information about this collaborative memory management in Linux? TIA. DJ Barton Robinson wrote: >Check out the collaborative memory management. You can tell >linux dynamically to not cache so much. It's available, but >not yet really implementable. > > > >>Date: Wed, 28 Jul 2004 09:39:23 -0500 >>From: Rich Smrcina <[EMAIL PROTECTED]> >> >>What is this machine used for? 110 MB of cache is pretty much a waste >>of storage. If the machine eats into all (or most) of that before it >>finally croaks, then you have a memory hog or leak somewhere. >> >>I've seen that happen with WebSphere and it turned out to be an >>application problem. >> >>The cache will slowly get released to a certain point, then paging will >>begin and the paging/cacheing dance will begin. When the page device >>fills and the cache is gone then your up the creek... >> >>On Wed, 2004-07-28 at 09:25, James Melin wrote: >> >> >>>I've got a linux guest that is pushing the wall, 17 megs free and dropping. >>>Swapping is going to be inevitable. The problem is that the memory usage >>>growth is slow, and that cache grows to 110 meg before we start to approach >>>the wall. Will SLES8 start to release or clean the cache before swapping >>>becomes rampant? >>> >>><vent_spleen> >>> >>>Since there seems to be no way to control the cache in SLES8, which really >>>sucks since, in our situation, it is caching unimportant things. None of >>>the application data is local. If there are any of the Linux Kernal >>>developers monitoring this list, add my voice to those that are telling you >>>that not being able to control cache behavior is a really frustrating when >>>working in a virtualized environment where you are trying to divide limited >>>resources amongst many guests. The Cache behaviour is the biggest >>>non-application pig that I can see. >>> >>>Just my 2 cents >>> >>></vent_spleen> >>> >>> > > > > > > > >"If you can't measure it, I'm Just NOT interested!"(tm) > >/************************************************************/ >Barton Robinson - CBW Internet: [EMAIL PROTECTED] >Velocity Software, Inc Mailing Address: > 196-D Castro Street P.O. Box 390640 > Mountain View, CA 94041 Mountain View, CA 94039-0640 > >VM Performance Hotline: 650-964-8867 >Fax: 650-964-9012 Web Page: WWW.VELOCITY-SOFTWARE.COM >/************************************************************/ > >---------------------------------------------------------------------- >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 > > > -- Dave Jones Sine Nomine Associates Houston, TX 281.578.7544 ---------------------------------------------------------------------- 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
