From: Jan Kiszka <jan.kiszka@domain.hid>
To: "M. Koehrer" <mathias_koehrer@domain.hid>
Cc: xenomai@xenomai.org
Subject: [Xenomai-core] Re: [RFC][PATCH 2/2] global CPU affinity control
Date: Wed, 29 Nov 2006 09:24:53 +0100 [thread overview]
Message-ID: <456D43D5.7060905@domain.hid> (raw)
In-Reply-To: <26126961.1164785592715.JavaMail.ngmail@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
M. Koehrer wrote:
> Hi Jan,
>
> thanks for the patch!
> This looks fine to me. This allows me easily to set the affinity of the xenomai tasks.
>
> As far as I understood, I have to specify XNPOD_ALL_CPUS as parameter
> at rt_task_create() to use this feature.
...or an empty mask, both works.
> What about the rtnet internal (kernel) task (created via RTDM)?
> Will it use this affinity as well or do I have to "force" rtnet somehow to use the
> "global" xenomai affinity?
Yes, it affects any Xenomai thread that doesn't specify an explicit
mask. And it forces all IRQs that are newly attached to the specified
affinity. You should be able to watch this under
/proc/irq/<n>/smp_affinity. That avoids e.g. that the NIC IRQ pops up on
CPU 0 but has to wake up the stack manager on CPU 1.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2006-11-29 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 13:51 [Xenomai-core] [RFC][PATCH 2/2] global CPU affinity control Jan Kiszka
2006-11-28 19:05 ` [Xenomai-core] " Gilles Chanteperdrix
2006-11-28 20:12 ` Jan Kiszka
2006-11-29 10:20 ` Gilles Chanteperdrix
2006-11-29 10:31 ` Jan Kiszka
[not found] ` <26126961.1164785592715.JavaMail.ngmail@domain.hid>
2006-11-29 8:24 ` Jan Kiszka [this message]
2006-11-29 12:48 ` [Xenomai-core] " Jan Kiszka
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=456D43D5.7060905@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=mathias_koehrer@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.