From owner-freebsd-stable@FreeBSD.ORG Thu May 12 16:40:24 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B66916A5E0 for ; Thu, 12 May 2005 16:40:24 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D80B043D64 for ; Thu, 12 May 2005 16:40:21 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])j4CGcfIK015162; Thu, 12 May 2005 19:38:42 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) j4CGeGLo042139; Thu, 12 May 2005 19:40:16 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost)j4CGeFK8042138; Thu, 12 May 2005 19:40:15 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 12 May 2005 19:40:15 +0300 From: Giorgos Keramidas To: Jonathan Noack Message-ID: <20050512164015.GA42110@orion.daedalusnetworks.priv> References: <1115815807.8809.3.camel@buffy.york.ac.uk> <20050512103929.GB1320@orion.daedalusnetworks.priv> <200505121349.31508.dom@goodforbusiness.co.uk> <20050512131219.GB3107@orion.daedalusnetworks.priv> <42836B8F.607@alumni.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42836B8F.607@alumni.rice.edu> cc: Dominic Marks cc: freebsd-stable@freebsd.org Subject: Re: Strange top(1) output X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2005 16:40:24 -0000 On 2005-05-12 09:43, Jonathan Noack wrote: >On 5/12/2005 8:12 AM, Giorgos Keramidas wrote: >>On 2005-05-12 13:49, Dominic Marks wrote: >>>> + When the view is toggled between processes/threads, the NTHR part >>>> becomes the thread ID of the particular thread. >>> >>> Okay, not really sure what this will look like to me but no need to >>> explain I'll wait until they hit -CURRENT and see for myself. >> >> Instead of displaying a single named/7 line, which would mean that >> there is a named process with 7 threads, in "thread mode" you would >> see 7 lines with named/0, named/1, named/2, ... which would be the >> thread IDs of the distinct threads. > > What happens if the command is long enough to overrun the screen? Is > the thread information truncated and lost? I believe this was the > argument for making a separate column for the thread info. By removing the THR column and merging CPU into WCPU we gain a lot of columns, so I'm hoping that it would be ok to trim the command name in favor of the thread count. Before actually having something in the form of a patchfile though it's hard to tell if it's going to be good or not. - Giorgos