Re: 2Q's: concurrency; pf on O2

New Message Reply Date view Thread view Subject view Author view

From: Allan Schaffer (allan++at++sgi.com)
Date: 11/16/2000 09:53:58


On Nov 15, 3:41pm, Dirk Baerts wrote:
> Thanks for your extensive answer.
> Unfortunately, one chef whipping the eggs isn't an option right now.

In that case, it would be best to force the 'chefs' to take turns.
In the DRAW callback for each [independent] program, set up a
synchronization barrier between the two using a semaphore or other
sort of mutual lock. You want each process to treat the entire
channel DRAW callback as a critical region.

This might seem counterintuitive since it would serialize rendering
from each program. But the net result will prevent the system from
being overwhelmed by graphics context switches, which _should_ be
a major improvement.

> And indeed, the O2 is short of system memory : 64 M. We'll do
> something about that.

Allan

-- 
Allan Schaffer                                            allan++at++sgi.com
Silicon Graphics                           http://reality.sgi.com/allan


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Nov 16 2000 - 09:54:01 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.