From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7150078ec6d4a983e1bc125e877704f7@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Rstat needs three size fields?
From: Geoff Collyer <geoff@collyer.net>
In-Reply-To: <3F05D809.7030707@null.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Date: Mon,  7 Jul 2003 02:03:08 -0700
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: eaf1bb02-eacb-11e9-9e20-41e7f4b1d025

Actually 2=E2=81=B3=E2=81=B2 is a fairly big number in the context of 9P =
read &
write byte counts (which is what Rob was talking about).  I don't
think I've ever read or written 4,294,967,296 bytes (or even close to
that many) in a single operation.

As for efficient integer encodings, at least for this purpose, if we
restricted I/O transfer lengths to powers of 2, we could just supply
the exponent in 9P (e.g., 16 in a length field in 9P would represent
2=E2=81=B1=E2=81=B6=3D65,536). =E2=98=BA  We could get away with a single=
 byte for length fields,
even a signed byte.