From: ebiederm@xmission.com (Eric W. Biederman)
To: "Albert Cahalan" <acahalan@gmail.com>
Cc: linux-kernel@vger.kernel.org, holt@sgi.com, oleg@tv-sign.ru,
roland@redhat.com, davidel@xmailserver.org, mingo@elte.hu,
torvalds@linux-foundation.org, akpm@linux-foundation.org
Subject: Re: [RFC, PATCH 1/3] introduce SYS_CLONE_MASK
Date: Mon, 28 May 2007 22:57:49 -0600 [thread overview]
Message-ID: <m11wh08bw2.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <787b0d920705281959l53e74d02g21a6fecd86d73219@mail.gmail.com> (Albert Cahalan's message of "Mon, 28 May 2007 22:59:28 -0400")
"Albert Cahalan" <acahalan@gmail.com> writes:
> This has long been rotten. Mind fixing it for us? :-)
>
> We have N types of thread on M CPUs. Pick something, N or M,
> to be at the top level in /proc. The other goes below, in the
> per-process task directories.
>
> You then have either N or M things showing up in ps, not N*M.
>
> Note that both ps and top can print the CPU number just fine.
> Abusing the task name for this is just retarded. This suggests
> that the top level should be the type of task, with the lower
> level in /proc/*/task being per-CPU and not needing distinct
> naming at all.
In a lot of ways that is reasonable. However kernel threads don't
share signal handling and getting to the point where they could share
signal handling would be difficult so we cannot use the generic
CLONE_THREAD handling they really are more like individual processes.
So at that level the cpu number in the name is just to help tell them
apart.
Eric
next prev parent reply other threads:[~2007-05-29 4:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 2:59 [RFC, PATCH 1/3] introduce SYS_CLONE_MASK Albert Cahalan
2007-05-29 4:57 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-29 3:23 Albert Cahalan
2007-05-29 4:53 ` Eric W. Biederman
2007-05-29 5:56 ` Roland McGrath
2007-05-30 0:33 ` Albert Cahalan
2007-05-30 1:43 ` Eric W. Biederman
2007-07-26 7:34 ` Jan Engelhardt
2007-04-08 15:53 Oleg Nesterov
2007-04-08 16:19 ` Eric W. Biederman
2007-04-08 16:57 ` Oleg Nesterov
2007-04-09 1:05 ` Eric W. Biederman
2007-04-09 2:06 ` Roland McGrath
2007-04-09 16:20 ` Eric W. Biederman
2007-04-09 17:30 ` Robin Holt
2007-04-10 0:35 ` Eric W. Biederman
2007-04-10 9:56 ` Robin Holt
2007-04-09 9:06 ` Oleg Nesterov
2007-04-09 10:43 ` Robin Holt
2007-04-09 14:36 ` Eric W. Biederman
2007-04-09 14:52 ` Robin Holt
2007-04-10 15:47 ` Jan Engelhardt
2007-04-10 18:20 ` Jan Engelhardt
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=m11wh08bw2.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=acahalan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=torvalds@linux-foundation.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