From: Andi Kleen <andi@firstfloor.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Dave Chinner <david@fromorbit.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.35
Date: Tue, 3 Aug 2010 11:49:40 +0200 [thread overview]
Message-ID: <20100803094940.GC31096@basil.fritz.box> (raw)
In-Reply-To: <20100803092823.GA5324@amd>
On Tue, Aug 03, 2010 at 07:28:23PM +1000, Nick Piggin wrote:
> OK, vfs-scale-working branch now has commits to enable rcu-walk aware
> d_revalidate, permission, and check_acl in the filesystems, and
> implements a basic rcu-walk aware scheme for generic/posix acls and
Cool. I was just looking at that.
> I was under the impression that ACLs on directories are not that common,
> so maybe this is as far as we need to go for now anyway.
Yes it shouldn't be common normally. I think the common case for distros
is just a few ACLs in /dev. Of course you never know for
specific end user workloads.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-08-03 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim8FALeVG+NPLNLEQChu=dPD=GHSpnxmZHYgsNx@mail.gmail.com>
[not found] ` <20100802023322.GA19164@dastard>
[not found] ` <AANLkTint_s6h_EC7mDiPsyxr=C0GSrnrgJYkCCU7JEtN@mail.gmail.com>
[not found] ` <20100802055834.GB19164@dastard>
2010-08-02 7:55 ` Linux 2.6.35 Nick Piggin
2010-08-02 8:24 ` Christoph Hellwig
2010-08-02 8:46 ` KOSAKI Motohiro
2010-08-02 9:05 ` Christoph Hellwig
2010-08-02 10:07 ` Nick Piggin
2010-08-02 9:51 ` Nick Piggin
[not found] ` <87tyncds89.fsf@basil.nowhere.org>
2010-08-03 9:28 ` Nick Piggin
2010-08-03 9:49 ` Andi Kleen [this message]
2010-08-03 15:05 ` Henrique de Moraes Holschuh
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=20100803094940.GC31096@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).