Skip to contentSkip to conversation

Dynamically determine if kernel includes CFS Scheduler

DISCUSSION Darren Hart 3 participants 6 messages Mar 6, 2009 – Mar 7, 2009

lore
Share & tools
lore
#0 lore raw

I've received an internal request for a means to determine at run-time if the CFS scheduler is included in the running kernel. Looking through the git commit log and the /proc/sys/kernel filesystem, I think I see two approaches:

1) stat("/proc/sys/kernel/sched_compat_yield")
This confirms 2.6.23-rc7 kernel or later which definitely has the CFS scheduler and this functionality is of interest anyway.
2) Test if the kernel version is >= 2.6.22 which is where I believe CFS landed.

Any guesses as to how robust/future-proof approach #1 would be?

Signature · 3 lines
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
#1 lore raw
Quoted 5 lines · Darren Hart

I've received an internal request for a means to determine at run-time if the CFS scheduler is included in the running kernel. Looking through the git commit log and the /proc/sys/kernel filesystem, I think I see two approaches:

Quoted 7 lines

1) stat("/proc/sys/kernel/sched_compat_yield")
This confirms 2.6.23-rc7 kernel or later which definitely has the CFS scheduler and this functionality is of interest anyway.
2) Test if the kernel version is >= 2.6.22 which is where I believe CFS landed.

Any guesses as to how robust/future-proof approach #1 would be?

The question is why? Relying on scheduler specifics outside of whatever POSIX mandates is an application bug.

#2 lore raw
In reply to Darren Hart
Quoted 4 lines · Darren Hart

I've received an internal request for a means to determine at run-time if the CFS scheduler is included in the running kernel. Looking through the git commit log and the /proc/sys/kernel filesystem, I think I see two approaches:

Sounds dangerous (you are dependent on scheduler beahviour) but if it exists you could check /proc/config.gz (or the config file in the /boot directory)...

Signature · 1 line
Sitsofe | http://sucs.org/~sits/
#3 lore raw
Quoted 7 lines · Sitsofe Wheeler
Quoted 1 line · Darren Hart

I've received an internal request for a means to determine at run-time if the CFS scheduler is included in the running kernel. Looking through the git commit log and the /proc/sys/kernel filesystem, I think I see two approaches:

Sounds dangerous (you are dependent on scheduler beahviour) but if it exists you could check /proc/config.gz (or the config file in the /boot directory)...

So I am of course in agreement with both you and Peter. In this case, the development team of an existing product is trying to move away from heavy use of sched_yield(), and the CFS scheduler provides some motivation for that as the behavior of sched_yield() changed (again). As we know, this behavior should not be depended upon, but lots of applications do it unfortunately. So, in this case the development team would like to move to becoming less dependent on it, but unfortunately do not feel it is feasible to make the change unconditionally as it has the potential to destabilize the existing installations, etc. They would like to be able to say, use this new approach using fewer sched_yield() calls on kernels with CFS.

I understand it isn't ideal, and I have of course provided that feedback, but I would like to provide them with all the information I can.

Thanks,

Signature · 3 lines
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
#4 lore raw
Quoted 4 lines · Darren Hart

So I am of course in agreement with both you and Peter. In this case, the development team of an existing product is trying to move away from heavy use of sched_yield(), and the CFS scheduler provides some

Hmm. The only thing I'll say about checking kernel versions is: do some tests/checks with the different enterprise distro kernels. I don't think they tend to do big backports any more but if they have that kernel version check could become tricky...

Signature · 1 line
Sitsofe | http://sucs.org/~sits/
#5 lore raw
Quoted 7 lines · Sitsofe Wheeler
Quoted 1 line · Darren Hart

So I am of course in agreement with both you and Peter. In this case, the development team of an existing product is trying to move away from heavy use of sched_yield(), and the CFS scheduler provides some

Hmm. The only thing I'll say about checking kernel versions is: do some tests/checks with the different enterprise distro kernels. I don't think they tend to do big backports any more but if they have that kernel version check could become tricky...

Right, excellent point. Regardless of how thing are right now, relying on the kernel revision is a bad idea for this reason.

Signature · 3 lines
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team