mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Daniel Gryniewicz <dang@fprintf.net>
Cc: Brian McGrew <Brian@doubledimension.com>, linux-kernel@vger.kernel.org
Subject: Re: Help with mapping memory into kernel space?
Date: Wed, 18 Aug 2004 11:59:42 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0408181144160.16298@chaos> (raw)
In-Reply-To: <1092843015.14961.2.camel@localhost>

On Wed, 18 Aug 2004, Daniel Gryniewicz wrote:

> On Tue, 2004-08-17 at 22:39 -0700, Brian McGrew wrote:
> > Good day All:
> >
>
> <snip>
>
> > 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.
>
> On x86, the kernel has 1 GiB of address space.  Try the 2G/2G split
> patches, or the 4G/4G patches, either one of which should increase your
> kernel address space enough to map both memory and your buffers.
>
> Daniel

>  out four camera systems with only 256MB of memory which is only
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You can use as much memory as you can afford if the designer of
this system would only understand that you can't fit 4 GB of
application RAM into 4 GB of address-space and leave anything
available for the system.

It needs to be done like this:

------------|-------------|-----------
 Other      |   N Mbyte   |  Other address space
 address    |   window    |  ..................
------------|-------------|-----------
            |
            |
        -----------------
        | Page register |
        |----------------
                        |
                        -----------------------
                        |    Page 0            |
                        |--|--------------------
                           |  Page 1            |
                           |---------------------
                                Page N, etc.

You make a small window in the available address-space, and you
map your RAM into that address-space with a page register. You
can access much, much more RAM than available address-space,
and with things like video and pictures, the occasional switching
of a page-register adds practically no overhead.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.



      reply	other threads:[~2004-08-18 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18  5:39 Brian McGrew
2004-08-18  7:31 ` William Lee Irwin III
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 [this message]

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=Pine.LNX.4.53.0408181144160.16298@chaos \
    --to=root@chaos.analogic.com \
    --cc=Brian@doubledimension.com \
    --cc=dang@fprintf.net \
    --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

all inboxes | Powered by JetHome®