public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: "Jaswinder Singh" <jaswinder.singh@3disystems.com>,
	"Linus Torvalds" <torvalds@transmeta.com>,
	"Jamey Hicks" <jamey@crl.dec.com>, <linux-kernel@vger.kernel.org>
Cc: "Stephen L Johnson" <sjohnson@monsters.org>
Subject: Re: Memory leak in the ramfs file system
Date: Thu, 29 Mar 2001 17:39:19 -0800	[thread overview]
Message-ID: <02eb01c0b8ba$3d785ce0$bba6b3d0@Toshiba> (raw)
In-Reply-To: <024801c0ab59$76350880$bba6b3d0@Toshiba>

There is some problem in my computer's clock . please do not mind .

I am sorry for inconvenience.

Jaswinder.

----- Original Message -----
From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: "Linus Torvalds" <torvalds@transmeta.com>; "Jamey Hicks"
<jamey@crl.dec.com>; <linux-kernel@vger.kernel.org>
Cc: "Stephen L Johnson" <sjohnson@monsters.org>; "Jaswinder Singh"
<jaswinder.singh@3disystems.com>
Sent: Monday, March 12, 2001 5:03 PM
Subject: Fw: Memory leak in the ramfs file system


> I am sorry, i am sending this mail again because earlier my Computer's
time
> was not set properly.
>
> Jaswinder
>
> ----- Original Message -----
> From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
> To: <linux-kernel@vger.kernel.org>; "Linus Torvalds"
> <torvalds@transmeta.com>; "Jamey Hicks" <jamey@crl.dec.com>
> Cc: "Stephen L Johnson" <sjohnson@monsters.org>; "Jaswinder Singh"
> <jaswinder.singh@3disystems.com>
> Sent: Monday, June 12, 2000 12:50 PM
> Subject: Re: Memory leak in the ramfs file system
>
>
> > Dear Linus,
> >
> >
> > > What does /proc/slabinfo say? The most likely leak is a dentry leak or
> > > an inode leak, and both of those should be fairly easy to see in the
> > > slab info (dentry_cache and inode_cache respectively).
> > >
> >
> > I am attaching details before and during  my application .
> >
> > Mainly changes are in dentry_cache and inode_cache , but i am attaching
> > whole /proc/slabinfo for your reference.
> >
> >
> > > Obviously, it could be a data page leak too, but such a leak should be
> > > easy to see by creating a few big files and deleting them..
> > >
> > > Linus
> >
> > I am also facing one more problem with ramfs.
> >
> > du and df shows 0 , so i am also attaching its output.
> >
> > Thanks for your help,
> >
> > Best Regards,
> >
> > Jaswinder.
> > --
> > These are my opinions not 3Di.
> >
> >
> >
> >
>


  reply	other threads:[~2001-03-30  1:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-13  1:03 Fw: Memory leak in the ramfs file system Jaswinder Singh
2001-03-30  1:39 ` Jaswinder Singh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-29 22:06 Stephen L Johnson
2001-03-29 23:48 ` Linus Torvalds
2000-06-12 20:50   ` Jaswinder Singh
2001-03-30  9:43     ` Jeff Garzik
2001-03-30  3:10 Amit D Chaudhary
2001-03-30  9:45 ` Jeff Garzik
2001-03-30 17:29   ` Amit D Chaudhary
2001-03-30 19:43 Amit D Chaudhary

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='02eb01c0b8ba$3d785ce0$bba6b3d0@Toshiba' \
    --to=jaswinder.singh@3disystems.com \
    --cc=jamey@crl.dec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sjohnson@monsters.org \
    --cc=torvalds@transmeta.com \
    /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