From owner-freebsd-smp Fri Nov 5 4: 7:30 1999 Delivered-To: freebsd-smp@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 5653414CC2 for ; Fri, 5 Nov 1999 04:07:22 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B42C61C03; Fri, 5 Nov 1999 20:06:24 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Joachim Strombergson Cc: freebsd-smp Subject: Re: Affinity In-reply-to: Your message of "Fri, 05 Nov 1999 08:43:12 +0100." <38228A90.B00F2E8C@emw.ericsson.se> Content-Transfer-Encoding: 8bit Date: Fri, 05 Nov 1999 20:06:24 +0800 From: Peter Wemm Message-Id: <19991105120624.B42C61C03@overcee.netplex.com.au> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joachim Strombergson wrote: > Hi! > > I've missed the message boats a few times so... Could anyone explain the > affinity thing again. If I understood it correctly, it's used to lock a > process to a certain CPU. > > When running say a SETI@Home and some other apps at the same time, and > then check top, I see a behaviour for the SETI process where the status > goes something like: CPU0->RUN->CPU1->RUN->CPU0.... Does that mean that > the process is bouncing back and forth between the CPUs? > > Any help and explanations would be very much appreciated. > > BTW: I'm running a Dual Celeron on ABIT BP6 machine with FreeBSD 3.3 > STABLE. 4.0 has some simple affinity tweaks that should help with this type of problem. It seems to help with rc564. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message