From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 6 17:57:36 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81EB7106564A for ; Sat, 6 Aug 2011 17:57:36 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 6DD338FC14 for ; Sat, 6 Aug 2011 17:57:36 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id p76HvZ8u024741; Sat, 6 Aug 2011 10:57:36 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4E3D808F.1030101@rawbw.com> Date: Sat, 06 Aug 2011 10:57:35 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110716 Thunderbird/5.0 MIME-Version: 1.0 To: Alexander Best References: <4E3CC033.6070604@rawbw.com> <20110806091127.GA39951@freebsd.org> In-Reply-To: <20110806091127.GA39951@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: top(1) loses process user time count when threads end X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Aug 2011 17:57:36 -0000 On 08/06/2011 02:11, Alexander Best wrote: > On Fri Aug 5 11, Yuri wrote: >> I have the process that first runs in 3 threads but later two active >> threads exit. >> >> top(1) shows this moment this way (1 sec intervals): >> 30833 yuri 3 76 0 4729M 4225M nanslp 4 0:32 88.62% app >> 30833 yuri 3 76 0 4729M 4225M nanslp 6 0:34 90.92% app >> 30833 yuri 1 96 0 4729M 4225M CPU1 1 0:03 1.17% app >> 30833 yuri 1 98 0 4729M 4226M CPU1 1 0:04 12.89% app >> >> Process time goes down: 0:34 -> 0:03. Also WCPU goes down 90.92% -> >> 1.17% even though this process is CPU bound and does intense things >> right after threads exit. >> >> getrusage(2) though, called in the process, shows the correct user time. >> >> I think this is the major bug in the process time accounting. > could you check, whether kern/128177 or kern/140892 describe your situation? I have ULE scheduler. kern/128177 talks about single thread with ULE scheduler, and my issue is with threads. So I am not sure if it is related. There have been no motion on kern/128177 since Feb 9, 2009. kern/140892 is probably the same as mine. In any case, both these PRs have to be fixed since they are very user visible, not just some obscure issues. Yuri