From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Are there disadvantages to walk?
Date: Mon, 1 Apr 2019 19:49:35 +0000 [thread overview]
Message-ID: <1859706859.14691305.1554148175942@mail.yahoo.com> (raw)
In-Reply-To: <1859706859.14691305.1554148175942.ref@mail.yahoo.com>
On Mon, 4/1/19, Ethan Gardener <eekee57@fastmail.fm> wrote:
> I remember hearing of some disadvantage to
> walking directories, but can't remember what it was.
> Could someone remind me, please? Perhaps there was
> more than one, of course. Perhaps a performance trick
> couldn't be employed?
The only complaint I've had about walk was the expectation
in the protocol that servers produce the list of Qids all
the way down. That got in the way when experimenting
with a server that used a hash table of full path names
to speed the walk process.
BLS
next parent reply other threads:[~2019-04-01 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1859706859.14691305.1554148175942.ref@mail.yahoo.com>
2019-04-01 19:49 ` Brian L. Stuart [this message]
2019-04-02 14:46 ` Ethan Gardener
2019-04-01 10:27 Ethan Gardener
2019-04-01 16:26 ` hiro
2019-04-01 16:32 ` Ethan Gardener
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=1859706859.14691305.1554148175942@mail.yahoo.com \
--to=blstuart@bellsouth.net \
--cc=9fans@9fans.net \
/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).