mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: girish <girishvg@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org, William Pitcock <nenolod@atheme.org>
Subject: Re: [PATCH] include children count, in Threads: field present in /proc/<pid>/status (take-1)
Date: Sat, 30 Sep 2006 02:18:12 +0900	[thread overview]
Message-ID: <CF74CE5D-42A1-4FF9-8C9B-682C5D6DEAE1@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0609291905550.27518@yvahk01.tjqt.qr>


On Sep 30, 2006, at 2:06 AM, Jan Engelhardt wrote:

>>>>
>>>> -	buffer += sprintf(buffer, "Threads:\t%d\n", num_threads);
>>>> +	buffer += sprintf(buffer, "Threads:\t%d\n", num_threads +
>>>> num_children);
>>>
>>> Personally, I'd prefer the children count to be separate,  
>>> something like:
>>>
>>> buffer += sprintf(buffer, "Threads:\t%d (%d children, %d total)",
>>> num_threads, num_children, num_threads + num_children);
>>>
>>> That would be rather nice, indeed.
>
> And I would suggest three separate lines to keep it parseable!
>
>
> Jan Engelhardt
> -- 

How about this?

         buffer += sprintf(buffer, "Threads:\t%d", num_threads);
         if (num_children)
                 buffer += sprintf(buffer, " Children: %d Total: %d",  
num_children, num_threads + num_children);
         buffer += sprintf(buffer, "\n");


  reply	other threads:[~2006-09-29 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29 15:18 girish
2006-09-29 16:31 ` William Pitcock
2006-09-29 16:51   ` girish
2006-09-29 17:06     ` Jan Engelhardt
2006-09-29 17:18       ` girish [this message]
2006-09-29 18:12         ` Jan Engelhardt
2006-09-29 18:24           ` [PATCH] include children count, in Threads: field present in /proc/<pid>/status (take-3) girish
2006-09-29 22:51             ` Eric W. Biederman
     [not found]               ` <E78297DA-5F0F-40FA-A008-89264570B313@gmail.com>
2006-09-30 17:11                 ` Jan Engelhardt
2006-10-01 11:34                   ` girish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CF74CE5D-42A1-4FF9-8C9B-682C5D6DEAE1@gmail.com \
    --to=girishvg@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nenolod@atheme.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®