Re: Linux compatible setaffinity.

On Dec 23, 2007 5:44 PM, David Xu <davidxu@xxxxxxxxxxx> wrote:

Robert Watson wrote:
On Fri, 21 Dec 2007, David Xu wrote:

I don't say no to these interfaces, but there is a need to tell user
which cpus are sharing cache, or memory distance is closest enough,
and which cpus are servicing interrupts, e.g, network interrupt and
disks etc, etc, otherwise, blindly setting cpu affinity mask only can
shoot itself in the foot.

While the Mac OS X API is pretty Mach-specific, it's worth taking a look
at their recently-announced affinity API:

http://developer.apple.com/releasenotes/Performance/RN-AffinityAPI/index.html


Robert N M Watson
Computer Laboratory
University of Cambridge



I like the interfaces, it is more flexible.

I agree. May I as k what's being planned? It's Jeffs' call finally I think.

Brian.
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Linux compatible setaffinity.
    ... Robert Watson wrote: ... which cpus are sharing cache, or memory distance is closest enough, and which cpus are servicing interrupts, e.g, network interrupt and disks etc, etc, otherwise, blindly setting cpu affinity mask only can shoot itself in the foot. ...
    (freebsd-arch)
  • Re: Linux compatible setaffinity.
    ... which cpus are sharing cache, or memory distance is closest enough, ... interface is a hard cpu binding interface, it is still needed in some circumstance. ... I have plans to make ULE even smarter in this regard so that the application developers would almost never need to hint it. ...
    (freebsd-arch)
  • Re: The machdep.hyperthreading_allowed & ULE weirdness in 7.1
    ... On Mon, 23 Feb 2009, Robert Watson wrote: ... CPUs for workload distribution, callout threads and sched_bind/sched_pinfor crypto load distribution, etc, you need a whole infrastructure for software-disabled CPUs. ... Changing the architecture of the kernel to disable CPU cores after boot is a significant investment of work, ...
    (freebsd-current)
  • Re: The machdep.hyperthreading_allowed & ULE weirdness in 7.1
    ... On Mon, 23 Feb 2009, Robert Watson wrote: ... CPUs for workload distribution, callout threads and sched_bind/sched_pinfor crypto load distribution, etc, you need a whole infrastructure for software-disabled CPUs. ... Changing the architecture of the kernel to disable CPU cores after boot is a significant investment of work, ...
    (freebsd-stable)
  • Re: Linux compatible setaffinity.
    ... which cpus are sharing cache, or memory distance is closest enough, ... disks etc, etc, otherwise, blindly setting cpu affinity mask only can ... interface is a hard cpu binding interface, it is still needed in some circumstance. ...
    (freebsd-arch)