From: girish <girishvg@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
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-3)
Date: Sun, 1 Oct 2006 20:34:30 +0900 [thread overview]
Message-ID: <FD5311BD-3DE3-4185-B093-CE05199F09C7@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0609301908460.4615@yvahk01.tjqt.qr>
>> PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD
>> RSIZE VSIZE
>> 22429 top 16.6% 0:21.12 1 18 20 1.35M 684K
>> 1.77M 26.9M
>> ---------------------------------------------------------------------
>> ---
>> --------------------------------------------------------
>>
>> Comments/opinions?
>
> I fail to see which column you mean.
>
> #TH perhaps? I think, that can be calculated under linux by
>
> (a) counting the directories in /proc/22429/task using readdir
> or
I have implemented the child_count script, in this way. I was
wondering what is more convenient.
> (b) get the nlink of /proc/22429/task and subtract 2, which should
> give
> the same as (a), and, better than (a), should also be atomic
This one, is good. I did not think about this approach.
prev parent reply other threads:[~2006-10-01 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 15:18 [PATCH] include children count, in Threads: field present in /proc/<pid>/status (take-1) 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
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 [this message]
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=FD5311BD-3DE3-4185-B093-CE05199F09C7@gmail.com \
--to=girishvg@gmail.com \
--cc=ebiederm@xmission.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®