Re: [PATCH 6/6] Break out memory initialisation code from page_alloc.c to mem_init.c

Mel Gorman wrote:

page_alloc.c contains a large amount of memory initialisation code. This patch
breaks out the initialisation code to a separate file to make page_alloc.c
a bit easier to read.


I realise this is at the wrong end of your queue, but if you _can_ easily
break it out and submit it first, it would be a nice cleanup and would help
shrink your main patchset.

Also, we're recently having some problems with architectures not aligning
zones correctly. Would it make sense to add these sorts of sanity checks,
and possibly forcing alignment corrections into your generic code?

Nick
--

Send instant messages to your online friends http://au.messenger.yahoo.com-

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH 6/6] Break out memory initialisation code from page_alloc.c to mem_init.c
  - From: Mel Gorman <[email protected]>

References:
- [PATCH 0/6] Sizing zones and holes in an architecture independent manner V6
  - From: Mel Gorman <[email protected]>
- [PATCH 6/6] Break out memory initialisation code from page_alloc.c to mem_init.c
  - From: Mel Gorman <[email protected]>

Prev by Date: Re: [PATCH 004 of 11] md: Increase the delay before marking metadata clean, and make it configurable.
Next by Date: Re: High load average on disk I/O on 2.6.17-rc3
Previous by thread: [PATCH 6/6] Break out memory initialisation code from page_alloc.c to mem_init.c
Next by thread: Re: [PATCH 6/6] Break out memory initialisation code from page_alloc.c to mem_init.c
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]