From: "LUTZ,TODD (HP-Boise,ex1)" <tlutz@hp.com>
To: "'linux-mm@kvack.org'" <linux-mm@kvack.org>
Subject: Ideas for adding physically contiguous memory support to mmap()??
Date: Tue, 10 Apr 2001 15:34:17 -0400 [thread overview]
Message-ID: <C78C149684DAD311B757009027AA5CDC094DA2A8@xboi02.boi.hp.com> (raw)
I would like to be able to extend mmap() (in 2.4.2) to support returning
physically contiguous memory as shared memory.
Here are some requirements:
1. Able to specify any size that is a multiple of PAGE_SIZE (not just powers
of 2).
2. Able to specify the size when the application runs (not on the bootline
like the bigphysarea patch).
3. Able to specify sizes larger than 4MB (somewhere between 256MB and 512MB
is probably the max).
4. Preferably add another bit to the flags parameter of mmap(), like
"MAP_CONTIG".
5. It is OK for the call to fail if there isn't enough physically contiguous
memory available (even if there is enough non-contiguous memory available).
After looking at the code, I think I need to...
1. Create a function like alloc_contig_pages() similar to alloc_pages() that
takes a "numpages" parameter instead of "order".
2. Increase MAX_ORDER in mmzone.h to 17.
3. Start at do_mmap_pgoff() and change all the calls down to alloc_pages().
Any suggestions or comments?
-- Thanks,
Todd Lutz
--
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 reply other threads:[~2001-04-10 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 19:34 LUTZ,TODD (HP-Boise,ex1) [this message]
2001-04-10 23:24 ` Benjamin C.R. LaHaise
2001-04-17 12:42 ` Stephen C. Tweedie
2001-04-11 3:39 Ideas for adding physically contiguous memory support to mmap ()?? LUTZ,TODD (HP-Boise,ex1)
2001-04-11 15:00 ` Benjamin C.R. LaHaise
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=C78C149684DAD311B757009027AA5CDC094DA2A8@xboi02.boi.hp.com \
--to=tlutz@hp.com \
--cc=linux-mm@kvack.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