On Wed, Jul 28, 1999 at 10:44:24PM -0500, Peter Hatch wrote:
> I'm interested in fixing this problem, but the linuxthreads implementatio=
n is=20
> the only one I've seen the source to, so it's the only one I fully unders=
tand.=20
> We've tossed around several potential solutions, but they all rely upon =
each=20
> thread having it's own PID, which is apparently a quality of linuxthreads=
that=20
> 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,
=2E..=20
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.)
=20
I believe linuxthreads will have different pids for different threads in the
future.
Just my 2=A4 (<=3D\texteuro)
--=20
Kurt Garloff <garloff@suse.de> SuSE GmbH, N=FCrnberg, FRG
Linux kernel development; SCSI drivers: tmscsim(DC390), DC395
--UugvWAfsgieZRqgk
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3in
iQCVAwUBN6CgqxaQN/7O/JIVAQEdEwP/a8pw3LCUKucWKn7y8Pv5qKf+w6ui8w9k
oRy+L4Uakxn/e1gxGsIsnxgNGQkKuqcwNH+bheY5hwjZFZCy3o+o25MJCBLACtCD
JP0kFkBP/WZvxpIlvKfDPW0uZKucIabLxlGw1+cAaJNoaanzwIrq0smwK7ay0W5Z
nXBni9oYOmM=
=ISbT
-----END PGP SIGNATURE-----
--UugvWAfsgieZRqgk--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/