Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Hardware Locality Development mailing list

Subject: Re: [hwloc-devel] non-PCI OS devices?
From: Brice Goglin (Brice.Goglin_at_[hidden])
Date: 2012-10-15 15:59:19

Le 15/10/2012 21:52, Guy Streeter a écrit :
> When I'm trying to visualize how my system is physically configured, in order
> to decide how best to bind applications, I'd like to know about every source
> of interrupts. keyboard and mouse, timers, sound, USB-connected devices, etc.
> Has any though been given to expanding the OS device information to include them?

There's a ticket about about USB device information, but it's far away
on my TODO-list because USB is low performance, so affinity shouldn't
matter much. That said, interrupts could indeed be a good reason to look
at USB and other non-PCI devices. But my understanding is that
interrupts are not guaranteed to be delivered to CPUs near the device.
Drivers (and daemons such as irqbalance) should be allowed to bind
interrupt as they want (even if it's a bad idea). So maybe we should
look at interrupts directly instead of going through USB devices?