From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Re: [RFC][PATCH 1/2] rework shadow CPU affinity
Date: Tue, 28 Nov 2006 21:10:33 +0100 [thread overview]
Message-ID: <456C97B9.1000402@domain.hid> (raw)
In-Reply-To: <456C8961.7060906@domain.hid>
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Picking up the earlier discussion of CPU affinity of shadow threads,
>> this patch now opens the possibility to assign a CPU mask on
>> xnshadow_map. It cleans up the related nucleus code and updates all
>> callers of xnshadow_map appropriately.
>>
>> Be warned, it's only tested on (q)emulated SMP. Comments and test
>> reports on real hardware are welcome.
>
> It is only possible to set the affinity of a user-space thread, why
> adding another way to do it ?
>
I'm not yet completely understanding what you mean.
So far the affinity was indirectly assigned to some xnthread by the CPU
the caller of xnshadow_map happened to run on. Now this is done
explicitly, thus in a more robust way (there was an undefined path in
the old code) and without duplicating code (/wrt skins).
Jan
next prev parent reply other threads:[~2006-11-28 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 13:51 [Xenomai-core] [RFC][PATCH 1/2] rework shadow CPU affinity Jan Kiszka
2006-11-28 19:09 ` [Xenomai-core] " Gilles Chanteperdrix
2006-11-28 20:10 ` Jan Kiszka [this message]
2006-11-29 9:01 ` Gilles Chanteperdrix
2006-11-29 9:11 ` Jan Kiszka
2006-11-29 9:32 ` Gilles Chanteperdrix
2006-11-29 9:52 ` Jan Kiszka
2006-11-29 10:28 ` Jan Kiszka
2006-11-29 10:54 ` Gilles Chanteperdrix
2006-11-29 18:38 ` Philippe Gerum
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=456C97B9.1000402@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--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.