Messages in this thread | | | Date | Thu, 29 Jul 1999 20:42:52 +0200 | From | Kurt Garloff <> | Subject | Re: linuxthreads and tid testing |
| |
On Wed, Jul 28, 1999 at 10:44:24PM -0500, Peter Hatch wrote: > I'm interested in fixing this problem, but the linuxthreads implementation is > the only one I've seen the source to, so it's the only one I fully understand. > We've tossed around several potential solutions, but they all rely upon each > thread having it's own PID, which is apparently a quality of linuxthreads that > is in contention??
I think that most kernel hackers agree, that it's a good thing to have threads handled like processes with some special features wrt VM, signals, ... This allows the kernel (scheduler) and all the tools (ps, top, gdb, ...) to just magically work. I see no technical reason to change it. (And I don't accept, that it looks nicer to see only one PID for one multithreaded app as a technical reason.)
I believe linuxthreads will have different pids for different threads in the future.
Just my 2¤ (<=\texteuro) -- Kurt Garloff <garloff@suse.de> SuSE GmbH, Nürnberg, FRG Linux kernel development; SCSI drivers: tmscsim(DC390), DC395 [unhandled content-type:application/pgp-signature] | |