All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	David Howells <dhowells@redhat.com>,
	Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: [patch] mm: cleanup bootmem
Date: Sun, 15 Jan 2006 05:06:24 +1100	[thread overview]
Message-ID: <43C93DA0.3040506@yahoo.com.au> (raw)
In-Reply-To: <43C93CCA.9080503@yahoo.com.au>

Nick Piggin wrote:
> Linus Torvalds wrote:
> 
>>
>> On Sat, 14 Jan 2006, Nick Piggin wrote:
>>
>>> Objections?
>>
>>
>>
>> The whole point of the pre-batching was that apparently the 
>> non-batched bootmem code took ages to boot in simulation with lots of 
>> memory. I think it was the ia64 people who used simulation a lot. So..
>>
>>         Linus
>>
> 
> Changelog doesn't mention it: a226f6c899799fe2c4919daa0767ac579c88f7bd
> 
> Or... what do you mean by pre-batching? (maybe I'm confused and you're
> talking about my prefetching change or something)
> 

Oh the BITS_PER_LONG batching? That's still completely functional after
my patch. In fact, as I said in a followup it is likely to work better
than with David's change to free batched pages as order-0, because I
reverted back to freeing them as higher order pages.

-- 
SUSE Labs, Novell Inc.

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

  reply	other threads:[~2006-01-14 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14 12:42 [patch] mm: cleanup bootmem Nick Piggin
2006-01-14 12:47 ` Nick Piggin
2006-01-14 17:50 ` Linus Torvalds
2006-01-14 18:02   ` Nick Piggin
2006-01-14 18:06     ` Nick Piggin [this message]
2006-01-14 18:13       ` Linus Torvalds
2006-01-14 18:43         ` Nick Piggin
2006-01-16  8:53         ` Jes Sorensen
2006-01-16 15:25           ` Jack Steiner

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=43C93DA0.3040506@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.