|Age||Commit message (Collapse)||Author||Files||Lines|
smp_affinity holds bitmask and smp_affinity_list holds list. So we
should write a list to smp_affinity_list, instead of smp_affinity.
Signed-off-by: Hu Tao <email@example.com>
Acked-by: Rob Landley <firstname.lastname@example.org>
Signed-off-by: Jiri Kosina <email@example.com>
Manually adjusting the smp_affinity for IRQ's becomes unwieldy when the
cpu count is large.
Setting smp affinity to cpus 256 to 263 would be:
echo 000000ff,00000000,00000000,00000000,00000000,00000000,00000000,00000000 > smp_affinity
echo 256-263 > smp_affinity_list
Think about what it looks like for cpus around say, 4088 to 4095.
We already have many alternate "list" interfaces:
Add a companion interface, smp_affinity_list to use cpu lists instead of
cpu maps. This conforms to other companion interfaces where both a map
and a list interface exists.
This required adding a bitmap_parselist_user() function in a manner
similar to the bitmap_parse_user() function.
[firstname.lastname@example.org: make __bitmap_parselist() static]
Signed-off-by: Mike Travis <email@example.com>
Cc: Thomas Gleixner <firstname.lastname@example.org>
Cc: Jack Steiner <email@example.com>
Cc: Lee Schermerhorn <firstname.lastname@example.org>
Cc: Andy Shevchenko <email@example.com>
Signed-off-by: Andrew Morton <firstname.lastname@example.org>
Signed-off-by: Linus Torvalds <email@example.com>
Current IRQ affinity interface does not provide a way to set affinity
for the IRQs that will be allocated/activated in the future.
This patch creates /proc/irq/default_smp_affinity that lets users set
default affinity mask for the newly allocated IRQs. Changing the default
does not affect affinity masks for the currently active IRQs, they
have to be changed explicitly.
Updated based on Paul J's comments and added some more documentation.
Signed-off-by: Max Krasnyansky <firstname.lastname@example.org>
Signed-off-by: Thomas Gleixner <email@example.com>
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.
Let it rip!