public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pauline Middelink <middelink@polyware.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: mapping physical memory
Date: Fri, 26 Jan 2001 17:28:56 +0100	[thread overview]
Message-ID: <20010126172856.A8069@polyware.nl> (raw)
In-Reply-To: <fa.h16635v.l0uu8m@ifi.uio.no> <027801c08784$48a04630$0701a8c0@morph>
In-Reply-To: <027801c08784$48a04630$0701a8c0@morph>; from dmaas@dcine.com on Fri, Jan 26, 2001 at 05:39:38AM -0500

On Fri, 26 Jan 2001 around 05:39:38 -0500, Dan Maas wrote:
> > I need to be able to obtain and pin approximately 8 MB of
> > contiguous physical memory in user space.  How would I go
> > about doing that under Linux if it is at all possible?
> 
> The only way to allocate that much *physically* contiguous memory is by
> writing a driver that grabs it at boot-time (I think the "bootmem" API is
> used for this). This is an extreme measure and should rarely be necessary,
> except in special cases such as primitive PCI cards that lack support for
> scatter/gather DMA.

Or is you want to reuse that memory between apps, use the bigphysarea
patch. Yes, its available for 2.4.0 now :)

    Met vriendelijke groet,
        Pauline Middelink
-- 
GPG Key fingerprint = 2D5B 87A7 DDA6 0378 5DEA  BD3B 9A50 B416 E2D0 C3C2
For more details look at my website http://www.polyware.nl/~middelink
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-26 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.h16635v.l0uu8m@ifi.uio.no>
2001-01-26 10:39 ` mapping physical memory Dan Maas
2001-01-26 16:28   ` Pauline Middelink [this message]
2001-01-26  3:53 Dima Brodsky

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=20010126172856.A8069@polyware.nl \
    --to=middelink@polyware.nl \
    --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