From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: "LUTZ,TODD (HP-Boise,ex1)" <tlutz@hp.com>
Cc: "'linux-mm@kvack.org'" <linux-mm@kvack.org>
Subject: RE: Ideas for adding physically contiguous memory support to mmap ()??
Date: Wed, 11 Apr 2001 11:00:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1010411105705.27917A-100000@kanga.kvack.org> (raw)
In-Reply-To: <C78C149684DAD311B757009027AA5CDC094DA2A9@xboi02.boi.hp.com>
On Tue, 10 Apr 2001, LUTZ,TODD (HP-Boise,ex1) wrote:
> The short answer...
>
> I have an embedded application that wants to manage most of memory in the
> system and wants it to be shared between processes. The application starts,
> determines the amount of free memory, leaves a little for the OS, then
> allocates the rest as shared memory. It needs to be physically contiguous
> because not all of our DMAs support scatter-gather.
Stop building broken hardware -- seriously! But if you must, just use the
bigmem patches to reserve a chunk of memory and then mmap it via /dev/mem
(or even boot with a mem= map that leaves memory unused). That doesn't
require any kernel changes and is much faster to implement.
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-04-11 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 3:39 LUTZ,TODD (HP-Boise,ex1)
2001-04-11 15:00 ` Benjamin C.R. LaHaise [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 19:34 Ideas for adding physically contiguous memory support to mmap()?? LUTZ,TODD (HP-Boise,ex1)
2001-04-10 23:24 ` Benjamin C.R. LaHaise
2001-04-17 12:42 ` Stephen C. Tweedie
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.3.96.1010411105705.27917A-100000@kanga.kvack.org \
--to=blah@kvack.org \
--cc=linux-mm@kvack.org \
--cc=tlutz@hp.com \
/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