From: Sebastian Poehn <sebastian.poehn@gmail.com>
To: netdev@vger.kernel.org
Subject: [PATCH] Documentation: Mention chunk format for irq affinity
Date: Wed, 22 Jul 2015 10:09:36 +0200 [thread overview]
Message-ID: <1437552576.2783.19.camel@googlemail.com> (raw)
It may not be obvious for everyone that bitmasks in proc require
32bit chunking
Signed-off-by: Sebastian Poehn <sebastian.poehn@gmail.com>
---
Documentation/IRQ-affinity.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/IRQ-affinity.txt b/Documentation/IRQ-affinity.txt
index 01a6751..d873dab 100644
--- a/Documentation/IRQ-affinity.txt
+++ b/Documentation/IRQ-affinity.txt
@@ -55,6 +55,11 @@ round-trip min/avg/max = 0.1/0.5/585.4 ms
This time around IRQ44 was delivered only to the last four processors.
i.e counters for the CPU0-3 did not change.
+Note that you have to split the bitmask to chunks when using more that 32 cpus:
+[root@moon 44]# echo 80,00000000 > smp_affinity
+[root@moon 44]# cat smp_affinity
+80,00000000
+
Here is an example of limiting that same irq (44) to cpus 1024 to 1031:
[root@moon 44]# echo 1024-1031 > smp_affinity_list
--
2.4.3
reply other threads:[~2015-07-22 8:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1437552576.2783.19.camel@googlemail.com \
--to=sebastian.poehn@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).