| 1 | |
|---|
| 2 | The IRIX port supports: |
|---|
| 3 | |
|---|
| 4 | - load meter |
|---|
| 5 | |
|---|
| 6 | - cpu meter: The cpu meter has a new X resource cpuFormat, with the |
|---|
| 7 | possible values of single, all, auto or both. It |
|---|
| 8 | determines how cpu meters are handled for |
|---|
| 9 | multiprocessors: single displays only meters for each |
|---|
| 10 | cpu, all displays only a cumulative meter for all cpus, |
|---|
| 11 | both displays both and auto behaves like both on mp |
|---|
| 12 | machines and single on up machines. |
|---|
| 13 | |
|---|
| 14 | - mem meter |
|---|
| 15 | |
|---|
| 16 | - gfx meter: Displays swapbuffers/second. |
|---|
| 17 | |
|---|
| 18 | Of course, you're welcome to send me patches. |
|---|
| 19 | |
|---|
| 20 | For the gfx meter, sadc is forked to read the activity. The sadc |
|---|
| 21 | process is handled from the singleton SarMeter, which reads the binary |
|---|
| 22 | data from sadc and converts it into structures. Currently, it parses |
|---|
| 23 | gfxinfo and diskinfo data. The diskinfo can be used to create a disk |
|---|
| 24 | meter, but I do not have the time currently. As said above, send me |
|---|
| 25 | patches ;). |
|---|
| 26 | |
|---|
| 27 | |
|---|
| 28 | It is tested on: |
|---|
| 29 | |
|---|
| 30 | IP20, IP22, IP27, IP30, IP32 and IP35. |
|---|
| 31 | |
|---|
| 32 | |
|---|
| 33 | Stefan Eilemann, Apr 03 eile@sgi.com |
|---|
| 34 | |
|---|
| 35 | $Id: README.irix,v 1.1.1.1 2008/05/04 15:53:48 emasson Exp $ |
|---|
