Messages in this thread | | | Date | Tue, 25 Apr 2006 10:48:55 +0900 | From | KAMEZAWA Hiroyuki <> | Subject | Re: [PATCH 0/7] [RFC] Sizing zones and holes in an architecture independent manner V4 |
| |
On Mon, 24 Apr 2006 21:20:09 +0100 (IST) Mel Gorman <mel@csn.ul.ie> wrote:
> This is V4 of the patchset to size zones and memory holes in an > architecture-independent manner. >
Could you add some documentation about 'how to use' your generic funcs ? I think more archs can use your generic routine if well documented.
All initialization path can be written in following way ? == for_all_memory_region() add_active_range(nid, start, end) free_area_init_nodes(max_dma, max_dma32, max_low_pfn, max_pfn); ==
And following functions are really needed ? == +extern void remove_all_active_ranges(void); +extern void get_pfn_range_for_nid(unsigned int nid, + unsigned long *start_pfn, unsigned long *end_pfn); +extern unsigned long find_min_pfn_with_active_regions(void); +extern unsigned long find_max_pfn_with_active_regions(void); +extern int early_pfn_to_nid(unsigned long pfn); +extern void free_bootmem_with_active_regions(int nid, + unsigned long max_low_pfn); +extern void sparse_memory_present_with_active_regions(int nid); +extern unsigned long absent_pages_in_range(unsigned long start_pfn, + unsigned long end_pfn);
-Kame
- 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/
| |