From owner-freebsd-current@FreeBSD.ORG Fri May 23 20:39:47 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8B25A74D; Fri, 23 May 2014 20:39:47 +0000 (UTC) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 541AF2432; Fri, 23 May 2014 20:39:47 +0000 (UTC) Received: from critter.freebsd.dk (unknown [192.168.60.3]) by phk.freebsd.dk (Postfix) with ESMTP id 8A0C71578; Fri, 23 May 2014 20:39:39 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.8/8.14.8) with ESMTP id s4NKddur009765; Fri, 23 May 2014 20:39:39 GMT (envelope-from phk@phk.freebsd.dk) To: John Baldwin Subject: Re: Change top's notion of idle processes / threads In-reply-to: <201405231605.26312.jhb@freebsd.org> From: "Poul-Henning Kamp" References: <201405231605.26312.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Date: Fri, 23 May 2014 20:39:39 +0000 Message-ID: <9764.1400877579@critter.freebsd.dk> Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 20:39:47 -0000 In message <201405231605.26312.jhb@freebsd.org>, John Baldwin writes: >In essence, top will consider any thread that has run on a CPU >since the last update as non-idle. Sounds a lot more usable than the current heuristic. Wouldn't ki_rusage.ru_n[i]vcsw be more correct than ki_runtime ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.