I'd just suggest a __setup() for it initially, let's see how it gets used.
There are certainly other options down the road, and I think that's one
reason you want to keep a very spartan interface and to make it not expose
any big details _except_ for the actual hw limitations.
> Do you think something like that would be worth it or do you prefer
> the really dumb version that just never tries to use the pages in
> magic dumb zone for anything else?
I'd really go for the dumb approach first, see what the Oracle users
think, and make sure that the _administration_ of the memory is totally
separate from the use of it (ie don't allow the oracle binary to do any
setup, start the setup with a kernel boot line, and down the line see if
you can add some more dynamic "try to free 8MB of contiguous RAM and add
it to the magic zone" things that would be run externally from Oracle).
And let's not _just_ blame oracle, maybe other uses can actually be found
for this (eg XFree86 for UMA graphics cards etc might actually want to use
something like this eventually).
Linus
-
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/