From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "H . J . Lu" <hjl@valinux.com>,
NFS maillist <nfs@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] Updated patch for the [2.4.x] NFS 'missing directory entry a.k.a. IRIX server' problem...
Date: Tue, 27 Feb 2001 20:12:02 +0100 [thread overview]
Message-ID: <20010227201202.B11060@pcep-jamie.cern.ch> (raw)
In-Reply-To: <14997.9938.106305.635202@charged.uio.no> <20010226152826.A20653@valinux.com> <15003.20448.999929.948597@charged.uio.no> <20010226230647.A14094@valinux.com> <15003.23067.683600.738764@charged.uio.no>
In-Reply-To: <15003.23067.683600.738764@charged.uio.no>; from trond.myklebust@fys.uio.no on Tue, Feb 27, 2001 at 08:41:15AM +0100
Trond Myklebust wrote:
> >>>>> " " == H J Lu <hjl@valinux.com> writes:
>
> > I much prefer to have a new getdents system call which will
> > also return d_type so that the 32 bit function in glibc can use
> > this new getdents instead of getdents64.
>
> That could also be done, however it seems odd to be adding a new
> 32-bit interface after the point when we're supposed to all have moved
> to 64 bits.
Indeed, getdents64 -> 32 conversion is hardly performance critical
anyway.
> BTW: does anybody anywhere actually use d_type? Certainly the standard
> utilities such as 'find' or 'ls' don't seem to have been adapted
> yet: I hacked up a version of NFSv3 that actually filled d_type
> (by using readdirplus rather than readdir) but I've yet to find
> any 'off the shelf' software, that uses the extra information.
Look for `treescan' via Google. It uses a number of heuristics to
optimise a recursive directory search, and one of those is d_type if
available. Though it dates back to a time before getdents64 (I hacked
getdents to return d_type).
d_type is quite effective for `find' type scans. I really ought to
release an updated treescan -- the intent was always to replace the
backend of `find' but I got caught up trying to optimise the order of
open/readdir/close sequences and then on to other things.
-- Jamie
next prev parent reply other threads:[~2001-02-27 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 14:48 Updated patch for the [2.4.x] NFS 'missing directory entry a.k.a. IRIX server' problem Trond Myklebust
2001-02-26 23:28 ` [NFS] " H . J . Lu
2001-02-27 6:57 ` Trond Myklebust
2001-02-27 7:06 ` H . J . Lu
2001-02-27 7:41 ` Trond Myklebust
2001-02-27 19:12 ` Jamie Lokier [this message]
2001-02-27 23:04 ` H . J . Lu
2001-02-27 23:24 ` H . J . Lu
2001-02-28 11:19 ` Trond Myklebust
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=20010227201202.B11060@pcep-jamie.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=hjl@valinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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).