From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Oleg Nesterov <oleg@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: Expose /proc/<pid>/task/<tid>/children unconditionally
Date: Wed, 26 Jun 2013 11:21:02 +0400 [thread overview]
Message-ID: <20130626072102.GE1726@moon> (raw)
In-Reply-To: <CALCETrV2WZ3m82D4THfxvmASW8AOf1SN7Pu14vE0jMORupO5xw@mail.gmail.com>
On Tue, Jun 25, 2013 at 03:01:35PM -0700, Andy Lutomirski wrote:
>
> This is a little strange. It looks like ppid (in status) shows the
> tgid, but the actual real_parent can refer to a thread (as opposed to
> a thread group leader), and task/tid/children respects that. So the
> tree that you get by following task/tid/ children won't be quite the
> same as the tree you get by following ppid.
>
> I wonder if the ptid should be added to status. Is there anything
> (other than task/tid/children) that cased which thread is the parent
> of a given task?
None I know of. As to ptid -- sounds reasonable to me. Oleg?
next prev parent reply other threads:[~2013-06-26 7:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 19:51 [PATCH] proc: Expose /proc/<pid>/task/<tid>/children unconditionally Andy Lutomirski
2013-06-25 20:16 ` Cyrill Gorcunov
2013-06-25 20:17 ` Oleg Nesterov
2013-06-25 21:36 ` Andy Lutomirski
2013-06-25 21:52 ` Cyrill Gorcunov
2013-06-25 22:01 ` Andy Lutomirski
2013-06-26 7:21 ` Cyrill Gorcunov [this message]
2013-06-26 15:57 ` Oleg Nesterov
2013-06-26 16:14 ` Andy Lutomirski
2013-06-26 21:05 ` [PATCH] proc: Document that /proc/<pid>/task/<tid>/children really is per-thread Andy Lutomirski
2013-06-27 6:21 ` Cyrill Gorcunov
2013-07-01 16:49 ` Rob Landley
2013-07-01 17:36 ` Andy Lutomirski
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=20130626072102.GE1726@moon \
--to=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.