From: Robert Love <rml@tech9.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] bootmem for 2.5
Date: 07 Nov 2001 21:06:04 -0500 [thread overview]
Message-ID: <1005185194.939.20.camel@phantasy> (raw)
In-Reply-To: <20011107164400.G26577@holomorphy.com>
In-Reply-To: <20011102140207.V31822@w-wli.des.beaverton.ibm.com> <1005017025.897.0.camel@phantasy> <20011107164400.G26577@holomorphy.com>
On Wed, 2001-11-07 at 19:44, William Lee Irwin III wrote:
> I've managed to reproduce the problem, and I heard from you elsewhere
> that you've verified the fix (although it appeared to reduce the memory
> savings to 4KB).
Fix does indeed work. Tested on:
P3-733 i815-based, gained 4KB from 384MB
PPro-200 i440FX-based, gained 4KB from 64MB
Celeron-500 i440BX-based, gained 8KB from 512MB
No problem on any system -- no difference, in fact, except the gain in
total system memory. Most importantly, however, the new design is quite
nice. :>
I bet the previous ~100KB gain came from not using APIC. I was
comparing APIC without new bootmem to new bootmem without APIC. The
much more realistic and modest 4KB is within range of what I would
expect, and I bet if I compared with and without bootmem on a non-APIC
kernel I would see the same results.
Would you expect problems from laptops or other things with flakey
mappings/reservations? I can test it on a couple of laptops if you
want...
Robert Love
next prev parent reply other threads:[~2001-11-08 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 22:02 [RFC] bootmem for 2.5 William Irwin
2001-11-03 3:31 ` William Lee Irwin III
[not found] ` <20011102214308.A8217@kroah.com>
2001-11-03 19:58 ` William Lee Irwin III
2001-11-06 3:23 ` Robert Love
2001-11-06 4:10 ` William Lee Irwin III
2001-11-08 0:44 ` William Lee Irwin III
2001-11-08 2:06 ` Robert Love [this message]
2001-11-09 0:27 ` William Lee Irwin III
2001-12-15 6:05 ` Ingo Molnar
2001-12-15 13:27 ` William Lee Irwin III
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=1005185194.939.20.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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.