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
Jan Kiszka wrote:
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
Gilles Chanteperdrix wrote:
Jan Kiszka wrote:
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
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.
--
Gilles Chanteperdrix
Hello,
I did some redesigning on my first draft.
- Now we have some kind of profile in include/rti2c.h.
- I got rid of some chunks of code that were not really needed.
- Linux kernel dependencies have been removed (I hope I catched all of them)
Cheers.
--
Dirk Eibach [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Dirk Eibach wrote:
Hello,
I did some redesigning on my first draft.
- Now we have some kind of profile in include/rti2c.h.
- I got rid of some chunks of code that were not really needed.
- Linux kernel dependencies have been removed (I hope I catched all of
them)
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
Gilles Chanteperdrix wrote:
Jan Kiszka wrote:
Nope, that's intentional (forgot to repeat this fact, was explained
earlier): Users can always override nkaffinity by their own mask. Only
the I-don't-care XNPOD_ALL_CPUS activates this new selection mechanism.
Ok. But there is still something
Jan Kiszka wrote:
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
Version 5 is basically a rebase over the first patch of this series. It
also enforces that cpus_allowed of a shadow thread only contains a
single CPU.
Only compile-tested.
Jan
---
include/nucleus/pod.h|2 +
ksrc/nucleus/intr.c |3 ++
ksrc/nucleus/module.c| 57
Second try of this patch, now consequently basing the affinity API for
xnshadow_map on current-cpus_allowed (affects the native skin). Just
like the current code does, this patch restricts a shadow thread to a
single (the first) CPU of its affinity mask.
Jan
---
ksrc/nucleus/shadow.c |
Dirk Eibach wrote:
Hello,
I did some redesigning on my first draft.
- Now we have some kind of profile in include/rti2c.h.
- I got rid of some chunks of code that were not really needed.
- Linux kernel dependencies have been removed (I hope I catched all of
them)
Hmm, I would rather
On Wed, 2006-11-29 at 11:43 +0100, Jan Kiszka wrote:
Hi,
we had this topic a few times before, but it's getting more and more
urgent now: How to establish a repository for Xenomai example code?
I think we have basically two options:
A) create /examples/skin, including
On Wed, 2006-11-29 at 11:54 +0100, Gilles Chanteperdrix wrote:
Jan Kiszka wrote:
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
Philippe Gerum wrote:
On Wed, 2006-11-29 at 11:43 +0100, Jan Kiszka wrote:
Hi,
we had this topic a few times before, but it's getting more and more
urgent now: How to establish a repository for Xenomai example code?
I think we have basically two options:
A) create /examples/skin,
15 matches
Mail list logo
