mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: "Mike Galbraith" <mikeg@wen-online.de>,
	"Alan Cox" <laughing@shared-source.org>,
	<linux-kernel@vger.kernel.org>
Cc: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
Subject: Re: Linux 2.4.4-ac17
Date: Thu, 24 May 2001 22:42:59 -0700	[thread overview]
Message-ID: <001d01c0e4dd$8f9cd7e0$53a6b3d0@Toshiba> (raw)
In-Reply-To: <Pine.LNX.4.33.0105250703550.568-100000@mikeg.weiden.de>

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 ,
2. Are you using any harddisk ,
3. How many many files are you creating ,
4. How frequently you are making files .
5. What are the size of your files ?

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.

Please tell me about your system and what you are doing on it ?

Thanks ,

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.



> -Mike
>


       reply	other threads:[~2001-05-25  5:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0105250703550.568-100000@mikeg.weiden.de>
2001-05-25  5:42 ` Jaswinder Singh [this message]
2001-05-25  9:06   ` Mike Galbraith
2001-05-25 10:33     ` Jaswinder Singh
2001-05-25 13:01       ` Mike Galbraith
2001-05-26 19:06         ` Jaswinder Singh
2001-05-27  6:21           ` Mike Galbraith
2001-05-27  7:13             ` Jaswinder Singh
2001-05-27  8:25               ` Mike Galbraith
2001-05-27 17:32                 ` Alan Cox
2001-05-26 20:11 Jaswinder Singh
  -- strict thread matches above, loose matches on Subject: below --
2001-05-24 23:37 Alan Cox
2001-05-25  1:26 ` Jaswinder Singh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001d01c0e4dd$8f9cd7e0$53a6b3d0@Toshiba' \
    --to=jaswinder.singh@3disystems.com \
    --cc=laughing@shared-source.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikeg@wen-online.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®