From: Ralf Baechle <ralf@linux-mips.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Paul Mackerras <paulus@samba.org>,
klibc@zytor.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sys_mmap2 on different architectures
Date: Thu, 23 Feb 2006 17:32:16 +0000 [thread overview]
Message-ID: <20060223173216.GA20322@linux-mips.org> (raw)
In-Reply-To: <43FD2D96.7030600@zytor.com>
On Wed, Feb 22, 2006 at 07:35:50PM -0800, H. Peter Anvin wrote:
> This is what I've found so far: (64-bit architectures excluded)
>
> arm - N/A (PAGE_SHIFT == 12)
> arm26 - MMAP2_PAGE_SHIFT == 12
> cris - MMAP2_PAGE_SHIFT == PAGE_SHIFT (13)
> frv - MMAP2_PAGE_SHIFT == 12
> h8300 - N/A (PAGE_SHIFT == 12)
> i386 - N/A (PAGE_SHIFT == 12)
> m32r - N/A (PAGE_SHIFT == 12)
> m68k - MMAP2_PAGE_SHIFT == PAGE_SHIFT (variable)
> mips - MMAP2_PAGE_SHIFT == PAGE_SHIFT (variable)
A variable which happens to be fixed to 12 in practice. As explained by
Ben the API is only relevant to 32-bit kernels and afaik PAGE_SHIFT
other than 12 has only been successfully been tested on 64-bit kernels.
Ralf
next prev parent reply other threads:[~2006-02-23 17:33 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
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 [this message]
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=20060223173216.GA20322@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=hpa@zytor.com \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).