From: William Lee Irwin III <wli@holomorphy.com>
To: Brian McGrew <Brian@doubledimension.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help with mapping memory into kernel space?
Date: Wed, 18 Aug 2004 00:31:41 -0700 [thread overview]
Message-ID: <20040818073141.GV11200@holomorphy.com> (raw)
In-Reply-To: <E6456D527ABC5B4DBD1119A9FB461E3501E00B@constellation.doubledimension.com>
On Tue, Aug 17, 2004 at 10:39:38PM -0700, Brian McGrew wrote:
> The overall problem is that the more system memory we install,
> the fewer IBB's we can use. For instance, 256MB lets us use
> four IBB's; 512MB lets us use three IBB's and so on. Basicly,
> the kernel blows up trying to map memory. Each IBB has two
> banks of 64MB of RAM on them which we try and memmap to system
> memory for speed of addressing. So essentaily, we're sending
> out four camera systems with only 256MB of memory which is only
> about one quarter of what we need.
> I can't think of any better way to explain it other than it's
> almost like adding system memory subtracts from kernel memory.
> Does that make any sense? We've tried building the kernel with
> the 4GB memory model and the 64GB memory model and had no success.
You appear to be trying to ioremap() vast areas. ia32 has limited
address space, so you need to do one of two things:
(a) subdivide into portions mapped into different address spaces
(b) map portions on demand
There is no support for (a) in Linux.
-- wli
next prev parent reply other threads:[~2004-08-18 7:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 5:39 Help with mapping memory into kernel space? Brian McGrew
2004-08-18 7:31 ` William Lee Irwin III [this message]
2004-08-18 11:16 ` Mark Hounschell
2004-08-18 20:27 ` William Lee Irwin III
2004-08-18 15:30 ` Daniel Gryniewicz
2004-08-18 15:59 ` Richard B. Johnson
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=20040818073141.GV11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Brian@doubledimension.com \
--cc=linux-kernel@vger.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