Re: mp only sched functions

2013-04-17 Thread Ted Unangst
On Wed, Apr 17, 2013 at 15:39, Ted Unangst wrote: > Some functions dealing with pegging procs to CPUs and migration costs > are only meaningful if we are running a multiprocessor kernel. Leave > dummy versions in to avoid ifdef mazes elsewhere. Here's a variant that covers a bit more code, by stub

Re: mp only sched functions

2013-04-17 Thread Ted Unangst
On Wed, Apr 17, 2013 at 13:41, Theo de Raadt wrote: > Please #ifdef the bodies of the functions, rather than adding wrappers > afterwards. The problem is sched_proc_to_cpu_cost has a bunch of globals outside it, so excluding them would add several more ifdef/endif sections. Doable, I just didn't l

Re: mp only sched functions

2013-04-17 Thread Theo de Raadt
Please #ifdef the bodies of the functions, rather than adding wrappers afterwards. > Some functions dealing with pegging procs to CPUs and migration costs > are only meaningful if we are running a multiprocessor kernel. Leave > dummy versions in to avoid ifdef mazes elsewhere. > > Index: kern_sch

mp only sched functions

2013-04-17 Thread Ted Unangst
Some functions dealing with pegging procs to CPUs and migration costs are only meaningful if we are running a multiprocessor kernel. Leave dummy versions in to avoid ifdef mazes elsewhere. Index: kern_sched.c === RCS file: /cvs/src/sy