From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <5d375e920904200758m1a1a96den579673e107b57b19@mail.gmail.com> <3e1162e60904201118u18e8846bkbfec62e561a15a91@mail.gmail.com> <3e1162e60904201155l2b29c0b7ge248c36f82f7324@mail.gmail.com> <3e1162e60904201317v4d50be85x4597a1a6a3123959@mail.gmail.com> <3e1162e60904201418g54ba56f4pbf8fc31bf95a9d81@mail.gmail.com> <14ec7b180904201428v1fc0845ayb042b6aa628e17cc@mail.gmail.com> Date: Tue, 21 Apr 2009 13:00:30 +0100 Message-ID: From: roger peppe To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan9 - the next 20 years Topicbox-Message-UUID: ecb4fea0-ead4-11e9-9d60-3106f5b1d025 i wrote: > the currently rather complex definition of Twalk could > be replaced by clone and walk1 instead, as > in the original 9p: {Tclone, Twalk, Twalk, ...} i've just realised that the replacement would be somewhat less efficient as the current Twalk, as the cloned fid would still have to be clunked on a failed walk. this is a common case when using paths that traverse a mount point, but perhaps it's less common that directories are mounted on external filesystems, and hence not such an important issue (he says, rationalising hastily :-) )