From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 18 Sep 2008 12:36:31 +0200 From: Christian Kellermann To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20080918103631.GG29361@hermes.my.domain> References: <140e7ec30809180257y34722805y287fd9838bd76f35@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FoLtEtfbNGMjfgrs" Content-Disposition: inline In-Reply-To: <140e7ec30809180257y34722805y287fd9838bd76f35@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: [9fans] 9p over high-latency Topicbox-Message-UUID: 11bf9d14-ead4-11e9-9d60-3106f5b1d025 --FoLtEtfbNGMjfgrs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * sqweek [080918 12:02]: > On Fri, Sep 12, 2008 at 7:47 PM, erik quanstrom w= rote: > > as an aside: i don't think 9p itself limits plan 9 performance > > over high-latency links. the limitations have more to do with > > the number of outstanding messages, which is 1 in the mnt > > driver. >=20 > Hm, but what's the alternative here? Readahead seems somewhat > attractive, if difficult (I worry about blocking reads and timing > sensitive file systems). But there's one problem I can't resolve - how > do you know what offset to Tread without consulting the previous > Rread's count? > Actually, I understand there has been discussion about grouping tags > to allow for things like Twalk/Topen batching without waiting for > Rwalk (which sounds like a great idea), maybe that would work here > also... There are some interesting approaches which have been discussed at the last= iwp9, including op from nemo's team. http://plan9.bell-labs.com/iwp9/papers/10.op.esoriano.pdf Maybe that is worth looking at for your issue? Kind regards, Christian --=20 You may use my gpg key for replies: pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen) --FoLtEtfbNGMjfgrs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (OpenBSD) iEYEARECAAYFAkjSLy8ACgkQXYob3Uf3l4gwhACeNRHc0kIrXUxHL2cGGF9+BpDJ 7XUAnjqphWj6QpGKd8sJ3Qm15i8uFJiP =S6aT -----END PGP SIGNATURE----- --FoLtEtfbNGMjfgrs--