Strange top(1) output
keramida at ceid.upatras.gr
Thu May 12 09:40:24 PDT 2005
On 2005-05-12 09:43, Jonathan Noack <noackjr at alumni.rice.edu> wrote:
>On 5/12/2005 8:12 AM, Giorgos Keramidas wrote:
>>On 2005-05-12 13:49, Dominic Marks <dom at goodforbusiness.co.uk> 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.
More information about the freebsd-stable