NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/comp/sys/sgi/18313

Internet Message Format | 1992-12-23 | 1.8 KB

Path: sparky!uunet!olivea!sgigate!odin!everest.esd.sgi.com!mas
From: [e-mail] (Michael Schulman)
Newsgroups: comp.sys.sgi
Subject: Re: CPU Type Detection
Message-ID: <[e-mail]>
Date: 23 Dec 92 23:21:42 GMT
References: <[e-mail]>
Sender: [e-mail] (Net News)
Reply-To: [e-mail]
Organization: Silicon Graphics Computer Systems, Mountain View, CA
Lines: 39
Nntp-Posting-Host: everest.esd.sgi.com

In article <[e-mail]>, [e-mail] (Frederick R. Phelan Jr.) writes:
|> From: [e-mail] (Frederick R. Phelan Jr.)
|> Newsgroups: comp.sys.sgi
|> Subject: CPU Type Detection
|> Date: Wed, 23 Dec 92 12:32:14 PDT
|> Lines: 11
|>
|> We have a graphics application for animated contouring that we need to slow down
|> when running on a Crimson.  The sginap(k) function does this nicely, but I would
|> like to feed it k based on the CPU it encounters so I don't need to recompile for
|> different machines.  How does one detect the CPU type at run time?  On a PI we
|> want no sginap, on the Crimson, we want an sginap(2).  Note that this app is
|> CPU bound not graphics bound, so getgdesc(~) to detect VGX vs. GT etc. is not what
|> we want.
|>
|> ---
|> Fred Phelan
|> [e-mail]

Another not so elegant solution is to have a loop that executes for some
period of time at the start of the program ( say 2 secs ).  From the timing
of this loop, you could then determine what the sginap value should be.  This
will work in the future, when the getinvent call returns new and faster values
that your program might not understand.



--

Michael Schulman
Manager, Technical Marketing
Engineering & Scientific Applications

Silicon Graphics Computer Systems
2011 N. Shoreline Blvd.
Mountain View, CA 94039
415-390-3308

[e-mail]