i must add that linux 2.4 implements processor affinity na. so i guess if you have a typical, non-cpu-bound process with threads, the threads will stay on one CPU. in general highly cpu-bound processes are poor candidates for threading anyway.. threads are more suited for i/o bound processes (e.g. worker threads waiting on a resource). as an aside, 2.4 kernel also supports wake-one functionality (as introduced in windows nt). so its a good i/o platform na (c.f. the tux webserver, fastest in the world as of now). contrast this with the dismal performance of linux in the mindcraft survey -- most of that was blamed on the thundering-herd implementation of wake-on-select in the 2.0/2.2 kernel. as i said, windows nt has a lot of good concepts (also: completion ports). btu the implementation somehow got screwed... -- --------------------------------------------------------------------- Orlando Andico <[EMAIL PROTECTED]> POTS Phone: +63 (2) 937-2293 Mosaic Communications, Inc. GSM Mobile: +63 (917) 531-5893 I'm not suffering from insanity -- I'm enjoying every minute of it!! _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
