There is some problem in my computer's clock . please do not mind .
I am sorry for inconvenience.
Jaswinder.
----- Original Message -----
From: "Jaswinder Singh" <[EMAIL PROTECTED]>
To: "Linus Torvalds" <[EMAIL PROTECTED]>; "Jamey Hicks"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: "Stephen L Johnson" <[EMAIL PROTECTED]>; "Jaswinder Singh"
<[EMAIL PROTECTED]>
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" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; "Linus Torvalds"
> <[EMAIL PROTECTED]>; "Jamey Hicks" <[EMAIL PROTECTED]>
> Cc: "Stephen L Johnson" <[EMAIL PROTECTED]>; "Jaswinder Singh"
> <[EMAIL PROTECTED]>
> 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.
> >
> >
> >
> >
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
