Hi Daniel,
I believe you didn't understand what Darryl wrote. It's probably just a
language issue. The sentence below says "not just help", not "not help". What
he means is that in addition to helping with locality issues, it also helps with
thread migrations.
So you are right (and that's wha
It really depends on the definition of idl. Is idl defined to be the
rounded idle time or 100 - (sum of the rounded sys + rounded usr).
They will be different (as in the example below). Which is correct is
dependent on the definition you want to use.
But as Jim points out, for most analysis the
Hi Stefan,
I haven't looked at the code to see exactly what it does, but what you
see could easily be explained by rounding.
For example, in the line above the one you mark, usr and sys are both 1, with
idl being 97. That doesn't add up to 100, either. But suppose usr and sys
are both 1.3, whic
You can also look at the "intrstat" tool which displays information
on each interrupt and the cpu handling it.
Dave Miller
Elad Lahav wrote, On 08/12/08 08:03:
> On Linux, it is possible to determine which processors on a
> multiprocessor handle each interrupt (via
> /proc/irq/IRQ_NUM/smp_affin
Hi Mark,
How much memory do you have on the system? By default, Solaris now allows a
user to allocate up to 1/4 of that for shared memory. If you don't have
80G or more, the allocation will fail.
You can change that by altering the project value for the user for
project.max-shm-memory. See "ma
