From owner-freebsd-amd64@FreeBSD.ORG Wed Oct 25 07:57:37 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11CD416A407 for ; Wed, 25 Oct 2006 07:57:37 +0000 (UTC) (envelope-from amon@sockar.homeip.net) Received: from mallaury.nerim.net (smtp-103-wednesday.noc.nerim.net [62.4.17.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97BF243D5D for ; Wed, 25 Oct 2006 07:57:35 +0000 (GMT) (envelope-from amon@sockar.homeip.net) Received: from sockar.homeip.net (tourist.net8.nerim.net [213.41.176.3]) by mallaury.nerim.net (Postfix) with ESMTP id F26AA4F3CF; Wed, 25 Oct 2006 09:57:28 +0200 (CEST) Received: from ra.aabs (localhost [127.0.0.1]) by sockar.homeip.net (8.13.4/8.13.4) with ESMTP id k9P7sQqx043657; Wed, 25 Oct 2006 09:54:26 +0200 (CEST) (envelope-from amon@ra.aabs) Received: (from amon@localhost) by ra.aabs (8.13.4/8.13.4/Submit) id k9P7sOft043656; Wed, 25 Oct 2006 09:54:24 +0200 (CEST) (envelope-from amon) Date: Wed, 25 Oct 2006 09:54:24 +0200 From: Herve Boulouis To: rondzierwa@comcast.net Message-ID: <20061025075424.GW46550@ra.aabs> References: <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Hardware topology X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2006 07:57:37 -0000 Le 24/10/2006 21:50, rondzierwa@comcast.net a écrit: > Does the amd64 kernel know anything about which memory is attached to > which processor, and which i/o bus is attached to which hypertransport link? > Can it use this information to do things like allocate pages to a process from > the memory that is physically attached to the cpu upon which the process is > running? Along these lines, is there any way to set affinity between a process > and a cpu (or set of cpu's in the case of multicore)? > > Likewise with i/o devices, if a process or device driver wants to operate a > particular device, can it be set to run on the cpu that owns the hypertransport > connection upon which the device is connected? The freebsd kernel is not NUMA aware, so it doesn't know anything of the underlying hardware topology. -- Herve Boulouis