From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: RAMFS
Date: Fri, 2 Feb 2001 21:41:22 +0100 [thread overview]
Message-ID: <20010202214122.C753@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010202185709.A753@nightmaster.csn.tu-chemnitz.de> <Pine.Linu.4.10.10102022022300.623-100000@mikeg.weiden.de>
In-Reply-To: <Pine.Linu.4.10.10102022022300.623-100000@mikeg.weiden.de>; from mikeg@wen-online.de on Fri, Feb 02, 2001 at 08:24:19PM +0100
On Fri, Feb 02, 2001 at 08:24:19PM +0100, Mike Galbraith wrote:
> On Fri, 2 Feb 2001, Ingo Oeser wrote:
> > No, so have to unlock it also, if you return -ENOSPC.
> >
> > So the correct fix seems to be:
[...]
> > This currently works for me (but using 2.4.0 + dwg-ramfs.patch + this patch)
>
> Have you stressed it? (I see leakiness)
I do reads and writes to it every 5 seconds and sometimes more (
mounted on /tmp, /var/run and the like ) and had an uptime of
about a week (I use it in an embedded-like system and we
sometimes change the system image).
There might be a dentry or inode leak, but that doesn't bite me,
because I only create the files I need once and extend or shrink
them.
But I couldn't stress it too much.
Where exactly do you see the leaks?
PS: For reference, I put the diff to 2.4.0 that I use to
http://www.tu-chemnitz.de/~ioe/dwg-ramfs.patch
The original patch has _not_ been done by me, but by
David Gibson, Linuxcare Australia.
PPS: It would be surprising anyway, if I used the right patch all
the time, while the wrong one was in acX. That's why I didn't
submit anything ;-)
Regards
Ingo Oeser
--
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< come and join the fun >>>>>>>>>>>>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-02 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 15:51 RAMFS Alan Cox
2001-02-02 17:57 ` RAMFS Ingo Oeser
2001-02-02 19:24 ` RAMFS Mike Galbraith
2001-02-02 20:41 ` Ingo Oeser [this message]
2001-02-02 21:03 ` RAMFS Mike Galbraith
2001-02-03 7:13 ` RAMFS Mike Galbraith
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=20010202214122.C753@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-fsdevel@vger.kernel.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®