[Home] [Groups] - Message: [Prev in Group] [Next in Group]
12159: [MUD-Dev] Two threads forced to one CPU? (was: Collecting ideas for a MUD server...)
[Full Header] [Plain Text]
From: "Wesley W. Terpstra" <terpstra@iota.dhs.org>
Newsgroups: nu.kanga.list.mud-dev
Date: Thu, 23 Dec 1999 01:40:44 -0800 (PST)
References: [1]
Organization: Kanga.Nu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 22 Dec 1999 21:54:37, Rahul Sinha <rsinha@glue.umd.edu> wrote:
> hear hear! keep in mind, multiple threads ought not seperate themselves on
> seperate cpus due to cache coherency issues (depends on your OS if they
> do) and either way, the only reason to have threads is to eliminate wait
> for blocking operations.
What?! You're saying if I spawn two threads and having both work nonstop
the OS won't put them on different CPUs?
I thought this was the whole point to multi-threading?
Please explain.
- ---
E-mail: terpstra@interchange.ubc.ca Host: iota.dhs.org
PGP key: hkp://wwwkeys.us.pgp.net/terpstra@interchange.ubc.ca
http://www.iota.dhs.org/pgp-keys/terpstra.pgp
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Comment: Made with pgp4pine 1.71b
Charset: noconv
iQA/AwUBOGHuH6Yi3MeZ5h2mEQJp6gCg+KKWJYHUJQOjG4xzQf4FbuZWMRAAoI+q
+R5yt/P1rR4JJL22kRWyQM6a
=pfEm
-----END PGP SIGNATURE-----
_______________________________________________
MUD-Dev maillist - MUD-Dev@kanga.nu
http://www.kanga.nu/lists/listinfo/mud-dev