From: Johannes Weiner <hannes@cmpxchg.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
jirislaby@gmail.com, Ralf Baechle <ralf@linux-mips.org>,
x86@kernel.org
Subject: Re: [RFC 1/1] bootmem: move big allocations behing 4G
Date: Tue, 19 Jan 2010 15:33:55 +0100 [thread overview]
Message-ID: <20100119143355.GB7932@cmpxchg.org> (raw)
In-Reply-To: <1263855390-32497-1-git-send-email-jslaby@suse.cz>
Hello Jiri,
On Mon, Jan 18, 2010 at 11:56:30PM +0100, Jiri Slaby wrote:
> Hi, I'm fighting a bug where Grub loads the kernel just fine, whereas
> isolinux doesn't. I found out, it's due to different addresses of
> loaded initrd. On a machine with 128G of memory, grub loads the
> initrd at 895M in our case and flat mem_map (2G long) is allocated
> above 4G due to 2-4G BIOS reservation.
>
> On the other hand, with isolinux, the 0-2G is free and mem_map is
> placed there leaving no space for others, hence kernel panics for
> swiotlb which needs to be below 4G.
Bootmem already protects the lower 16MB DMA zone for the obvious reasons,
how about shifting the default bootmem goal above the DMA32 zone if it exists?
I added Ralf and the x86 Team on Cc as this only affects x86 and mips, afaics.
> Any ideas?
I tested the below on a rather dull x86_64 machine and it seems to work. Would
this work in your case as well? The goal for mem_map should now be above 4G.
Hannes
next prev parent reply other threads:[~2010-01-19 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 22:56 Jiri Slaby
2010-01-19 14:33 ` Johannes Weiner [this message]
2010-01-19 22:02 ` Jiri Slaby
2010-01-20 13:50 ` Jiri Slaby
2010-01-20 15:30 ` Johannes Weiner
2010-01-20 22:53 ` [PATCH] bootmem: avoid DMA32 zone by default Johannes Weiner
2010-01-20 23:12 ` Jiri Slaby
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=20100119143355.GB7932@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ralf@linux-mips.org \
--cc=x86@kernel.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