public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Beaumont" <christophe@paracel.com>
To: "Linux-Kernel" <linux-kernel@vger.kernel.org>
Subject: HUGE contiguous mem space with 2.4
Date: Mon, 21 May 2001 15:39:32 -0700	[thread overview]
Message-ID: <NFBBINOGHMOOBMPNBAHKMEFLCAAA.christophe@paracel.com> (raw)

Hi...

I am facing an odd problem here. I have an application here
that requires a HUGE physically contiguous memory area to 
be locked (yes, I have hardware DMA'ing in and out of that
area, over the PCI bus). HUGE being like one Gig (could be
more if needed...)
I am trying to use the mem=1024M option at boot time (yes,
the box has 2 Gigs of RAM) and then ioremap() from within 
my module. There I have a couple of issues:
 - if I use high_memory as is, I cannot remap any area 
(high_memory=f800:0000 ???)
 - if I use high_memory thru virt_to_phys, I can then remap...
up to 64 Megs (maybe a little more, but for sure less than
128 Megs) (virt_to_phys(high_mem)=3800:0000)

I tried with other values (like mem=250M 512M 1536M) and could
NOT remap anything close to the whole amount of "reserved" memory
(best case being with mem=256M I can remap 512M out of 1.75Gigs)

I guess I am missing a point somewhere.... or have totally 
been "ignoring" some doc somewhere (alessandro could be the man
for this one thing *-) )

[system is a dual P3 with 2 gigs of RAM, a 2.4.3 kernel with SMP
turned on... and the nice option for 4Gigs of RAM... would the
64Gig option help me??? just wondering there...]

Any pointer, advise, help, hint... laugh at the stupid thing I 
have forgotten is more than welcome..

tia

Chris.

             reply	other threads:[~2001-05-21 22:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-21 22:39 Christophe Beaumont [this message]
2001-05-23 20:46 ` HUGE contiguous mem space with 2.4 Jeff Hartmann

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=NFBBINOGHMOOBMPNBAHKMEFLCAAA.christophe@paracel.com \
    --to=christophe@paracel.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