On Tue, 26 Jan 1999 15:15:04 +0100 (CET), MOLNAR Ingo
<mingo@chiara.csoma.elte.hu> said:
> this is conceptually 'boot-time allocation of big buffers' by splitting
> all available memory into two pieces:
> size_kernel: generic memory
> size_user: only swappable
which is something we already need to do if we want to support 4G
physical memory cleanly (ie. add support for anonymous and cache pages
to be mapped on demand into the kernel's VA, rather than having the
whole of physical memory virtually mapped at all times).
> the toughest part is the 'moving' stuff, which is not yet present and
> hard/impossible to implement in a clean and maintainable way.
Not at all. We only need to be able to free swappable pages: only the
swappable region will be usable for large contiguous allocations. We
don't even need to move them: they can be paged back in afterwards.
Obviously this is expensive if we expect to do it often, but in reality
it is probably something we only need to do at driver setup time (or
occasionally on driver open).
--Stephen
-
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.tux.org/lkml/