worker_cpu_affinity

Cliff Wells cliff at develix.com
Sat Dec 22 00:27:59 MSK 2007


On Sat, 2007-12-22 at 01:57 +0800, 焦胜强 wrote:
> I'm running a INTEL 5110*2 platform,RHEL4U4 for EM64T,Nginx 0.5.31
> the nginx.conf:
> worker_processes  4;
> worker_cpu_affinity 0001 0010 0100 1000;
> 
> I see in my error log the following:
> 2007/12/22 01:48:33 [alert] 15442#0: sched_setaffinity(0x00000002)
> failed (22: Invalid argument)
> 2007/12/22 01:48:33 [alert] 15443#0: sched_setaffinity(0x00000004)
> failed (22: Invalid argument)
> 2007/12/22 01:48:33 [alert] 15441#0: sched_setaffinity(0x00000001)
> failed (22: Invalid argument) 
> 2007/12/22 01:48:33 [alert] 15444#0: sched_setaffinity(0x00000008)
> failed (22: Invalid argument)
> 
This is a known issue that's going to be addressed in future release.

Quoting Igor:

"I will return to sched_setaffinity after cache will be done.
Current sched_setaffinity() processing needs to be rewritten:
1) it does not support RedHat sched_setaffinity() interface,
2) it should use CPU_SET()/etc interface for other Linuxes."

Regards,
Cliff






More information about the nginx mailing list