Date: Sat, 27 Dec 2008 13:04:30 +0100 From: =?ISO-8859-2?Q?Nikola_Kne=BEevi=E6?= <laladelausanne@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: ps not showing CPU# correctly Message-ID: <13986D39-BE78-4CB4-A1E5-83F0382915AC@gmail.com> In-Reply-To: <e7799ca20812261730x27e09d46p834b19d9dee17e97@mail.gmail.com> References: <7555893E-5D2F-4C3C-A1C7-7BCC2461AE23@gmail.com> <e7799ca20812261730x27e09d46p834b19d9dee17e97@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 Dec 2008, at 02:30 , Mateusz Guzik wrote: >> on my system, I noticed that ps(1) is not showing the CPU# >> correctly (it >> always displays 0). There was a bug in it, and it was fetching >> ki_estcpu >> instead of ki_lastcpu. >> > > From the man page: > cpu short-term CPU usage factor (for scheduling) > > Apparently not last cpu's number. :) You're probably using SCHED_ULE - > this scheduler does not alter td_estcpu and that's why ps -o cpu gives > you only 0. Ups :) I got mislead with top showing the cpu on which process executes. I find the information on which cpu is process/thread executed quite useful for performance debugging. Maybe I should add it to ps as cpu# or cpuno or cpuid? Cheers, Nikola
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13986D39-BE78-4CB4-A1E5-83F0382915AC>