From: Ulrich Drepper <drepper@gmail.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Jamie Lokier <jamie@shareable.org>, Jeff Garzik <jeff@garzik.org>,
Oleg Drokin <green@linuxhacker.ru>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Attempt at "stat light" implementation
Date: Tue, 7 Apr 2009 12:30:45 -0700 [thread overview]
Message-ID: <a36005b50904071230h4850b5e3q2ad72a8e8babe09a@mail.gmail.com> (raw)
In-Reply-To: <20090407182157.GW3204@webber.adilger.int>
On Tue, Apr 7, 2009 at 11:21 AM, Andreas Dilger <adilger@sun.com> wrote:
> There is one in OS/X called getattrlist, but it is quite complex and
> would require attribute handling wildly different than what the kernel
> and *nix applications are doing:
>
> http://www.manpagez.com/man/2/getattrlist/
I think this is overkill. There are two different tasks to do:
- speed up stat by providing a subset of the information
- provide a mechanism to get arbitrary attribute support and efficient
ways to get to it
Trying to force both of these tasks into one interface will partially
defeat the purpose of the first, creating a fast stat replacement. I
think these should be different interfaces (if the second type is
needed at all).
As for making the interface extendable. In all the years there hasn't
really been much need to extend the stat structure (ignoring extended
attributes). So, I'd not be worried about using a simple 32-bit
bitmask to select the fields to include in the fast stat.
next prev parent reply other threads:[~2009-04-07 19:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 6:23 Attempt at "stat light" implementation Oleg Drokin
2009-04-07 10:23 ` Andreas Dilger
2009-04-07 14:54 ` Oleg Drokin
2009-04-07 17:52 ` Christoph Hellwig
2009-04-07 15:22 ` jim owens
2009-04-07 15:38 ` Oleg Drokin
2009-04-07 16:20 ` jim owens
2009-04-07 17:32 ` Jamie Lokier
2009-04-07 17:38 ` Jeff Garzik
2009-04-07 17:56 ` Jamie Lokier
2009-04-07 18:21 ` Andreas Dilger
2009-04-07 19:30 ` Ulrich Drepper [this message]
2009-04-12 20:55 ` Jamie Lokier
2009-04-07 17:41 ` Oleg Drokin
2009-04-07 17:54 ` Jamie Lokier
2009-04-07 18:00 ` Oleg Drokin
2009-04-07 18:18 ` Andreas Dilger
2009-04-07 18:31 ` Nicholas Miell
2009-04-07 17:49 ` Christoph Hellwig
2009-04-07 17:56 ` Oleg Drokin
2009-04-07 18:28 ` Andreas Dilger
2009-04-07 18:50 ` Jamie Lokier
2009-04-07 19:48 ` Jeff Garzik
2009-04-07 19:47 ` Jeff Garzik
2009-04-07 20:18 ` Evgeniy Polyakov
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=a36005b50904071230h4850b5e3q2ad72a8e8babe09a@mail.gmail.com \
--to=drepper@gmail.com \
--cc=adilger@sun.com \
--cc=green@linuxhacker.ru \
--cc=jamie@shareable.org \
--cc=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).