[PATCH] fix CONFIG_DISCONTIGMEM and CONFIG_VIRTUAL_MEMMAP

From: Jesse Barnes <jbarnes_at_engr.sgi.com>
Date: 2004-09-06 01:33:46
Looks like the patch that fixed Ian's problem introduced an ugly warning.  
Maybe we could just switch to requiring CONFIG_DISCONTIGMEM and 
CONFIG_VIRTUAL_MEMMAP for ia64 in general?  That would let us kill a lot of 
code and only have one code path, etc.  Benchmarks have shown that the 
overhead of CONFIG_DISCONTIGMEM is very difficult to measure (if you look at 
the code, the only added overhead in any fast path is an additional pointer 
dereference in alloc_pages).  CONFIG_VIRTUAL_MEMMAP is a little more 
expensive iirc, but still difficult to measure.

Jesse

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Received on Sun Sep 5 11:34:28 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:30 EST