On Friday 08 July 2011 22:41:54 Paul Davis wrote:
Empty for reading. Lots of space for writing.
Its much more interesting to see what happens when the indezes cross the 2^=
or 2^64 mark, then the write-index will be smaller then the read-index unti=
the read-index catches up. But as far as I see currently, this wouldn't be =
problem either. The writer only has to stop writing when its at read_ptr - =
Maybe I don't understand it all, but with fons approach I think it only wor=
when the buffer-sizes are 2^n. When you have a buffer of say 5 elements, do=
the modulo at the element-access and not at the read/write-head-movement, t=
will jump every now and then, right?
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
-----END PGP SIGNATURE-----