Messages in this thread | ![/](/images/icornerl.gif) | | Date | Mon, 05 May 2003 14:49:15 -0400 | From | Timothy Miller <> | Subject | Re: will be able to load new kernel without restarting? |
| |
Valdis.Kletnieks@vt.edu wrote: but I don't see any easy way > to implement rmmmod/insmod semantics for things like kernel/schedule.c (how > would you get your next timeslice?).
This isn't such a silly idea, really.
How much code would be required for a default, completely brainless scheduler? That's built-in. When you load a new scheduler, the default one doesn't get kicked out; it just gets turned off. When you unload, the default takes over.
The only major issue is that the data structures used to manage processes would be different from one scheduler to the next. One possible answer would be to have an unloading driver translate all of its process information into the default scheduler's format. A newly loaded one would translate it to its own format. Things that would be lost in the translation include interactivity information, etc.
Please forgive my total ignorance about how processes are represented in data structures in the linux kernel.
- 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/
| ![\](/images/icornerr.gif) |