From owner-freebsd-current@FreeBSD.ORG Sat Apr 16 14:55:45 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB73216A4CE; Sat, 16 Apr 2005 14:55:45 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0A4A43D2F; Sat, 16 Apr 2005 14:55:44 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-b193.otenet.gr [212.205.244.201]) j3GEsUUJ030320; Sat, 16 Apr 2005 17:54:30 +0300 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.3/8.13.3) with ESMTP id j3GEtTK4000873; Sat, 16 Apr 2005 17:55:29 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.3/8.13.3/Submit) id j3GEtQCS000872; Sat, 16 Apr 2005 17:55:26 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Sat, 16 Apr 2005 17:55:26 +0300 From: Giorgos Keramidas To: David Xu Message-ID: <20050416145525.GA821@gothmog.gr> References: <425CC7F8.3030803@samsco.org> <425CD009.6040208@freebsd.org> <20050413132603.GA39006@orion.daedalusnetworks.priv> <20050413140838.GA77217@renaissance.homeip.net> <20050413141957.GA40546@orion.daedalusnetworks.priv> <20050415055604.N93987@lexi.siliconlandmark.com> <20050415164941.E93987@lexi.siliconlandmark.com> <4260D92C.1030703@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4260D92C.1030703@freebsd.org> cc: freebsd-current@freebsd.org cc: Jiawei Ye cc: Julian Elischer cc: Anthony Ginepro Subject: Re: How does one know how many thread a process owns? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sat, 16 Apr 2005 14:55:45 -0000 On 2005-04-16 17:21, David Xu wrote: >>I realize that top isn't an exact science, but I find that >>approximations are generally a bad idea. I am in favor of axing the >>useless CPU column and reclaiming some useful screen space for the >>others... :) I considered that, but didn't know when or if the CPU column does make sense. > CPU column is not very useful when displaying process and thread > count, if it is only useful if it is displaying individual thread > which is activated by 'H' key. Thanks for that. This is good to know :-) Unfortunately, the current implementation of top makes it absurdly difficult to set up different "fields" for each mode that top supports; but it's ok, I'm already looking at ways to make all the visible columns configurable by the current mode.