From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 25 May 2001 06:33:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 25 May 2001 06:33:46 -0400 Received: from server1.cosmoslink.net ([208.179.167.101]:42030 "EHLO server1.cosmoslink.net") by vger.kernel.org with ESMTP id ; Fri, 25 May 2001 06:33:31 -0400 Message-ID: <014901c0e506$20be97e0$53a6b3d0@Toshiba> From: "Jaswinder Singh" To: "Mike Galbraith" Cc: "Alan Cox" , , "Jaswinder Singh" In-Reply-To: Subject: Re: Linux 2.4.4-ac17 Date: Fri, 25 May 2001 03:33:23 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Dear Mike , Are you using harddisk ? Jaswinder. ----- Original Message ----- From: "Mike Galbraith" To: "Jaswinder Singh" Cc: "Alan Cox" ; Sent: Friday, May 25, 2001 2:06 AM Subject: Re: Linux 2.4.4-ac17 > On Thu, 24 May 2001, Jaswinder Singh wrote: > > > Dear Mike , > > > > > > > > This one I tested with memleak. It wasn't a leak, it was dcache > > > growth. Under vm stress, it shrank down fine. > > > > > > > It will depends upon lot of thing :- > > 1.What is your size of ramfs , > unlimited. > > 2. Are you using any harddisk , > (?? ramfs) I think I misunderstand. > > 3. How many many files are you creating , > lots of different names. (like you were) > > 4. How frequently you are making files . > as fast as a C proglet could create/maybe(random)access/destroy them. > > 5. What are the size of your files ? > varying from empty to small. > > > > In my case , my ramfs is of 14 MB , using no hard-disk , i am continously > > making and deleting files of 4 K size , my Machine hangs within 5 minutes , > > by saying no memory left. > > I can write random 4k files as fast and long as I like (with swap off) > and if I flush out the rather large dcache... > > procs memory swap io system cpu > r b w swpd free buff cache si so bi bo in cs us sy id > 2 0 1 0 17600 104 4456 0 0 197 4 118 41 6 83 11 > 1 0 0 0 14888 124 4476 0 0 31 0 123 37 13 87 0 > 1 0 0 0 12252 124 4476 0 0 0 0 103 9 11 89 0 > 1 0 0 0 9632 124 4476 0 0 0 0 105 7 17 83 0 > 1 0 0 0 7032 124 4480 0 0 0 0 103 10 11 89 0 > 1 0 0 0 4460 124 4476 0 0 0 0 101 10 12 88 0 > 1 0 1 0 20272 128 4480 0 0 1 2 116 16 23 77 0 > 1 0 0 0 17860 128 4480 0 0 0 15 115 10 17 83 0 > 1 0 0 0 15196 128 4476 0 0 0 0 110 7 15 85 0 > dentry_cache 747962 747990 128 24933 24933 1 > dentry_cache 769651 769680 128 25656 25656 1 > dentry_cache 792664 792690 128 26423 26423 1 > dentry_cache 814779 814800 128 27160 27160 1 > dentry_cache 835972 835980 128 27866 27866 1 > dentry_cache 715148 715170 128 23839 23839 1 > > ...afterward, I don't see leakage. Only a short test this time, but > long enough to eat all of my ram many times over if it leaked as fast > as your description indicates. I can't reproduce it. (2.4.4 btw) > > > Please tell me about your system and what you are doing on it ? > > Generic 128mb PIII/500. What I was doing on it was beating up ramfs > looking for the leak you reported :) > > -Mike > >