[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1318600023.2223.18.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
Date: Fri, 14 Oct 2011 15:47:03 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: "Seger, Mark" <mark.seger@...com>
Cc: "Oberman, Laurence (HAS GSE)" <Laurence.Oberman@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Cabaniols, Sebastien" <Sebastien.Cabaniols@...com>
Subject: RE: Regression in reading /proc/stat in the newer kernels with
large SMP and NUMA configurations
Le vendredi 14 octobre 2011 à 14:36 +0100, Seger, Mark a écrit :
> For me the easiest reproducer, which admittedly doesn't show any
> deeper analysis, is to just run "cat /proc/stat>/dev/null" in a loop
> and time it.
OK, but you already provided a global number.
We would like to check where in kernel cpu time is consumed.
Maybe something really obvious could pop out.
"perf" is provided in kernel sources, and really is a piece of cake.
cd tools/perf ; make
2x4x2 means : Two sockets, 4 cores per physical package, 2 threads per
core.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists