linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc44x: support for 256K PAGE_SIZE
Date: Thu, 18 Oct 2007 21:45:14 +1000	[thread overview]
Message-ID: <1192707914.12879.51.camel@pasglop> (raw)
In-Reply-To: <1192704248.13993.36.camel@localhost.localdomain>


On Thu, 2007-10-18 at 05:44 -0500, Josh Boyer wrote:
> On Thu, 2007-10-18 at 11:08 +0400, Yuri Tikhonov wrote:
> >  Hello,
> > 
> >  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).
> 
> Sorry, this is against arch/ppc which is bug fix only.  New features
> should be done against arch/powerpc.  Also, I'd rather see something
> along the lines of hugetlbfs support instead.

I slightly disagree on that one. It does make sense in embedded
applications to use larger page sizes like that to compensate for small
TLBs, and hugetlbfs has serious constraints that may well make it
impractical.

Based on that, I'd be tempted to let that in provided it doesn't
requires ugly hacks, which seems to be the case. It still needs to be
adapted to arch/powerpc however, and get closer scrutiny that I didn't
have time to do yet.

You are the maintainer, so you decide, but my opinion here is that
wanting that is fair enough.

Cheers,
Ben.

  reply	other threads:[~2007-10-18 11:45 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 [this message]
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
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=1192707914.12879.51.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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).