From: Nathan Scott <nathans@sgi.com>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Christoph Hellwig <hch@infradead.org>,
torvalds@transmeta.com, Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] Add POSIX Access Control Lists to ext2/3
Date: Fri, 18 Oct 2002 07:55:55 +1000 [thread overview]
Message-ID: <20021018075555.B307856@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <200210171204.08922.agruen@suse.de>; from agruen@suse.de on Thu, Oct 17, 2002 at 12:04:08PM +0200
On Thu, Oct 17, 2002 at 12:04:08PM +0200, Andreas Gruenbacher wrote:
> Hello Nathan,
hi there,
> On Thursday 17 October 2002 00:48, Nathan Scott wrote:
> > They are an optimisization for the one special case (posix acls),
> > and manage to pollute the VFS for that one special case ...
> ...
> As soon as any filesystem independent part of the kernel needs an interface
> more efficient that pass-by-value we will again have exactly the same
> problem.
My point is simply that a proposal to extend the VFS in this way needs
to be accompanied by a compelling argument showing the performance bump
that its providing.
> Going to disk and fetching EAs only causes disk accesses once; afterwards the
> block is cached.
Good - this is true for both XFS and ext2/3 then. So, we are talking about
using ref counting vs. copying for any in-kernel users of attrs, and you're
saying there is some significant overheads with copying and I'm saying show
me what kind of overheads we're talking about, please.
cheers.
--
Nathan
prev parent reply other threads:[~2002-10-17 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 22:20 tytso
2002-10-16 13:11 ` Christoph Hellwig
2002-10-16 15:50 ` Theodore Ts'o
2002-10-16 16:09 ` Andreas Gruenbacher
2002-10-16 22:48 ` Nathan Scott
2002-10-17 10:04 ` Andreas Gruenbacher
2002-10-17 21:55 ` Nathan Scott [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=20021018075555.B307856@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=agruen@suse.de \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=tytso@mit.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®