From: Eric Dumazet <dada1@cosmosbay.com>
To: David Brown <dmlb2000@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PAGE_SIZE Availability Inconsistency
Date: Tue, 06 Mar 2007 00:59:24 +0100 [thread overview]
Message-ID: <45ECAEDC.1090009@cosmosbay.com> (raw)
In-Reply-To: <9c21eeae0703051555x1884fd7cse7968a71ec04eb27@mail.gmail.com>
David Brown a écrit :
> I was rtfc'ing the code one day and noticed somethings about the
> PAGE_SIZE define that is kinda inconsistent around its relative
> location to the __KERNEL__ define.
>
> On some architectures the PAGE_SIZE is outside the __KERNEL__ define
> (i386 and x86_64) and on others its inside the define (ia64 and
> powerpc). I was wondering if this is because the powerpc and ia64
> architectures have dynamic page sizes so that's why they can't export
> PAGE_SIZE outside __KERNEL__.
>
> I'm kinda wondering how I'm supposed to write portable user-space code
> if I want to use the PAGE_SIZE define on different architectures.
The real question is : why do you need PAGE_SIZE from user-space code ?
If it's for mmap() use, you should use getpagesize()
next prev parent reply other threads:[~2007-03-05 23:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 23:55 PAGE_SIZE Availability Inconsistency David Brown
2007-03-05 23:59 ` Eric Dumazet [this message]
2007-03-06 0:01 ` Randy Dunlap
2007-03-06 0:03 ` David Miller
2007-03-06 0:04 ` David Brown
2007-03-06 0:26 ` David Miller
2007-03-06 2:21 ` H. Peter Anvin
2007-03-08 21:08 ` Avi Kivity
2007-03-08 22:21 ` H. Peter Anvin
2007-03-19 19:39 ` Eric W. Biederman
2007-03-06 9:29 ` Christoph Hellwig
2007-03-08 2:18 ` Roman Zippel
2007-03-08 5:28 ` David Brown
2007-03-08 8:32 ` Christoph Hellwig
2007-03-08 9:00 ` Christoph Hellwig
2007-03-08 15:53 ` Arjan van de Ven
2007-03-08 16:08 ` Christoph Hellwig
2007-03-08 16:21 ` Daniel Jacobowitz
2007-03-08 17:05 ` H. Peter Anvin
2007-03-08 17:12 ` Christoph Hellwig
2007-03-08 17:57 ` Anton Blanchard
2007-03-08 18:04 ` H. Peter Anvin
2007-03-08 21:42 ` Anton Blanchard
2007-03-08 21:46 ` Anton Blanchard
2007-03-08 21:48 ` David Miller
2007-03-09 2:43 ` Anton Blanchard
2007-03-09 4:18 ` H. Peter Anvin
2007-03-09 4:27 ` David Miller
2007-03-09 4:31 ` H. Peter Anvin
2007-03-09 4:36 ` David Miller
2007-03-21 2:12 ` Anton Blanchard
2007-03-21 2:48 ` H. Peter Anvin
2007-03-08 22:22 ` H. Peter Anvin
2007-03-08 21:03 ` David Brown
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=45ECAEDC.1090009@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=dmlb2000@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.