On 12/01/2015 7:52 AM, Johnny Billquist wrote:
On 2015-12-01 16:49, John Robertson wrote:
On 11/28/2015 3:41 PM, Mouse wrote:
Love that term, "bounce buffer" (I wrote a whole package to support
them in a packet switch I did) - I'm officially adopting it, right
now! :-)
Hey - anything that anyo
On 2015-12-01 16:49, John Robertson wrote:
On 11/28/2015 3:41 PM, Mouse wrote:
Love that term, "bounce buffer" (I wrote a whole package to support
them in a packet switch I did) - I'm officially adopting it, right
now! :-)
Hey - anything that anyone writes is automatically copyrighted.
I reali
On 11/28/2015 3:41 PM, Mouse wrote:
Love that term, "bounce buffer" (I wrote a whole package to support
them in a packet switch I did) - I'm officially adopting it, right
now! :-)
Hey - anything that anyone writes is automatically copyrighted.
I realize you...may have been less than entirely se
unday, November 29, 2015 1:56 PM
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Re: "Bounce buffer" copyright [was Re: flash (or ide) storage for
unibus 11?]
There were a few systems (such as CP/M) that optimized (or attempted to)
interleave depending on use. So, "b
There were a few systems (such as CP/M) that optimized (or attempted to)
interleave depending on use. So, "boot" tracks were 1:1, "directory"
may have been 2:1 and user data 3:1.
Schemes varied widely. One or two even interleaved side-to-side in
addition to "skewing track-to-track. Obviousl
On Sun, Nov 29, 2015 at 1:19 PM, Fred Cisin wrote:
> it physically laid out the 10 sectors as 0 2 3 4 6 8 1 3 5 7 9 so that
>>> when reading sequentially, you had half a disk rotation to get your act
>>> together to read the next sector. This turned out to be only a small
>>> performance win, and
it physically laid out the 10 sectors as 0 2 3 4 6 8 1 3 5 7 9 so that
when reading sequentially, you had half a disk rotation to get your act
together to read the next sector. This turned out to be only a small
performance win, and was a pita for interoperability,
On Sun, 29 Nov 2015, Tapley,
On Nov 29, 2015, at 12:13 PM, Warner Losh wrote:
> A similar thing was implemented on the old DEC Rainbow 100 (though
> I'm sure others). To give the software a chance to do some minor things
> while processing, it physically laid out the 10 sectors as 0 2 3 4 6 8 1 3 5
> 7 9
> so that when read
> On Nov 29, 2015, at 1:13 PM, Warner Losh wrote:
>
> ...
> A similar thing was implemented on the old DEC Rainbow 100 (though
> I'm sure others). To give the software a chance to do some minor things
> while processing, it physically laid out the 10 sectors as 0 2 3 4 6 8 1 3
> 5 7 9
> so that
On Sat, Nov 28, 2015 at 7:19 PM, Jerome H. Fine
wrote:
> >Mouse wrote:
>
> Love that term, "bounce buffer" (I wrote a whole package to support
them in a packet switch I did) - I'm officially adopting it, right
now! :-)
Hey - anything that anyone writes is automatically copyrig
>Mouse wrote:
Love that term, "bounce buffer" (I wrote a whole package to support
them in a packet switch I did) - I'm officially adopting it, right
now! :-)
Hey - anything that anyone writes is automatically copyrighted.
I realize you...may have been less than entirely serious. But what yo
>> Love that term, "bounce buffer" (I wrote a whole package to support
>> them in a packet switch I did) - I'm officially adopting it, right
>> now! :-)
> Hey - anything that anyone writes is automatically copyrighted.
I realize you...may have been less than entirely serious. But what you
wrote
12 matches
Mail list logo
