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>
Cc: "Alan Cox" <laughing@shared-source.org>,
	<linux-kernel@vger.kernel.org>,
	"Jaswinder Singh" <jaswinder.singh@3disystems.com>
Subject: Re: Linux 2.4.4-ac17
Date: Sun, 27 May 2001 00:13:22 -0700	[thread overview]
Message-ID: <001101c0e67c$844017e0$50a6b3d0@Toshiba> (raw)
In-Reply-To: <Pine.LNX.4.33.0105270656480.603-100000@mikeg.weiden.de>

Dear Mike,

"Mike Galbraith" <mikeg@wen-online.de> wrote :

>
> Exactly.  Nothing but ram and it's mostly unfreeable.  That makes
> life pretty tough for the vm.
>

This is not a good concept at all , why linux is wasting precious RAM
unnecassarily, if not required .

Then what will happen for Embedded system (like in my case), which do not
have any Hard disk , only things they have Flash or Ram.

> Does it hang if you are doing other things than creating/destroying
> tiny files (with unique names) as rapidly as possible?.. ie did you
> start doing that to troubleshoot because it was hanging over a long
> period of time?
>

If i create and delete files with same name , inode_cache & dentry_cache
increases only one time , there is no problem .
If i create and delete files with different name , inode_cache &
dentry_cache increases continously and will eat my whole RAM and crash
system.

And if i create and delete my file after long lapse , inode_cache &
dentry_cache are restore after some time , their is no problem .
But if i create and delete files very frequently , inode_cache &
dentry_cache get no time for restore and eat my whole RAM and crash system.

If i donot create and delete files files frequently with different name ,
their is no problem at all.

> You snipped my suggestion.. did you try it?  If not, please do.  In
> fact, go a bit further.  Make unconditional calls to kmem_cache_reap()
> and shrink_icache_memory() as well.. prior to calling page_launder().
> It's a long shot, but it might help.  If it does help, that will
> tell developers what they need to know.  It costs you five minutes.
>
> Another option is to build 2.4.5-pre6 and add the patch Rik posted.
> If my thinker is working right, that _will_ help (if not cure).
>
> Another option which virtually guarantees successful identification
> of the problem (but costs more than five minutes) is for you to grab
> a copy of IKD from your favorite kernel mirror and give memleak a try
> locally.  It can be found in /pub/linux/kernel/people/andrea/ikd. If
> you choose this option and have any trouble, drop me a note offline.
>

Thank you very much for your suggestions , i was getting this problem in my
ARM target machine and right now i am working on SH target machines , and i
am quite busy with my SH target machines now , i have to do lot of setups to
change my target machines , i am sorry right now i am not in position to
test your suggestions , but as soon as my SH target machine work is over , i
will test all your suggestions and options.

BTW, i am getting Ramdisk intialization problem in SH target machine.

Thank you,

Best Regards,

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





  reply	other threads:[~2001-05-27  7:13 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
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 [this message]
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='001101c0e67c$844017e0$50a6b3d0@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®