linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Josh Boyer <jwboyer@charter.net>
Cc: Dan Malek <dan@embeddededge.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Large TLBs on 40x
Date: Wed, 11 Aug 2004 08:45:11 -0700	[thread overview]
Message-ID: <20040811084511.A8378@home.com> (raw)
In-Reply-To: <1092232201.32005.4.camel@c68.115.86.108.roc.mn.charter.com>; from jwboyer@charter.net on Wed, Aug 11, 2004 at 08:50:03AM -0500


On Wed, Aug 11, 2004 at 08:50:03AM -0500, Josh Boyer wrote:
> On Tue, 2004-08-10 at 09:35, Matt Porter wrote:
> > On Tue, Aug 10, 2004 at 02:04:44AM -0400, Dan Malek wrote:
> > >
> > > On Aug 9, 2004, at 10:21 PM, Josh Boyer wrote:
> > >
> > > > I have some boards I could test such a patch on.  Or is it a case of
> > > > "this isn't trivial to do"?
> > >
> > > Ummmmm.....what are we talking about here?
> > >
> > > Both MPC8xx, and IBM40x have configuration options for
> > > pinning some (small) amount of kernel space.  You can choose
> > > to enable this if you wish, I don't think it is normally enabled.
> > > I've never found a benchmark that proved either was better,
> > > but I left the code there for others to experiment with.
> >
> > PPC40x no longer has this in 2.6. It has been deprecated by the dynamic
> > large tlb support. He's looking for an option (like nobats) to cause
> > kernel lowmem to not be mapped by large page entries.
> >
> > So, to answer the original question, I would suggest a patch
> > that that uses a 'noltlb' cmdline option, then skips the PPC40x
> > large page mapping in 4xx_mmu.c based on that. See the code
> > that implements 'nobats' for an example.
>
> Hm...  like this?  Against 2.6.8-rc4.

Looks good to me, except we should probably have the cmdline option
be 'noltlbs'...minor nit.

Please repost after reading http://kerneltrap.org/node/view/3180
and agreeing to the DCO by providing a signed off line. Then it
can go into mainline.

Thanks,
Matt

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2004-08-11 15:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 23:05 Large TLBs on 40x Josh Boyer
2004-08-04  0:16 ` Matt Porter
2004-08-04 11:49   ` Josh Boyer
2004-08-04 16:36     ` Dan Malek
2004-08-04 16:39       ` Matt Porter
2004-08-04 17:03         ` Dan Malek
2004-08-10  2:21           ` Josh Boyer
2004-08-10  6:04             ` Dan Malek
2004-08-10 14:35               ` Matt Porter
2004-08-10 14:57                 ` Dan Malek
2004-08-11 13:50                 ` Josh Boyer
2004-08-11 15:30                   ` Dan Malek
2004-08-11 17:58                     ` Josh Boyer
2004-08-11 18:21                       ` Dan Malek
2004-08-11 15:45                   ` Matt Porter [this message]
2004-08-11 17:42                     ` Josh Boyer
2004-08-11 18:16                       ` Dan Malek
2004-08-11 18:38                         ` Matt Porter

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=20040811084511.A8378@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=dan@embeddededge.com \
    --cc=jwboyer@charter.net \
    --cc=linuxppc-embedded@lists.linuxppc.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).