linux-kernel - Re: init_task belongs to "process 0" or "process 1"?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 10 Jan 2010 12:58:06 -0800
From:	"Leonidas ." <leonidas137@...il.com>
To:	Nobin Mathew <nobin.mathew@...il.com>
Cc:	Shivdas Gujare <shivdas.tech@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: init_task belongs to "process 0" or "process 1"?

> 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.

An idle task per core? So these tasks must be having different pids
right? As per my understanding there is only 1 idle task, in that case
on multiple cores when there is no activties on more than one cores,
how things would work? Same task cant be stored on different cores at
the same time right?

How is this handled?

-Leo.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/