From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Cyrill Gorcunov" <gorcunov@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: bootmem allocator
Date: Mon, 7 Apr 2008 14:45:57 -0700 [thread overview]
Message-ID: <86802c440804071445l7bef949fg5c500f0c09ae40e@mail.gmail.com> (raw)
In-Reply-To: <87iqytqwl7.fsf@basil.nowhere.org>
On Mon, Apr 7, 2008 at 12:44 PM, Andi Kleen <andi@firstfloor.org> wrote:
>
> Ingo Molnar <mingo@elte.hu> writes:
>
> > * Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> >
> >> Hi Ingo, Peter,
> >>
> >> small question. It was a patch recently posted which removes memset(x,
> >> 0, x) after __alloc_bootmem call. There are a few another code
> >> snippets who still call memset(x, 0, x). And who is responsible for
> >> memory clearing? bootmem allocator or caller?
> >
> > hm, bootmem allocator is supposed to clear memory. We have a couple of
> > places that rely on that.
>
> I was actually considering to change that for the GB pages hugetlbfs
> patchkit, because memset for 1G is a little slow and not needed (will be cleared later
> anyways) and it might be a problem for very large systems with a lot of such
> pages at boot.
add another zalloc_bootmem?
YH
next prev parent reply other threads:[~2008-04-07 21:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 18:56 Cyrill Gorcunov
2008-04-07 19:09 ` Ingo Molnar
2008-04-07 19:44 ` Andi Kleen
2008-04-07 21:45 ` Yinghai Lu [this message]
2008-04-08 4:14 ` Cyrill Gorcunov
2008-04-08 4:33 ` H. Peter Anvin
2008-04-08 5:50 ` Cyrill Gorcunov
2008-04-08 16:18 ` Cyrill Gorcunov
2008-04-08 8:04 ` Ingo Molnar
2008-04-08 8:12 ` Andi Kleen
2008-04-08 13:57 ` Cyrill Gorcunov
2008-04-08 17:34 ` Cyrill Gorcunov
2008-04-08 17:44 ` H. Peter Anvin
2008-04-09 6:00 ` Mike Travis
2008-04-09 6:08 ` Andi Kleen
2008-04-09 6:55 ` Mike Travis
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=86802c440804071445l7bef949fg5c500f0c09ae40e@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=andi@firstfloor.org \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®