--pgp-sign-Multipart_Tue_Oct__4_21:54:52_2005-1
Content-Type: text/plain; charset=US-ASCII

>>>>> "s" == segv  <segv@netctl.net> writes:

     s> it can't even schedule multiple threads within the
     s> same process onto different CPUs.

well, for sparc64 that's still academic but...is that really true?
I'm surprised because I thought this was exactly the whole point of
scheduler activations: to move just enough context switching into the
kernel to keep all CPUs busy, and do the rest in user space where it's
faster.  Otherwise it may as well just be pth?

pthread(3)

ENVIRONMENT
     PTHREAD_CONCURRENCY      The number of concurrent threads to be run.
                              This value should at least be 1, and smaller
                              than or equal to the number of CPUs.

Next you will tell me that if one thread gets stalled waiting for
pagein/out, all the other threads stall too ha ha.

--pgp-sign-Multipart_Tue_Oct__4_21:54:52_2005-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQCVAwUAQ0MybInCBbTaW/4dAQLbtgP+P1LvRSBbDSUdow7m202mp7S4/KLtw7ib
qoOTvpmLW0TppXgEFD+H2c7YSV06qXOQM73+0imqBakloCXBIQKvWD76SKm72/42
cU0wEpQPETOasjADFxe0/xyPdjmEjnfZZ/16QoVIBXdjGo1qu/vdQzNqD6535EDy
7PNB3+ABYzc=
=AZEy
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Tue_Oct__4_21:54:52_2005-1--