diff options
| author |   Christoph Lameter <clameter@sgi.com> | 2006-09-25 23:31:19 -0700 |
|---|---|---|
| committer |   Linus Torvalds <torvalds@g5.osdl.org> | 2006-09-26 08:48:47 -0700 |
| commit | 19655d3487001d7df0e10e9cbfc27c758b77c2b5 (patch) | |
| tree | 8d0aaa216bd32bd64e3a9652fd34d40bdb9d1075 /include/linux/swap.h | |
| parent | [PATCH] Apply type enum zone_type (diff) | |
| download | linux-dev-19655d3487001d7df0e10e9cbfc27c758b77c2b5.tar.xz linux-dev-19655d3487001d7df0e10e9cbfc27c758b77c2b5.zip | |
[PATCH] linearly index zone->node_zonelists[]
I wonder why we need this bitmask indexing into zone->node_zonelists[]?
We always start with the highest zone and then include all lower zones
if we build zonelists.
Are there really cases where we need allocation from ZONE_DMA or
ZONE_HIGHMEM but not ZONE_NORMAL? It seems that the current implementation
of highest_zone() makes that already impossible.
If we go linear on the index then gfp_zone() == highest_zone() and a lot
of definitions fall by the wayside.
We can now revert back to the use of gfp_zone() in mempolicy.c ;-)
Signed-off-by: Christoph Lameter <clameter@sgi.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include/linux/swap.h')
0 files changed, 0 insertions, 0 deletions