linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>
Subject: Re: [PATCH] ppc: Add support for bigger page sizes than 4KB on PPC44x
Date: Tue, 13 Mar 2007 14:54:27 +0100	[thread overview]
Message-ID: <1173794067.24454.78.camel@localhost.localdomain> (raw)
In-Reply-To: <20070313093754.4DE90353A9E@atlas.denx.de>

On Tue, 2007-03-13 at 10:37 +0100, Wolfgang Denk wrote:
> Dear Ben,
> 
> in message <1173769934.24454.67.camel@localhost.localdomain> you wrote:
> >
> >  - It's arch/ppc. We shouldn't do new major features on this codebase.
> > You are welcome however in helping moving over 4xx to arch/powerpc :-)
> 
> Will do that as soon as we have an arch/powerpc port for the 440SP /
> 440SPe

Ah great. I was thinking about working on 440GX after I'm back from the
ski. (I have a Taishan board)

We'll need to look into the MSI problem for SPe I suppose too...
hopefully Michael should have a proper MSI core merged upstream soom
(/me crosses fingers).

> >  - Have you tried other page sizes ? How hard would it be to support 16K
> > and what kind of performance numbers do you get with 16K ? It's a better
> 
> 16 kB should work, but was not tested so far. From our RAID oriented
> calculations it's not interesting.

Fair enough. I still think it would be useful for other workloads to
have that choice though :-)

> We tried 256 kB, but kernel linking fails with a "Not enough room for
> program headers" error message. We will investigate this ASAP, but at
> the moment we have other priorities. [Any hints what might  go  wrong
> are welcome.]

256K will not be doable without serious hacking afaik. Anything above
64K. You won't be able to run most userland apps for example as the
sections are generally 64K aligned.

> Agreed, but this obviously depends  on  the  sort  of  application(s)
> you're running.

Definitely.

Cheers,
Ben.

  reply	other threads:[~2007-03-13 13:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 21:54 [PATCH] ppc: Add support for bigger page sizes than 4KB on PPC44x Stefan Roese
2007-03-13  4:56 ` Paul Mackerras
2007-03-13  5:10   ` David Gibson
2007-03-13  7:12 ` Benjamin Herrenschmidt
2007-03-13  7:37   ` Stefan Roese
2007-03-13  9:37   ` Wolfgang Denk
2007-03-13 13:54     ` Benjamin Herrenschmidt [this message]
2007-03-13  9:42 ` Christoph Hellwig
2007-03-13  9:54   ` David Gibson
2007-03-13 14:00   ` Grant Likely
2007-03-13 14:09     ` Josh Boyer
2007-03-16  5:14 ` Paul Mackerras
  -- strict thread matches above, loose matches on Subject: below --
2007-03-16 13:34 Yuri Tikhonov
2007-03-16 22:34 ` Paul Mackerras
2007-03-17 11:41   ` Yuri Tikhonov
2007-03-21 10:43     ` Paul Mackerras
2007-03-21 11:23       ` Yuri Tikhonov
2007-04-25 17:37       ` Yuri Tikhonov
2007-03-16 13:35 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=1173794067.24454.78.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@denx.de \
    --cc=wd@denx.de \
    /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).