On Tue, Aug 12, 2003 at 08:25:38AM +1000, Andy Farkas wrote:
> On Mon, 11 Aug 2003, Eriq Lamar wrote:
>
> > Is there any advantage in 5.1 over 4.8 for two amd mp's. and if so could
> > someone tell what they are. I am interested in building dual system using
> > mp's but not sure which version wou
PROTECTED] On Behalf Of Steve Kargl
> Sent: Monday, August 11, 2003 7:10 PM
> To: Andy Farkas
> Cc: [EMAIL PROTECTED]; Eriq Lamar
> Subject: Re: smp in 5.1
>
>
> On Tue, Aug 12, 2003 at 08:25:38AM +1000, Andy Farkas wrote:
> > On Mon, 11 Aug 2003, Eriq Lamar wrote:
&g
.
;-)
Evan Dower
From: Andre Guibert de Bruet <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: RE: smp in 5.1
Date: Mon, 11 Aug 2003 22:40:21 -0400 (EDT)
I guess I'll chime in as well... I have a Dual Athlon 2000+ MP here and
it's running like a charm with SCHED_4BSD.
Andy
> An
On Tue, Aug 12, 2003 at 08:25:38AM +1000, Andy Farkas wrote:
> On Mon, 11 Aug 2003, Eriq Lamar wrote:
>
> > Is there any advantage in 5.1 over 4.8 for two amd mp's. and if so could
> > someone tell what they are. I am interested in building dual system using
> > mp's but not sure which version wou
At 6:16 PM -0400 8/11/03, Eriq Lamar wrote:
Is there any advantage in 5.1 over 4.8 for two amd mp's. and
if so could someone tell what they are. I am interested in
building dual system using mp's but not sure which version
would be better.
I run 5.x on a dual-Althon 2000 machine. I have no idea if
On Mon, 11 Aug 2003, Eriq Lamar wrote:
> Is there any advantage in 5.1 over 4.8 for two amd mp's. and if so could
> someone tell what they are. I am interested in building dual system using
> mp's but not sure which version would be better.
Scheduling in 5.1 is broken (sched_ule doesn't even work
nt: Monday, August 11, 2003 7:10 PM
To: Andy Farkas
Cc: [EMAIL PROTECTED]; Eriq Lamar
Subject: Re: smp in 5.1
On Tue, Aug 12, 2003 at 08:25:38AM +1000, Andy Farkas wrote:
> On Mon, 11 Aug 2003, Eriq Lamar wrote:
>
> > Is there any advantage in 5.1 over 4.8 for two amd mp's. and if so
On Thu, 12 Jun 2003, Killing wrote:
> > Halting them will still cause the CPUs to be detected. They just won't do
> > any useful work.
>
> Yep but the issue is that all the core admin tools are unaware of this and
> hence include the virtual cores in idle calcs etc making load monitoring
> impossi
Original Message -
From: "John-Mark Gurney" <[EMAIL PROTECTED]>
> > Yes 5.X is still new tech and may not run on all machines but on the ones
> > which it does ( and it runs very well here ) basic tools are required. If
> > it doesn't run on a machine your under know false impressions, if
Killing wrote this message on Thu, Jun 12, 2003 at 18:47 +0100:
> I suppose the hurry is that basic utils that we use day to day like top
> and vmstat to monitor machine load cannot be trusted to give accurate
> info.
Actually, the basic tools ARE correct, there is a cpu sitting idle that
the sysa
> Well, hyperthreading can be disabled via a kernel directive, right?
>From what I've seen that was removed between 5.0 and 5.1 correct
me if Im wrong.
> > Which ever it needs someone to pick it up ASAP dont you think?
>
> Really? What's the hurry? FreeBSD 5.x isn't even bootable/installa
On Thu, 12 Jun 2003, Killing wrote:
> - Original Message -
> From: "Doug White" <[EMAIL PROTECTED]>
> > > sysctl machdep.hlt_logical_cpus:
> > > machdep.hlt_logical_cpus: 1
> >
> > Halting them will still cause the CPUs to be detected. They just won't do
> > any useful work.
>
> Yep bu
- Original Message -
From: "Doug White" <[EMAIL PROTECTED]>
> > sysctl machdep.hlt_logical_cpus:
> > machdep.hlt_logical_cpus: 1
>
> Halting them will still cause the CPUs to be detected. They just won't do
> any useful work.
Yep but the issue is that all the core admin tools are unaware
On Wed, 11 Jun 2003, Steven Hartland wrote:
> sysctl machdep.hlt_logical_cpus:
> machdep.hlt_logical_cpus: 1
Halting them will still cause the CPUs to be detected. They just won't do
any useful work.
> Relevant sections from dmesg:
> Programming 24 pins in IOAPIC #0
> IOAPIC #0 intpin 2 -> irq 0
14 matches
Mail list logo