From: Nobin Mathew <nobin.mathew@gmail.com>
To: Shivdas Gujare <shivdas.tech@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: init_task belongs to "process 0" or "process 1"?
Date: Tue, 5 Jan 2010 13:02:46 +0530 [thread overview]
Message-ID: <8d6898731001042332m6b5b97b0n5515ae166f62aad2@mail.gmail.com> (raw)
In-Reply-To: <cf70f0211001040007s5be9f1aas7bb52928c8d50e7c@mail.gmail.com>
init_task is the head of doubly linked list which holds all
task_structs in the system. init_task is again the task_struct for
process 0/swapper/idle task. This process is created manually (I meant
to say not by copy_process() calls). Manually means they are static
structures defined in the code (see INIT_TASK, init_mm, init_fs etc).
There will be multiple idle task if there is more than 1 cpu core.
Idle task is the one which is scheduled if there is no other task
ready for scheduling.
Init task is process 1 which is initially a kernel thread created from
process 0 using copy_process(), then it does an execv() (/sbin/init )
or similar one to create the normal process init.
Name given to process 0 is swapper.
.comm = "swapper"
On Mon, Jan 4, 2010 at 1:37 PM, Shivdas Gujare <shivdas.tech@gmail.com> wrote:
> Hi all,
>
> I am trying to understand the role of linux kernel "process 0" i.e. swapper.
> I am not able to understand, where it gets started? and Does
> "init_task" from arch/arm/kernel/init_task.c belongs to "swapper" or
> "init"?
> whats the purpose of "init_task"?
>
> Thanks for your help.
>
> Thanks and Regards,
> Shivdas Gujare
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2010-01-05 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 8:07 Shivdas Gujare
2010-01-05 7:32 ` Nobin Mathew [this message]
2010-01-05 15:52 ` Chris Friesen
2010-01-10 20:58 ` Leonidas .
2010-01-11 12:23 ` Nobin Mathew
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=8d6898731001042332m6b5b97b0n5515ae166f62aad2@mail.gmail.com \
--to=nobin.mathew@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shivdas.tech@gmail.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 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®