From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <clameter@sgi.com>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] sparsemem vmemmap: initialize memmap.
Date: Fri, 9 May 2008 13:34:34 +0200 [thread overview]
Message-ID: <20080509113434.GG9840@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20080509103132.GB10210@shadowen.org>
> > Index: linux-2.6/mm/sparse-vmemmap.c
> > ===================================================================
> > --- linux-2.6.orig/mm/sparse-vmemmap.c
> > +++ linux-2.6/mm/sparse-vmemmap.c
> > @@ -154,6 +154,6 @@ struct page * __meminit sparse_mem_map_p
> > int error = vmemmap_populate(map, PAGES_PER_SECTION, nid);
> > if (error)
> > return NULL;
> > -
> > + memset(map, 0, PAGES_PER_SECTION * sizeof(struct page));
> > return map;
> > }
>
> The normal expectation is that all allocations are made using
> vmemmap_alloc_block() which allocates from the appropriate place. Once
> the buddy is up and available it uses:
>
> struct page *page = alloc_pages_node(node,
> GFP_KERNEL | __GFP_ZERO, get_order(size));
>
> to get the memory so it should all be zero'd. So I would expect all
> existing users to be covered by that? Can you not simply use __GFP_ZERO
> for your allocations or use vmemmap_alloc_block() ?
Ah, I didn't notice the __GFP_ZERO. So it's just an s390 bug. Will
move the memset to our code instead.
Thanks!
--
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:[~2008-05-09 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 6:38 Heiko Carstens, Heiko Carstens
2008-05-09 10:31 ` Andy Whitcroft
2008-05-09 11:34 ` Heiko Carstens [this message]
2008-05-09 16:25 ` Christoph Lameter
2008-05-09 17:01 ` Heiko Carstens
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=20080509113434.GG9840@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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