linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Yuri Tikhonov <yur@emcraft.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] ppc44x: support for 256K PAGE_SIZE
Date: Tue, 23 Oct 2007 15:59:31 +0200	[thread overview]
Message-ID: <6c38f6dc60553ae158e4d3094b879e10@kernel.crashing.org> (raw)
In-Reply-To: <200710222012.20316.yur@emcraft.com>

>>>> The following patch adds support for 256KB PAGE_SIZE on ppc44x-
>>>> based boards.
>>>> The applications to be run on the kernel with 256KB PAGE_SIZE have
>>>> to be
>>>> built using the modified version of binutils, where the MAXPAGESIZE
>>>> definition is set to 0x40000 (as opposite to standard 0x10000).
>>>
>>> Have you measured the performance using a 64kB page size?  If so, how
>>> does it compare with the 256kB page size?
>>
>> I was wondering about this as well?  Isn't this technically in
>> violation of the ABI?
>
>  No it isn't the violation.
>
>  As stated in "System V ABI. PowerPC processor supplement"
> (on which the "Linux Standard Base Core Specification for PPC32"
> is based): " ... Virtual addresses and file offsets for the PowerPC 
> processor family
> segments are congruent modulo 64 Kbytes (0x10000) or larger powers of 
> 2...".
>
>  So, 256 Kbytes is just a larger case.

If I understand you correctly, the only problem with existing binaries
is that the ELF segments are aligned to 64kB, but not necessarily to
256kB.  Couldn't you handle this as a special case, for example by
mapping the "ends" of such an unaligned segment with normal 4kB pages?
That way, a new binutils isn't required to get a big part of the 
benefit,
and importantly, existing shared library binaries will work with your
apps.


Segher

  reply	other threads:[~2007-10-23 13:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18  7:08 [PATCH] ppc44x: support for 256K PAGE_SIZE Yuri Tikhonov
2007-10-18 10:44 ` Josh Boyer
2007-10-18 11:45   ` Benjamin Herrenschmidt
2007-10-18 12:01     ` Josh Boyer
2007-10-18 12:12       ` Benjamin Herrenschmidt
2007-10-18 13:25         ` Yuri Tikhonov
2007-10-23 14:00       ` Segher Boessenkool
2007-10-18 13:18   ` Yuri Tikhonov
2007-10-18 13:25     ` Josh Boyer
2007-10-18 13:30       ` Yuri Tikhonov
2007-10-18 14:41         ` Josh Boyer
2007-10-18 23:21 ` Paul Mackerras
2007-10-19 13:24   ` Kumar Gala
2007-10-22 16:12     ` Yuri Tikhonov
2007-10-23 13:59       ` Segher Boessenkool [this message]
2007-10-23 23:08         ` Paul Mackerras
2007-10-23 23:15       ` Paul Mackerras
2007-10-19 15:37   ` Yuri Tikhonov
2007-10-19 15:48     ` Kumar Gala
2007-10-19 16:03       ` Yuri Tikhonov
2007-10-19 16:36 ` Josh Boyer
2007-10-19 19:04   ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2007-10-18 11:00 Yuri Tikhonov
2007-10-18 11:47 ` Benjamin Herrenschmidt
2007-10-18 13:20   ` Yuri Tikhonov

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=6c38f6dc60553ae158e4d3094b879e10@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=yur@emcraft.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;
as well as URLs for NNTP newsgroup(s).