From owner-freebsd-smp Fri Nov 5 0:47:31 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 7055414FA2 for ; Fri, 5 Nov 1999 00:47:29 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id CAA44798; Fri, 5 Nov 1999 02:47:07 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Fri, 5 Nov 1999 02:47:07 -0600 (CST) From: David Scheidt To: Joachim Strombergson Cc: freebsd-smp Subject: Re: Affinity In-Reply-To: <38228A90.B00F2E8C@emw.ericsson.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 5 Nov 1999, 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. More or less right. Processor affinity needn't be implmented such that a process only runs on a certain CPU, it can also just make it more likely that it runs on that CPU. How much of a win it is depends on a number of factors, like what the job is, how big its primary data and code sets are, and the cache coherency model of the machine is. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message