On Friday 08 July 2011 20:12:08 Gabriel M. Beddingfield wrote:
What would happen? The ringbuffer in jack is explicitely only for one-reade=
one-writer. So in this optimization, the only participant using the read_pt=
to do something possibly bad, is the reading participant which is currently=
executing this code.
The writing participant can access that read_ptr for example to check the=20
available space. But as the docs state (afair), the available sizes for=20
read/write are not strict functions, the only thing that counts is if you h=
space for reading/writing. And that is fulfilled if read_ptr!=3Dwrite_ptr...
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-----