mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Wed, 08 Mar 2006 13:00:58 -0700	[thread overview]
Message-ID: <m1irqovh8l.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <440F2F4A.3E91C272@tv-sign.ru> (Oleg Nesterov's message of "Wed, 08 Mar 2006 22:23:54 +0300")

Oleg Nesterov <oleg@tv-sign.ru> writes:

> Changes:
> 	s/tgrp/thread_group/
>
> 	make it rcu-safe
>
> [PATCH rc5-mm] pids: kill PIDTYPE_TGID
>
> depends on pidhash-dont-count-idle-threads.patch
>
> 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 thread_group' to 'struct task_struct'
> instead.
>
> 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.
>
> 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.

Looks good.  I have one final nit.

> --- 2.6.16-rc5/kernel/fork.c~1_TGID	2006-03-09 00:17:24.000000000 +0300
> +++ 2.6.16-rc5/kernel/fork.c	2006-03-09 00:41:35.000000000 +0300
> @@ -1100,6 +1100,7 @@ static task_t *copy_process(unsigned lon
>  	 * We dont wake it up yet.
>  	 */
>  	p->group_leader = p;
> +	INIT_LIST_HEAD(&p->thread_group);
>  	INIT_LIST_HEAD(&p->ptrace_children);
>  	INIT_LIST_HEAD(&p->ptrace_list);
>  
> @@ -1153,7 +1154,9 @@ static task_t *copy_process(unsigned lon
>  			retval = -EAGAIN;
>  			goto bad_fork_cleanup_namespace;
>  		}
> +
>  		p->group_leader = current->group_leader;
> +		list_add_tail_rcu(&p->thread_group, &current->thread_group);
Can this be:
		list_add_tail_rcu(&p->thread_group, &current->group_leader->thread_group);

That way at least the odds of missing a new task_struct when doing an
rcu traversal are reduced almost to 0.

>  
>  		if (current->signal->group_stop_count > 0) {
>  			/*
> @@ -1201,7 +1204,6 @@ static task_t *copy_process(unsigned lon
>  			list_add_tail(&p->tasks, &init_task.tasks);
>  			__get_cpu_var(process_counts)++;
>  		}
> -		attach_pid(p, PIDTYPE_TGID, p->tgid);
>  		attach_pid(p, PIDTYPE_PID, p->pid);
>  		nr_threads++;
>  	}


Eric

  reply	other threads:[~2006-03-08 20:01 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
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 [this message]
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=m1irqovh8l.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®