Hi folks. I've been using Linux since 2000 and supporting it with Red
Hat since 2007 and now I'm a Red Hat Quality Assurance Engineer.
At Red Hat we use the 'make check' build target to test hwloc. I did a
review of what that target tests and what it doesn't and this is what I
found.
Did I miss a
Le 06/11/2012 21:48, John Brier a écrit :
> Hi folks. I've been using Linux since 2000 and supporting it with Red
> Hat since 2007 and now I'm a Red Hat Quality Assurance Engineer.
>
> At Red Hat we use the 'make check' build target to test hwloc. I did a
> review of what that target tests and what
I noticed on my system (Fedora 17) that the OS Devices don't have their own
cpuset. It seems like it would be good to know the affinity of the interrupt
assigned to the device. Is there a provision for this in hwloc, or would I
need to find it another way?
thanks,
--Guy
Hello Guy,
I don't think OS devices ever had a cpuset. All objects that are not
things where you can bind processes usually have NULL cpusets. So when
you have a PCI or OS device, you walk up the obj->parent pointer until
you find an object with a non-NULL cpuset. That's the affinity you're
lookin
On 11/06/2012 03:53 PM, Brice Goglin wrote:
> Hello Guy,
>
> I don't think OS devices ever had a cpuset. All objects that are not
> things where you can bind processes usually have NULL cpusets. So when
> you have a PCI or OS device, you walk up the obj->parent pointer until
> you find an object w
Le 06/11/2012 23:55, Guy Streeter a écrit :
> On 11/06/2012 03:53 PM, Brice Goglin wrote:
>> Hello Guy,
>>
>> I don't think OS devices ever had a cpuset. All objects that are not
>> things where you can bind processes usually have NULL cpusets. So when
>> you have a PCI or OS device, you walk up th
Guy Streeter, le Tue 06 Nov 2012 23:56:29 +0100, a écrit :
> My question is how do I specify a binding like "not on the same CPU
> that is handling the Ethernet interrupts"?
About interrupts, that's unfortunately actually not related with actual
topology of the machine, Linux is free to direct the
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.6a1r5006
Start time: Tue Nov 6 21:01:02 EST 2012
End time: Tue Nov 6 21:04:55 EST 2012
Your friendly daemon,
Cyrador
