| 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
| ||
|
Date: Thu, 12 Jul 2007 12:48:14 -0400 From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen) To: "Ni@m" <niam.niam@...il.com> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: Fwd: NPTL On Thu, Jul 12, 2007 at 03:58:34PM +0300, Ni@m wrote: > Of course .. I ment they are _almoust_ similar. The lack of an address space seems to make them rather different too. A process contains address space, and one or more threads. A thread is hence a component of a process, but not really similar to a process since it is just part of a process. > Hm. If the thread is running after it's sister or parent process - you > do not have to switich the process context. Is this done in kernel?? You are switching out cpu registers, stack, and such, even though you are not changing address space, so you are doing a context switch. The cpu registers and state is the context. Running multiple threads of a single process in a row can avoid messing with the TLB and other address space related things, but it still switches context. -- Len Sorensen - 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