[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[RFC] tabulating page->virtual on highmem
- To: linux-mm@kvack.org
- Subject: [RFC] tabulating page->virtual on highmem
- From: William Lee Irwin III <wli@holomorphy.com>
- Date: Wed, 8 May 2002 15:15:06 -0700
- Fake-Sender: owner-linux-mm@kvack.org
- Mail-Followup-To: William Lee Irwin III <wli@holomorphy.com>,linux-mm@kvack.org
- Organization: The Domain of Holomorphy
- Original-Recipient: rfc822;linux-mm-archive@humbolt.geo.uu.nl
- Sender: Rik van Riel <riel@nl.linux.org>
- User-Agent: Mutt/1.3.25i
The size of the kmap pool appears to dictate the number of distinct
values of page->virtual. Maintaining an index into the pool would
seem to provide superior space behavior, as the index need not be
of full machine word precision. Furthermore, no auxiliary lookup
would appear to be required as the kmap pool is virtually contiguous
and so the virtual address could be calculated from base virtual
address of the kmap pool and the index into the pool.
For architectures using page->virtual for page_address() calculation
this technique does not apply, and so page->virtual would then need
to be maintained as is, or at least retain enough precision for a full
page frame number.
I don't have my heart set on this but I thought I'd at least throw the
idea out where its desirability (and potential implementations) could
be discussed.
Cheers,
Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/