Linux compatible setaffinity.
Daniel Eischen
deischen at freebsd.org
Tue Dec 25 23:51:42 PST 2007
On Tue, 25 Dec 2007, David Xu wrote:
> Brian McGinty wrote:
>> On Dec 23, 2007 5:44 PM, David Xu <davidxu at freebsd.org> 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.
>
> I don't have plan. ;-) If I understand it correctly, it is a hint to
> scheduler, it is better describing thread relationship, while Jeff's
> interface is a hard cpu binding interface, it is still needed in some
> circumstance.
Please take a look at Solaris' API for processor set binding:
http://docs.sun.com/app/docs/doc/816-5167/6mbb2jae6?a=expand
See processor_bind, processor_info, and pset_*.
--
DE
More information about the freebsd-arch
mailing list