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] [day] [month] [year] [list]
Date:	Thu, 12 Jul 2007 05:58:20 -0700
From:	"David Schwartz" <davids@...master.com>
To:	"LKML" <linux-kernel@...r.kernel.org>
Subject: RE: NPTL


> So I can say that in linux 'thread' == 'process'?

No. A process can have any number of threads.

> Is kernel routine 'kthread' creating a process?

No, since a process can have more than one thread.

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

I don't follow.

The kernel sometimes calls a KSE a 'process'. This is largely a legacy from
when there was a one-to-one correspondence between KSEs and processes.
However, this is no longer the case. In Linux, 'KSE' == 'thread'.

DS


-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ