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: Wed, 29 Nov 2006 11:28:39 +0100 [thread overview]
Message-ID: <456D60D7.4090202@domain.hid> (raw)
In-Reply-To: <456D5871.6040401@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> OK. So you are suggesting to read out the affinity mask from task_struct
>>> instead of passing it as an additional argument?
>>>
>> Unless I am wrong, it is the way it currently works.
>>
>
> Yes, for the posix skin. But native is different due to the spilt-up
> create/start and its own affinity API. And that caused problems when
> applying nkaffinity.
>
> Nevertheless, I should try to combine the cleanup of xnshadow_map with
> passing the mask ALWAYS in task_struct. Let's see how this works out,
> most likely with less patching.
sched_setaffinity is 2.6 only. So we would have to push the mask
application into kernel space for the native skin anyway. Hmm.
What are posix skin users supposed to do over 2.4? Upgrade to 2.6? BTW,
do you plan to support pthread_attr_setaffinity_np somehow?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-11-29 10:28 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
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 [this message]
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=456D60D7.4090202@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.