From: Benjamin LaHaise <bcrl@kvack.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: klibc@zytor.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sys_mmap2 on different architectures
Date: Wed, 22 Feb 2006 19:14:11 -0500 [thread overview]
Message-ID: <20060223001411.GA20487@kvack.org> (raw)
In-Reply-To: <43FCDB8A.5060100@zytor.com>
On Wed, Feb 22, 2006 at 01:45:46PM -0800, H. Peter Anvin wrote:
> I've looked through the code for sys_mmap2 on several architectures, and
> it looks like some architectures plays by the "shift is always 12" rule,
> e.g. SPARC, and some expect userspace to actually obtain the page
> size, e.g. PowerPC and MIPS. On some architectures, e.g. x86 and ARM,
> the point is moot since PAGE_SIZE is always 2^12.
The sys_mmap2() ABI is that the page shift is always fixed to whatever
page size is reasonable for the architecture, typically 2^12. The syscall
should never be exposed as mmap2(), only as the large file size version
of mmap() (aka mmap64()). The other consideration is that it should not
be implemented in 64 bit ABIs, as those machines should be using a 64 bit
native mmap(). Does that clear things up a bit? Cheers,
-ben
--
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here
and they've asked us to stop the party." Don't Email: <dont@kvack.org>.
next prev parent reply other threads:[~2006-02-23 0:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 21:45 sys_mmap2 on different architectures H. Peter Anvin
2006-02-22 21:54 ` David S. Miller
2006-02-22 22:00 ` H. Peter Anvin
2006-02-23 0:05 ` H. Peter Anvin
2006-02-23 0:40 ` David S. Miller
2006-02-23 0:41 ` David S. Miller
2006-02-23 0:14 ` Benjamin LaHaise [this message]
2006-02-23 0:22 ` H. Peter Anvin
2006-02-23 0:43 ` David S. Miller
2006-02-23 0:59 ` H. Peter Anvin
2006-02-23 1:03 ` David S. Miller
2006-02-23 1:06 ` H. Peter Anvin
2006-02-23 17:39 ` Benjamin LaHaise
2006-02-23 17:47 ` H. Peter Anvin
2006-02-23 2:56 ` Paul Mackerras
2006-02-23 3:35 ` H. Peter Anvin
2006-02-23 17:32 ` Ralf Baechle
2006-02-23 17:43 ` H. Peter Anvin
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=20060223001411.GA20487@kvack.org \
--to=bcrl@kvack.org \
--cc=hpa@zytor.com \
--cc=klibc@zytor.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