From: Oleg Nesterov <oleg@tv-sign.ru>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Davide Libenzi <davidel@xmailserver.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Robin Holt <holt@sgi.com>, Roland McGrath <roland@redhat.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Gautham R Shenoy <ego@in.ibm.com>
Subject: Re: [PATCH] kthread: Don't depend on work queues (take 2)
Date: Wed, 11 Apr 2007 23:28:09 +0400 [thread overview]
Message-ID: <20070411192809.GA106@tv-sign.ru> (raw)
In-Reply-To: <m1hcrmsr4g.fsf_-_@ebiederm.dsl.xmission.com>
On 04/11, Eric W. Biederman wrote:
>
> @@ -435,8 +436,12 @@ static void __init setup_command_line(char *command_line)
> static void noinline rest_init(void)
> __releases(kernel_lock)
> {
> + int pid;
> kernel_thread(init, NULL, CLONE_FS | CLONE_SIGHAND);
> numa_default_policy();
> +
> + pid = kernel_thread(kthreadd, NULL, CLONE_FS | CLONE_FILES);
> + kthreadd_task = find_task_by_pid(pid);
> unlock_kernel();
Just curious. What if kernel/kthread.c declares
static struct task_struct *kthreadd_task = &init_task;
an then kthreadd_setup() does kthreadd_task = current. I assume it is always
safe to try_to_wake_up(idle_thread), because it always TASK_RUNNING. This
way we don't need to export kthreadd_task.
> + spin_lock(&kthread_create_lock);
> + list_add_tail(&create.list, &kthread_create_list);
> + wake_up_process(kthreadd_task);
> + spin_unlock(&kthread_create_lock);
Very minor nit, but we don't need to do wake_up under spin_unlock().
Oleg.
next prev parent reply other threads:[~2007-04-11 19:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 18:51 [PATCH 2/3] make kernel threads invisible to /sbin/init Oleg Nesterov
2007-04-10 23:16 ` Serge E. Hallyn
2007-04-11 3:29 ` Eric W. Biederman
2007-04-11 3:56 ` Eric W. Biederman
2007-04-11 11:42 ` Oleg Nesterov
2007-04-11 5:44 ` [PATCH] kthread: Don't depend on work queues Eric W. Biederman
2007-04-11 7:03 ` Andrew Morton
2007-04-11 10:13 ` Rafael J. Wysocki
2007-04-11 11:21 ` Gautham R Shenoy
2007-04-11 11:48 ` Oleg Nesterov
2007-04-11 13:31 ` Gautham R Shenoy
2007-04-11 14:36 ` Oleg Nesterov
2007-04-11 19:37 ` Rafael J. Wysocki
2007-04-11 14:44 ` Rafael J. Wysocki
2007-04-11 18:22 ` Eric W. Biederman
2007-04-11 18:27 ` [PATCH] kthread: Don't depend on work queues (take 2) Eric W. Biederman
2007-04-11 18:49 ` [PATCH] Change reparent_to_init to reparent_to_kthreadd Eric W. Biederman
2007-04-11 19:21 ` [PATCH] kthread: Don't depend on work queues (take 2) Andrew Morton
2007-04-11 19:28 ` Oleg Nesterov [this message]
2007-04-11 19:40 ` Eric W. Biederman
2007-04-11 19:49 ` Oleg Nesterov
2007-04-11 20:02 ` Eric W. Biederman
2007-04-11 12:04 ` [PATCH] kthread: Don't depend on work queues Oleg Nesterov
2007-04-11 16:25 ` Eric W. Biederman
2007-04-11 13:15 ` Oleg Nesterov
2007-04-11 16:22 ` 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=20070411192809.GA106@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=ebiederm@xmission.com \
--cc=ego@in.ibm.com \
--cc=holt@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=roland@redhat.com \
--cc=serge@hallyn.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 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.