[GRASS5] Driver Update

Justin Hickey jhickey at hpcc.nectec.or.th
Mon Apr 23 04:08:20 EDT 2001


Hi Glynn

Glynn Clements wrote:
> It's possible that there's a busy-wait in the monitor; does it show
> high CPU usage?

The system is a dual CPU system and neither CPU was ever maxed at 100%
for my test. The interesting thing is that I am running Grass remotely
on an SGI Origin from an SGI Indigo2 and the system delay is somehow
related to the Indigo2 machine. As a test, I ran a demo program on the
Indigo2 that allows you to rotate a cube, while the XDRIVER was still
running on the Origin. The cube would periodically stop but when it
started rotating again, it skipped to its new positon. That is, the demo
kept running calculating the position of the cube, but the graphics
update was being delayed. I also noticed that the CPU on the Indigo2
machine was spending a lot of time dealing with interrupts
 
> I have time, but I don't have an SGI; if you can obtain any more
> information it would help.

I can give a few minutes to test something but I don't have time for
debugging. Oh yeah, the system delay didn't seem to occur until just
before the d.mon command quit. I don't know if that helps or not.

> I've checked in one change already; there is a flag ("no_mon") which
> is set in the SIGALRM handler and tested in sync_driver(). I've
> changed the declaration to include "volatile", although this 
> shouldn't matter unless the compilation had optimisation enabled.

No optimization was used.

Sorry I couldn't be much help.

-- 
Sincerely,

Jazzman (a.k.a. Justin Hickey)  e-mail: jhickey at hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand
==================================================================
People who think they know everything are very irritating to those
of us who do.  ---Anonymous

Jazz and Trek Rule!!!
==================================================================

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'



More information about the grass-dev mailing list