DragonFlyBSD

If you take "top" to only apply to CPU#1, doesn't the report then seem correct?

Does the manpage say it will average these values across CPUs when "-M" isn't used or are you just assuming it should be doing that?

On 11/15/12 01:34, John Marino via Redmine wrote:

Issue #2447 has been updated by John Marino.

If you take "top" to only apply to CPU#1, doesn't the report then seem correct?

Per his description, no,

Because it should be 50/50 (cpu/idle)
instead of 0/100 for cpu0 and 100/0 for cpu1

Only one of his processors is busy - for a total of 50% system-wide usage

Does the manpage say it will average these values across CPUs when "-M" isn't used or are you just assuming it should be doing that?

The label in the top display says 'states' (plural) - so either it should
be averaging, or we should change the label to say 'cpu0' - which would
be kind of silly - why would you only want to see the 1st processor activity
on an SMP system? e.g. why bother with the effort to only make it worse?

Upstream doesn't appear to have a multi cpu option, at least per the page
on unixtop.org - I don't have a Free/Net set of systems around to
review w/r/t to their behavior - per manpage similarities, openbsd appears
to default to multicpu, with a '-1' flag to force combined statistics,
but my sole openbsd machine is uniproc so not sure if this is accurate.

I'll try to noodle with this this weekend if noone gets to it by then.

Cheers,

- Chris

On 11/15/12 07:52, Chris Turner via Redmine wrote:

The label in the top display says 'states' (plural) -

Well - this was me reading it wrong - since 'states'
is what is said for multi CPU as well - states
looks to refer to e.g. user/system/idle 'states'.

But anyhow - an average would be better.

Will take a crack at it unless someone beats
me to it.

Cheers,

- Chris