On Sun, 6 May 2001, Chris Wedgwood wrote:
> On Sat, May 05, 2001 at 11:19:09PM -0300, Rik van Riel wrote:
>
> This only leaves two issues, the first is device drivers and the
> second is the question whether we'd want the overhead needed to
> implement the (fairly easy) memory relocation.
>
> How do you relocate
>
> -- pages which are mlocked without violating RT contraints?
Fuck RT constraints. Linux doesn't have infinitely small
scheduling latencies, it's easy to copy a page without
increasing the scheduling latencies much.
> -- pages which contain kernel pointers and might be accessed from
> interrupt context?
Block interrupts while copying a kernel page?
Remember that this is an emergency situation, so it's ok
to use "big hammer" solutions.
regards,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/ http://distro.conectiva.com/
Send all your spam to [EMAIL PROTECTED] (spam digging piggy)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
