-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27/08/13 00:07, Brice Goglin wrote:
> But there's a more general problem here, some people may want > something similar for other cases. I need to think about it. Something like a sort order perhaps, combined with some method to exclude or weight PUs based on some metrics (including a user defined weight)? I had a quick poke around looking at /proc/irq/*/ and it would appear you can gather info about which CPUs are eligible to handle IRQs from the smp_affinity bitmask (or smp_affinity_list). The node file there just "shows the node to which the device using the IRQ reports itself as being attached. This hardware locality information does not include information about any possible driver locality preference." cheers, Chris - -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlIcF/QACgkQO2KABBYQAh/7oQCcDSLlgEJqBGDerUD481ho6UWc Rp0AnRC4cC/Kdhwe75tgg1O/LrcfxXM0 =r4pj -----END PGP SIGNATURE-----
