Worker_cpu_affinity

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)

On Sat, Dec 22, 2007 at 01:57:20AM +0800, ??? wrote:

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)

Now worker_cpu_affinity is broken.

On Sat, 2007-12-22 at 01:57 +0800, 焦胜强 wrote:

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

On Sam 22.12.2007 01:57, ??? wrote:

I’m running a INTEL 5110*2 platform,RHEL4U4 for EM64T,Nginx 0.5.31

Please look at:

http://article.gmane.org/gmane.comp.web.nginx.english/2418/match=worker_cpu_affinity

Cheers

Aleks

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs