From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>
Cc: "LUTZ,TODD (HP-Boise,ex1)" <tlutz@hp.com>,
"'linux-mm@kvack.org'" <linux-mm@kvack.org>
Subject: Re: Ideas for adding physically contiguous memory support to mmap()??
Date: Tue, 17 Apr 2001 13:42:51 +0100 [thread overview]
Message-ID: <20010417134251.B2505@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1010410191553.22333A-100000@kanga.kvack.org>; from blah@kvack.org on Tue, Apr 10, 2001 at 07:24:12PM -0400
Hi,
On Tue, Apr 10, 2001 at 07:24:12PM -0400, Benjamin C.R. LaHaise wrote:
> On Tue, 10 Apr 2001, LUTZ,TODD (HP-Boise,ex1) wrote:
>
> > 1. Able to specify any size that is a multiple of PAGE_SIZE (not just powers
> > of 2).
>
> First off: why do you need this functionality? It does not sound like it
> provides any significant benefits over the current system once you take
> into consideration the effects it will have on memory fragmentation.
Indeed. Most of the motivation for large contiguous memory areas in
user space are concerned with cache line colouring and efficient use
of tlbs. An API for large page support and kernel support for cache
colouring would be nice, but in general the more of this that can be
done opportunistically (without any application API changes), the
better.
Cheers,
Stephen
--
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-17 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 19:34 LUTZ,TODD (HP-Boise,ex1)
2001-04-10 23:24 ` Benjamin C.R. LaHaise
2001-04-17 12:42 ` Stephen C. Tweedie [this message]
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=20010417134251.B2505@redhat.com \
--to=sct@redhat.com \
--cc=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