From: ebiederm@xmission.com (Eric W. Biederman)
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH rc5-mm] pids: kill PIDTYPE_TGID
Date: Tue, 07 Mar 2006 15:42:54 -0700 [thread overview]
Message-ID: <m11wxd27wx.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <440DEADB.72C3A8A6@tv-sign.ru> (Oleg Nesterov's message of "Tue, 07 Mar 2006 23:19:39 +0300")
Oleg Nesterov <oleg@tv-sign.ru> writes:
> depends on
>
> pidhash-dont-count-idle-threads.patch
> pidhash-kill-switch_exec_pids.patch
>
> otherwise (I think) it is orthogonal to all tref/proc changes.
You also depend on your recent change to call __unhash_process
under the sighand lock. Since the ->tgrp is protected by
the sighand lock.
> This patch kills PIDTYPE_TGID pid_type thus saving one hash table
> in kernel/pid.c and speeding up subthreads create/destroy a bit.
> It is also a preparation for the further tref/pids rework.
>
> This patch adds 'struct list_head tgrp' to 'struct task_struct'
> instead. Note that ->tgrp need not to be rcu safe.
Is there a reason for this? I think at least proc could easily
take advantage of an rcu safe implementation.
Hmm. At the moment proc is only taking the tasklist_lock during
traversal so we may have a problem with the list_add anyway.
Also could we name the member not ->tgrp but ->threads?
I keep half expecting tgrp to be a number, and have a hard
time not mispelling it tpgrp.
> We don't detach group leader from PIDTYPE_PID namespace until another
> thread inherits it's ->pid == ->tgid, so we are safe wrt premature
> free_pidmap(->tgid) call.
Agreed.
> Currently there are no users of find_task_by_pid_type(PIDTYPE_TGID).
> Should the need arise, we can use find_task_by_pid()->group_leader.
>
> include/linux/pid.h | 1 -
> include/linux/sched.h | 10 +++++++---
> kernel/exit.c | 10 +---------
> kernel/fork.c | 4 +++-
> 4 files changed, 11 insertions(+), 14 deletions(-)
Eric
next prev parent reply other threads:[~2006-03-07 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 20:19 Oleg Nesterov
2006-03-07 22:42 ` Eric W. Biederman [this message]
2006-03-08 14:41 ` Oleg Nesterov
2006-03-08 16:19 ` Eric W. Biederman
2006-03-08 19:23 ` Oleg Nesterov
2006-03-08 20:00 ` Eric W. Biederman
2006-03-08 21:46 ` Oleg Nesterov
2006-03-08 22:12 ` Eric W. Biederman
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=m11wxd27wx.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=paulmck@us.ibm.com \
--cc=torvalds@osdl.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®