On Tue, 22 Sep 98 00:32 BST, alan@lxorguk.ukuu.org.uk (Alan Cox) said:
> Is there any current reason that the shared memory tables (the ulong per
> page) can't be vmalloc() instead of kmalloc()'d. Its a small change to
> allow support for much bigger shared memory areas that the price of RAM
> makes eminently reasonable.
No reason I can think of except the same reason we only reserved one
page for the swap lock map: we've always done it that way. The shm map
is only used for paging, so it's not desperately performance critical,
and should never be accessed from interrupts.
--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/