> I have to admit, I like the idea of being able to swap out some code and
> data. In particular, I have in mind my configuration manager stuff, much
> of which remains pretty idle once the system has gone past it's
> initialisation stage. Some, however, needs to remain in real memory
> because, at the very least, it interacts directly with the interrupt
> handling stuff.
Some candidates I can think of for being swappable:
- PnP code (especially if we get full blown ISA PnP)
- legacy PCI cruft
- fib (suggested by Alan Cox)
- math emulation
- bits of some drivers (have to be very careful here)
- networking protocols with no active sockets
- filesystems which aren't presently in use
The latter three being swapable only at certain times (don't swap anything
that might be required to swap back in), so I'm not sure if that would be
feasible.
The math emulation code could perhaps go in its own section, and if its not
require, free those pages early on. Or is this getting to messy?
-cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html