From: Andy Whitcroft <apw@shadowen.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-mm@kvack.org, linux-arch@vger.kernel.org,
Nick Piggin <npiggin@suse.de>,
Christoph Lameter <clameter@sgi.com>, Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH 3/7] Generic Virtual Memmap support for SPARSEMEM
Date: Mon, 30 Jul 2007 15:39:55 +0100 [thread overview]
Message-ID: <46ADF83B.3050406@shadowen.org> (raw)
In-Reply-To: <20070714152058.GA12478@infradead.org>
Christoph Hellwig wrote:
>> --- a/include/asm-generic/memory_model.h
>> +++ b/include/asm-generic/memory_model.h
>> @@ -46,6 +46,12 @@
>> __pgdat->node_start_pfn; \
>> })
>>
>> +#elif defined(CONFIG_SPARSEMEM_VMEMMAP)
>> +
>> +/* memmap is virtually contigious. */
>> +#define __pfn_to_page(pfn) (vmemmap + (pfn))
>> +#define __page_to_pfn(page) ((page) - vmemmap)
>> +
>> #elif defined(CONFIG_SPARSEMEM)
>
> nice ifdef mess you have here. and an sm-generic file should be something
> truely generic instead of a complete ifdef forest. I think we'd be
> much better off duplicating the two lines above in architectures using
> it anyway.
The code itself is generic in the sense its architecture neutral. This
is "per memory model" code. I am wondering however why it is in an
asm-anything include file here. This seems to the world like it should
be in include/linux/memory_model.h.
>> diff --git a/mm/sparse.c b/mm/sparse.c
>> index d6678ab..5cc6e74 100644
>> --- a/mm/sparse.c
>> +++ b/mm/sparse.c
>> @@ -9,6 +9,8 @@
>> #include <linux/spinlock.h>
>> #include <linux/vmalloc.h>
>> #include <asm/dma.h>
>> +#include <asm/pgalloc.h>
>> +#include <asm/pgtable.h>
>>
>> /*
>> * Permanent SPARSEMEM data:
>> @@ -218,6 +220,192 @@ void *alloc_bootmem_high_node(pg_data_t *pgdat, unsigned long size)
>> return NULL;
>> }
>>
>> +#ifdef CONFIG_SPARSEMEM_VMEMMAP
>> +/*
>> + * Virtual Memory Map support
>> + *
>> + * (C) 2007 sgi. Christoph Lameter <clameter@sgi.com>.
>
> When did we start putting copyright lines and large block comment in the
> middle of the file?
>
> Please sort this and the ifdef mess out, I suspect a new file for this
> code would be best.
I will have a look at how this would look pulled out into separate .c files.
>> +void * __meminit vmemmap_alloc_block(unsigned long size, int node)
>
> void * __meminit vmemmap_alloc_block(unsigned long size, int node)
>
>> +#ifndef CONFIG_ARCH_POPULATES_SPARSEMEM_VMEMMAP
>> +void __meminit vmemmap_verify(pte_t *pte, int node,
>> + unsigned long start, unsigned long end)
>> +{
>> + unsigned long pfn = pte_pfn(*pte);
>> + int actual_node = early_pfn_to_nid(pfn);
>> +
>> + if (actual_node != node)
>> + printk(KERN_WARNING "[%lx-%lx] potential offnode "
>> + "page_structs\n", start, end - 1);
>> +}
>
> Given tht this function is a tiny noop please just put them into the
> arch dir for !CONFIG_ARCH_POPULATES_SPARSEMEM_VMEMMAP architectures
> and save yourself both the ifdef mess and the config option.
>
Will also look that over and see how it comes out.
-apw
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-30 14:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 13:34 [PATCH 0/7] Sparsemem Virtual Memmap V5 Andy Whitcroft
2007-07-13 13:35 ` [PATCH 1/7] sparsemem: clean up spelling error in comments Andy Whitcroft
2007-07-13 13:35 ` [PATCH 2/7] sparsemem: record when a section has a valid mem_map Andy Whitcroft
2007-07-13 14:24 ` [PATCH] Bah, hoisted by my own petard. Below is an updated version Andy Whitcroft
2007-07-13 13:36 ` [PATCH 3/7] Generic Virtual Memmap support for SPARSEMEM Andy Whitcroft
2007-07-13 14:51 ` KAMEZAWA Hiroyuki
2007-07-13 22:42 ` Christoph Lameter
2007-07-13 23:12 ` KAMEZAWA Hiroyuki
2007-07-13 23:17 ` Christoph Lameter
2007-07-13 23:25 ` KAMEZAWA Hiroyuki
2007-07-14 15:20 ` Christoph Hellwig
2007-07-14 16:06 ` Christoph Lameter
2007-07-14 16:33 ` Christoph Hellwig
2007-07-23 19:36 ` Christoph Lameter
2007-07-30 14:39 ` Andy Whitcroft [this message]
2007-07-30 18:35 ` Christoph Lameter
2007-07-13 13:36 ` [PATCH 4/7] x86_64: SPARSEMEM_VMEMMAP 2M page size support Andy Whitcroft
2007-07-19 23:25 ` Andrew Morton
2007-07-13 13:37 ` [PATCH 5/7] IA64: SPARSEMEM_VMEMMAP 16K " Andy Whitcroft
2007-07-13 13:37 ` [PATCH 6/7] SPARC64: SPARSEMEM_VMEMMAP support Andy Whitcroft
2007-07-13 17:00 ` Christoph Lameter
2007-07-13 13:38 ` [PATCH 7/7] ppc64: " Andy Whitcroft
2007-07-13 17:04 ` [PATCH 0/7] Sparsemem Virtual Memmap V5 Christoph Lameter
2007-07-13 17:40 ` Andrew Morton
2007-07-13 18:23 ` Christoph Lameter
2007-07-14 8:57 ` Russell King
2007-07-14 15:10 ` Christoph Lameter
2007-07-14 17:16 ` Russell King
2007-07-13 20:08 ` Roman Zippel
2007-07-13 22:02 ` Luck, Tony
2007-07-13 22:21 ` Christoph Lameter
2007-07-13 22:37 ` Luck, Tony
2007-07-13 22:54 ` Christoph Lameter
2007-07-13 23:27 ` KAMEZAWA Hiroyuki
2007-07-13 23:28 ` Christoph Lameter
2007-07-14 8:49 ` Nick Piggin
2007-07-14 15:07 ` Christoph Lameter
2007-07-13 22:43 ` David Miller, Andrew Morton
2007-07-26 8:05 ` Paul Mundt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46ADF83B.3050406@shadowen.org \
--to=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=hch@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=npiggin@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox