From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@coraid.com>
Date: Thu, 23 Apr 2009 07:51:13 -0400
To: 9fans@9fans.net
Message-ID: <235a74371fc051b8a56e9bef4ade7ea9@coraid.com>
In-Reply-To: <20090423053650.GR14047@masters6.cs.jhu.edu>
References: <7c22175ab60f8a5ae2cf894d462b29e5@9netics.com>
	<191db84e421c825f67aa18631ffc0884@coraid.com>
	<140e7ec30904222207r36c41d7dgbae9c320e79cfc29@mail.gmail.com>
	<20090423053650.GR14047@masters6.cs.jhu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Plan9 - the next 20 years
Topicbox-Message-UUID: efd842f4-ead4-11e9-9d60-3106f5b1d025

> Not to beat a (potentially) dead horse (even further) to death, but if we
> had some way of knowing that files were actually data (i.e. not ctl files;
> cf. QTDECENT) we could do more prefetching in a proxy -- e.g. cfs could be
> modified to do read entire files into its cache (presumably it would have to
> Tstat afterwards to ensure that it's got a stable snapshot of the file).
> Adding cache journal callbacks would further allow us to avoid the RTT of
> Tstat on open and would bring us a bit closer to a fully coherent store.
> Achieving actual coherency could be an interesting future direction (IMHO).

you're right.  i think cfs is becoming a pretty dead horse.  if you're
running at a significant rtt from your main system, and you don't
have one of your own, the simple solution is to install 9vx.  that
way your system is local and only the shared files get shared.

does cfs even work with import?  if it doesn't then using it implies
that all your data are free for public viewing on whatever network
you're using, since direct fs connections aren't encrypted.

regarding the QTDECENT, i think russ is still on point
http://9fans.net/archive/2007/10/562

- erik