Re: SGI Interrupts

New Message Reply Date view Thread view Subject view Author view

Angus Dorbie (dorbie++at++sgi.com)
Fri, 22 May 1998 18:30:51 -0700

Angus Dorbie wrote:
>
> > Sorroche, Joe CEI-TACCSF wrote:
> >
> > People;
> >
> > We're running Performer 2.2 on an Onyx, IRIX 6.2 OS. When we
> > run gr_osview, for a second, the interrupts "peg" the processor. Any
> > hints?
> >
>
> You need to isolate and lockdown the CPUs you need for real-time and
> put a NOINTR=cpu_number directive for those CPUs in the stune file
> (I think) I can't confirm this right now but there should be mention
> of this in the archives and no doubt someone with a better memory than
> I will post the exact details.
>
> The new IRIX 6.5 OS has really kernel threads & interrupts so you

                                ^ insert "light weight" here (must type
slower & think faster).

> shouldn't have to worry about this in future unless you are _really_
> running at a high frame rate (I mean kHz).
>
> Cheers,Angus.
>
> --
> "Only the mediocre are always at their best." -- Jean Giraudoux
>
> For advanced 3D graphics Performer + OpenGL based examples and tutors:
> http://www.dorbie.com/
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com

-- 
"Only the mediocre are always at their best." -- Jean Giraudoux 


For advanced 3D graphics Performer + OpenGL based examples and tutors:
http://www.dorbie.com/
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:57:26 PDT

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