RE: Bug in calcru in he 6.2 and 6.3 kernels

2008-07-20 Thread Murty, Ravi
Has anyone identified the issue(s) that might be broken in the ULE scheduler in 6.2? I am running a rather simple test - creates 8 threads and runs it on an 8 CPU system (not a whole lot running on the system). When I run it with ULE, it runs slow, very slow sometimes - it's almost like the

Re: Bug in calcru in he 6.2 and 6.3 kernels

2008-07-20 Thread Jeremy Chadwick
On Sun, Jul 20, 2008 at 06:51:22AM -0700, Murty, Ravi wrote: Has anyone identified the issue(s) that might be broken in the ULE scheduler in 6.2? I am running a rather simple test - creates 8 threads and runs it on an 8 CPU system (not a whole lot running on the system). When I run it with

RE: Bug in calcru in he 6.2 and 6.3 kernels

2008-07-20 Thread Murty, Ravi
Jeremy, thanks. I look forward to switching to ULE in 7.0 and realize that it is a completely new scheduler (I spent some time yesterday looking at it) -- which is my porting effort is much harder than a simple cut and paste. I just wanted to find out if there was something simple I could look at

Re: Bug in calcru in he 6.2 and 6.3 kernels

2008-07-20 Thread Kris Kennaway
Murty, Ravi wrote: Jeremy, thanks. I look forward to switching to ULE in 7.0 and realize that it is a completely new scheduler (I spent some time yesterday looking at it) -- which is my porting effort is much harder than a simple cut and paste. I just wanted to find out if there was something

Re: Bug in calcru in he 6.2 and 6.3 kernels

2008-07-20 Thread Garrett Cooper
On Sun, Jul 20, 2008 at 7:13 AM, Kris Kennaway [EMAIL PROTECTED] wrote: Murty, Ravi wrote: Jeremy, thanks. I look forward to switching to ULE in 7.0 and realize that it is a completely new scheduler (I spent some time yesterday looking at it) -- which is my porting effort is much harder than

Re: Bug in calcru in he 6.2 and 6.3 kernels

2008-07-07 Thread Kris Kennaway
Murty, Ravi wrote: Hello everyone, Finally found what my last problem was. We were running top in a loop and running some workloads that called sched_bind() to bind threads to specific CPUs. The problem was that (and I am using ULE) sched_bind calls a function to notify another CPU of a

Re: Bug in calcru in he 6.2 and 6.3 kernels

2008-07-07 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kris Kennaway wrote: | Murty, Ravi wrote: | Hello everyone, | | | | Finally found what my last problem was. We were running top in a loop | and running some workloads that called sched_bind() to bind threads to | specific CPUs. The problem was that

Re: Bug in calcru in he 6.2 and 6.3 kernels

2008-07-07 Thread Kris Kennaway
Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kris Kennaway wrote: | Murty, Ravi wrote: | Hello everyone, | | | | Finally found what my last problem was. We were running top in a loop | and running some workloads that called sched_bind() to bind threads to | specific CPUs. The