Date: Fri, 17 Mar 2000 14:24:54 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: "Brent York" <york@mediarack.com>, <freebsd-smp@FreeBSD.ORG> Subject: Re: *sigh* Message-ID: <v0421010fb4f80fc6e8d3@[128.113.24.47]> In-Reply-To: <000701bf8f9f$2b2859e0$5c5aca83@csd.unb.ca.acscience.com> References: <000701bf8f9f$2b2859e0$5c5aca83@csd.unb.ca.acscience.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 7:27 PM -0400 3/16/00, Brent York wrote: >I'm quite sure I have the kernel options configured correctly, >which is why Im so confused about this. > >So, without further ado, I ask a simple question, does FreeBSD 4.0-R >fix this problem? Or is there some way I can fix it with 3.3-R such >that the SMP is working properly and or most efficiently, and allowing >threads to span CPU's and execute concurrently, and likewise with >processes? Just as a data point, I have run dual-processor systems on both 3.0-beta (pre-release) and 3.2-release. On both, I definitely see "CPU0" and "CPU1" show up as state's in 'top -SI' on the same screen-update (and sometimes a few more processes in READY...). Those are separate processes, not separate threads in one process. If you don't see multiple processors active while you're running multiple cpu-bound processes, then I doubt an upgrade to 4.0 will whatever problem you're seeing with 3.3-release... (unless maybe you do have some config wrong and you happen to correct that while installing the new release). What do you get for output from: dmesg | grep -i cpu If you're trying to run multiple threads in a single process, well, other messages have already given the details of the current status of threads. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v0421010fb4f80fc6e8d3>