pcp
[Top] [All Lists]

Re: [pcp] pernode metrics still wrong on 1 CPU systems

To: Mark Goodwin <goodwinos@xxxxxxxxx>, Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pernode metrics still wrong on 1 CPU systems
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 21 Jan 2015 17:52:26 -0500 (EST)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <54C02474.9000407@xxxxxxxxx>
References: <54C00816.10808@xxxxxxxxxxxxxxxx> <54C02474.9000407@xxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: /fabYa7WUFII9uPaXtOOZygivtO2ww==
Thread-topic: pernode metrics still wrong on 1 CPU systems

----- Original Message -----
> [...]
> > Mark, what additional info would help diagnose/fix this?
> 
> what is vm04 (kernel non-smp? uname -a, which distro)?
> 
> ls -l /sys/devices/system/node
> ls -l /sys/devices/system/node/node0/cpu*
> 
> As previously noted, I'm merging and partly re-writing proc_cpuinfo.[ch]
> and proc_stat.[ch], including the pernode metrics. I wont get time to work
> on this at all until Saturday. A shorter term fix might be possible with
> the above requested info ..

I have one machine here reporting no NUMA nodes, if that's the trigger?

$ pminfo -f hinv.nnode

hinv.nnode
    value 0

$ ls /sys/devices/system/node
ls: cannot access /sys/devices/system/node: No such file or directory

$ uname -a
Linux verge 3.2.0-4-rt-686-pae #1 SMP PREEMPT RT Debian 3.2.41-2 i686 GNU/Linux

We'll need a fix before Saturday, let me know if you want me to dig into
it further before then (but I don't want to duplicate work if either of
you guys are already looking) ... thanks!

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>