Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Oct 2006 12:38:15 -0500
From:      Astrodog <astrodog@gmail.com>
To:        "David Xu" <davidxu@freebsd.org>
Cc:        rondzierwa@comcast.net, freebsd-amd64@freebsd.org
Subject:   Re: Hardware topology
Message-ID:  <2fd864e0610251038h46042de8u3712170010b48228@mail.gmail.com>
In-Reply-To: <200610252013.38119.davidxu@freebsd.org>
References:  <102420062150.6756.453E8A9D000980D700001A6422007613940E999D0A07960B02019D@comcast.net> <200610252013.38119.davidxu@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/25/06, David Xu <davidxu@freebsd.org> wrote:
> On Wednesday 25 October 2006 05:50, rondzierwa@comcast.net wrote:
> > 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?
> >
> > thanks,
> > ron.
>
> There is no unique hardware topology structure in kernel,  but scheduler
> has some APIs can bind thread to a specific CPU, though there is no any
> syscall can let you do it.
>

I'm working on tying this into memory location. Currently slogging
through the VM side of things. I'm expecting some usable patches to
come out in the next month or so.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2fd864e0610251038h46042de8u3712170010b48228>