Linux never really had proper memory management.
As in, the program interface makes each program look like it is running in their own machine with all the memory.

However, not all pages are created equal. There are pages that really should never be moved to swap.

My solution, if ever i get the machinery, is to create a linux processor.
Or, basically, design a microprocessor that would work seamlessly with linux kernels.

In doing so, it would probably be very easy to make this same microprocessor run I/O for the USB/UART, or the disk drives (like the Amiga).

Then, you have this processor that runs the linux kernel, and only the kernel so it never leaves the runtime. It is always instantly available, and can more actively monitor other processes based on usage, while those processes are running.

Further, if i do this right, i can make many processor machines. If these processors can handle actual loads... which is hard to tell, because Mozilla needs a lot of resources... can it run on multiple RISC processors simultaneously, or we still need a large main processor?

But, if the multi-processors works, than i would like to array them like chip on glass, or chips on wafers. Make the individual processors able to be made by less than cutting edge wafer etching machines. And then ganging them up in post production. This also may work out better for heat.