| 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
| ||
|
Message-ID: <46962413.8060702@gmail.com> Date: Thu, 12 Jul 2007 18:22:35 +0530 From: jimmy bahuleyan <knight.camelot@...il.com> To: "Ni@m" <niam.niam@...il.com> CC: davids@...master.com, LKML <linux-kernel@...r.kernel.org> Subject: Re: NPTL Ni@m wrote: > So I can say that in linux 'thread' == 'process'? > No. It's more like, in linux threads are visible to the kernel (unlike in N:1 thread models, linux is 1:1). Threads are the basic unit of scheduling. A process can have >1 threads. > Is kernel routine 'kthread' creating a process? > I'm just thinking on this subject: if to create 'real threads' - will > it increase performance? Should I ever think in this way? > When I say 'real thread' - I mean the thread that doen't switch > context when it's starting to run. > What do you mean by context? Each thread has it's own stack, registers, etc. which form it's context. A process has more info like file descriptors, IPC resources, virtual memory info. Between scheduling threads of the same process these stay same. -jb -- Tact is the art of making a point without making an enemy. - 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/
Powered by blists - more mailing lists