From: Al Viro <viro@ZenIV.linux.org.uk>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, robert.richter@amd.com,
oprofile-list@lists.sf.net
Subject: Re: [patch] fs: shrink struct dentry
Date: Wed, 10 Dec 2008 06:53:21 +0000 [thread overview]
Message-ID: <20081210065320.GF28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20081210060048.GG8434@wotan.suse.de>
On Wed, Dec 10, 2008 at 07:00:48AM +0100, Nick Piggin wrote:
> OK, this is a new patch with updated changelog, and slightly tweaked
> change to dcookie subsystem (now we'll *never* do any more hash lookups
> on dcookie lookup, ignoring that "fast" dcookie lookups would effectively
> mean my previous version wouldn't have done any more lookups anyway).
I agree with reordering part, and I don't have too serious objections
against the rest, but...
Just what the bleeding fsck is that stuff doing to paths?
a) get two instances of fs mounted somewhere (or just have a binding, or
have two namespaces) and you'll get very funny results from dcookie -
it'll stick with vfsmount it had run into originally. Nevermind that
it might be not reachable for you. Or reachable for anyone, for that
matter, since the namespace it had been in might be long gone by now.
b) when is it evicted, anyway? We are stuck with a bunch of randomly
selected pinned dentries and vfsmounts...
c) may I have whatever dcookie_user inventor had been smoking?
struct dcookie_user {
struct list_head next;
};
with a cyclic list going through those and the only use of that list
is "is it empty?" checks. That's one hell of a way to implement a
counter, of course, but...
Anyway, I'll put it into VFS queue.
Al, currently one turd away from being through with audit queue for
the next merge window...
next prev parent reply other threads:[~2008-12-10 6:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 8:33 [patch][rfc] fs: shrink struct dentry Nick Piggin
2008-12-01 8:33 ` Nick Piggin
2008-12-01 11:09 ` Andi Kleen
2008-12-01 11:09 ` Andi Kleen
2008-12-01 11:26 ` Nick Piggin
2008-12-01 11:26 ` Nick Piggin
2008-12-01 17:51 ` John Levon
2008-12-01 17:51 ` John Levon
2008-12-01 18:04 ` Nick Piggin
2008-12-01 18:04 ` Nick Piggin
2008-12-01 19:38 ` John Levon
2008-12-01 19:38 ` John Levon
2008-12-02 7:06 ` Nick Piggin
2008-12-02 7:06 ` Nick Piggin
2008-12-02 13:04 ` John Levon
2008-12-02 13:04 ` John Levon
2008-12-02 13:49 ` Nick Piggin
2008-12-02 13:49 ` Nick Piggin
2008-12-02 14:49 ` John Levon
2008-12-02 14:49 ` John Levon
2008-12-02 15:11 ` Nick Piggin
2008-12-02 15:11 ` Nick Piggin
2008-12-10 6:00 ` [patch] " Nick Piggin
2008-12-10 6:53 ` Al Viro [this message]
2008-12-10 7:19 ` Nick Piggin
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=20081210065320.GF28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=oprofile-list@lists.sf.net \
--cc=robert.richter@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.