Originally developed at the University of North Carolina, it is being used by Google to test scheduler policies. "At Google we have used Linsched as a testing tool to validate the behavior of the kernel scheduler," details Google's Ranjit Manomohan, "We could cut down our validation time from several days to a couple of hours due to the ability to run multiple tests on several different types of hardware models."
This has already led to several improvements in the kernel scheduler, thanks to the high fegree of code sharing between LinSched and the 'real' scheduler. "Due to the high degree of code sharing between LinSched and the Linux scheduler, porting LinSched code to Linux is reasonably straightforward," Manomohan explains, "LinSched may be especially useful to those who are new to Linux scheduler development."
"Since Linsched allows arbitrary hardware topologies to be modeled, it enables testing of scheduler changes on hardware that may not be easily accessible to the developer," he adds, "For example, most developers don't have access to a quad-core quad-socket box, but they can use LinSched to see how their changes affect the scheduler on such boxes."
The code is out there.