From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joachim Eastwood <manabian@gmail.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs pile 2 (automount work)
Date: Sun, 16 Jan 2011 23:06:14 +0000 [thread overview]
Message-ID: <20110116230614.GE22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20110116214426.GD22723@ZenIV.linux.org.uk>
On Sun, Jan 16, 2011 at 09:44:26PM +0000, Al Viro wrote:
> Already fixed. Actually, taking it out of ifdef would work (the only
> place that actually cares about the value of that sucker is SMP side
> of mntput()), but we are obviously better off just not touching it on
> UP at all - why do pointless work and waste space?
>
> See the patch upthread. ->mnt_longterm is SMP-only optimization of
> mntput(); it's there only to free the common case of mntput() from
> cacheline bouncing and on UP it's needed at all.
PS: the patch does survive UP beating. Could you pull
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus ?
There's only one patch at the moment:
Al Viro (1):
mnt_longterm is there only on SMP
fs/namespace.c | 31 ++++++++++++++++++++++++-------
1 files changed, 24 insertions(+), 7 deletions(-)
prev parent reply other threads:[~2011-01-16 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 18:57 [git pull] vfs pile 2 (automount work) Al Viro
2011-01-16 21:15 ` Joachim Eastwood
2011-01-16 21:36 ` Al Viro
2011-01-16 22:05 ` Joachim Eastwood
2011-01-16 21:37 ` Linus Torvalds
2011-01-16 21:44 ` Al Viro
2011-01-16 21:57 ` Sedat Dilek
2011-01-16 21:57 ` Sedat Dilek
2011-01-16 23:06 ` Al Viro [this message]
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=20110116230614.GE22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=torvalds@linux-foundation.org \
/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.