From: Mark Mielke <mark@mark.mielke.cc>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: negative dentries wasting ram
Date: Fri, 24 May 2002 14:36:25 -0400 [thread overview]
Message-ID: <20020524143625.A25016@mark.mielke.cc> (raw)
In-Reply-To: <Pine.LNX.4.44.0205240927580.11495-100000@home.transmeta.com> <Pine.GSO.4.21.0205241259230.9792-100000@weyl.math.psu.edu>
On Fri, May 24, 2002 at 01:00:14PM -0400, Alexander Viro wrote:
> > The only think we save is a dentry kfree/kmalloc in this case, nbot a FS
> > downcall. And I think Andrea is right that it can waste memory for the
> > likely much more common case where the file just stays removed.
> ???
> It's lookup + unlink + lookup + create vs. lookup + unlink + create.
I would rather use kernel memory for far more useful things, such as
more room for actual dentries/inodes, or negative dentries found from
failed lookup() calls (i.e. proven useful).
The overhead of unlink()/create() probably swamps the rather minimal
gain from a saved lookup() in this not very common situation.
Just the opinion of somebody that doesn't matter... :-)
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-05-24 18:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 7:16 Andrea Arcangeli
2002-05-24 8:10 ` Andreas Dilger
2002-05-24 15:36 ` Andrea Arcangeli
2002-05-24 16:12 ` Alexander Viro
2002-05-24 16:21 ` Andrea Arcangeli
2002-05-24 16:24 ` Alexander Viro
2002-05-24 14:43 ` Linus Torvalds
2002-05-24 14:51 ` David S. Miller
2002-05-24 14:53 ` Jakub Jelinek
2002-05-24 20:44 ` David Schwartz
2002-05-25 17:33 ` Florian Weimer
2002-05-24 15:54 ` Andrea Arcangeli
2002-05-24 16:22 ` Alexander Viro
2002-05-24 16:29 ` Linus Torvalds
2002-05-24 16:39 ` Andrea Arcangeli
2002-05-24 17:04 ` Alexander Viro
2002-05-24 17:06 ` Alexander Viro
2002-05-24 17:55 ` Andrea Arcangeli
2002-05-24 18:00 ` Alexander Viro
2002-05-24 18:58 ` Andrea Arcangeli
2002-05-24 19:04 ` Alexander Viro
2002-05-24 19:43 ` Andrea Arcangeli
2002-05-24 19:55 ` Alexander Viro
2002-05-24 20:36 ` Andrea Arcangeli
2002-05-24 22:14 ` Jan Harkes
2002-05-24 22:31 ` Andrea Arcangeli
2002-05-26 8:06 ` Eric W. Biederman
2002-05-24 17:00 ` Alexander Viro
2002-05-24 18:36 ` Mark Mielke [this message]
2002-05-31 8:34 ` Oliver Neukum
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=20020524143625.A25016@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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®