From: ebiederm@xmission.com (Eric W. Biederman)
To: girish <girishvg@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
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: Fri, 29 Sep 2006 16:51:24 -0600 [thread overview]
Message-ID: <m1mz8ii8wj.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <BEC70F7E-6143-4D8D-9800-A8538A152A18@gmail.com> (girishvg@gmail.com's message of "Sat, 30 Sep 2006 03:24:41 +0900")
This conflicts with the /proc changes in -mm.
Where we have manged to remove the use of the tasklist_lock.
The information in Children: is racy as it may change immediately
after you drop the lock.
Why is it interesting to report this information?
A process that cares can keep track of this in user space?
Eric
> Signed-off-by: Girish V. Gulawani <girishvg@gmail.com>
>
> --- linux-vanilla/fs/proc/array.c 2006-09-20 12:42:06.000000000 +0900
> +++ linux/fs/proc/array.c 2006-09-30 03:18:28.000000000 +0900
> @@ -248,6 +248,8 @@ static inline char * task_sig(struct tas
> int num_threads = 0;
> unsigned long qsize = 0;
> unsigned long qlim = 0;
> + int num_children = 0;
> + struct list_head *_p;
>
> sigemptyset(&pending);
> sigemptyset(&shpending);
> @@ -268,9 +270,13 @@ static inline char * task_sig(struct tas
> qlim = p->signal->rlim[RLIMIT_SIGPENDING].rlim_cur;
> spin_unlock_irq(&p->sighand->siglock);
> }
> + list_for_each(_p, &p->children)
> + ++num_children;
> read_unlock(&tasklist_lock);
>
> buffer += sprintf(buffer, "Threads:\t%d\n", num_threads);
> + if (num_children)
> + buffer += sprintf(buffer, "Children:\t%d\nTotal:\t%d\n",
> num_children, num_threads + num_children);
> buffer += sprintf(buffer, "SigQ:\t%lu/%lu\n", qsize, qlim);
>
> /* render them all */
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-09-29 22:53 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 [this message]
[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=m1mz8ii8wj.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=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®