[Chromium-dev] Binaryswap issues

[Michael H. <mho...@gr...>]

I'm almost done with the bounding box code, but I'm still a little stuck
on what to do about thread and mutli-context support.

The composite network is currently defined on a node by node basis. 
What is a good way to be able to define the network on a thread by
thread basis and/or a window by window basis?  The composite network
need to remain relatively static, ie we must have a power of two
network.  What if a new thread gets spawned that makes it 2^n+1?  

I'm not sure multi-context multi-thread really makes sense for
compositing anyway.  The problem here is bandwidth.  If we have one node
sending even more frame information that we currently do, readback and
transmit will become even more of a bottleneck.  In the case of a big
SGI or running on a single system, binaryswap will be no faster than ust
using readback.  Binary swap was designed to reduce bandwidth
requirements for many to one, the same benefits do not apply if you are
on the same node or are running one to one.

My preference would be to error out if more that one context/thread is
created.  Thoughts?  

-Mike