Hi,

I'm still blocked on a CPU affinity problem.
In order to adapt a set affinity function which is based on
posix linux lib :
- CPU_AssignPID(uint32 PID, uint32 CPU_id)
- the cpu affinity of the caller and all its child threads must be set to 
CPU_id.

Problems are:
Child PIDs must be listed, the only means I found is listing pids using `ls 
/proc/"Parent pid"/ > temp_file`
And each listed pid is sched_setaffinity'ed.
I don't know if setting affinity of RT threads from an other thread (parent) 
using pid works with xenomai.

So, my question is :
With xenomai, is recursively cpu affinity setting from a parent thread, a good 
way of doing ?
I read switchtest program, and I conclude that in a xenomai and RT perspective, 
it seems "nicer"
to set affinity each threads separately during their init phase before the RT 
infinite loop.
Otherwise, setting affinity after child threads creation from its parent, may 
switch them into 
secondary mode during their RT loop, and at an unknown moment.
Argumentation is important for my internship because I have to port on xenomai 
a very big RT 
posix based application. And I should justify any modifications and prevent 
potential problems.

Sorry, I don't know if it is clear.

Thanks in advance, Niry.

This e-mail is intended only for the above addressee. It may contain privileged 
information.
If you are not the addressee you must not copy, distribute, disclose or use any 
of the information in it. 
If you have received it in error please delete it and immediately notify the 
sender.
Security Notice: all e-mail, sent to or from this address, may be accessed by 
someone other than the recipient, for system management and security reasons. 
This access is controlled under Regulation of security reasons.
This access is controlled under Regulation of Investigatory Powers Act 2000, 
Lawful Business Practises.



_______________________________________________
Xenomai-help mailing list
[email protected]
https://mail.gna.org/listinfo/xenomai-help

Reply via email to