Messages in this thread | | | Date | Sun, 15 Jul 2001 13:51:10 -0700 (PDT) | From | Davide Libenzi <> | Subject | Re: [Lse-tech] Re: CPU affinity & IPI latency |
| |
On 13-Jul-2001 Shailabh Nagar wrote: > That is true to an extent. It would be convenient for us as scheduler > rewriters to have neatly differentiated classes like UP, SMP, BIG_SMP, NUMA > etc. But it forces all other scheduler-sensitive code to think of each of > these cases separately and is exactly the reason why #ifdef's are > discouraged for critical kernel code like the scheduler.
Personally I hate #ifdef's inside the code more than my cat water, but something like :
[sched.c] #ifdef CONFIG_SCHED_XXX #include "sched_xxx.c" #else #ifdef CONFIG_SCHED_YYY #include "sched_yyy.c"
...
#endif
looks pretty clean to me.
- Davide
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |