linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Chris Dumoulin <cdumoulin@ics-ltd.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Pinned TLB entries with 2.6 linux kernel on PPC4xx
Date: Thu, 1 Jun 2006 12:51:29 -0700	[thread overview]
Message-ID: <20060601195129.GA15262@gate.ebshome.net> (raw)
In-Reply-To: <447F4021.5030109@ics-ltd.com>

On Thu, Jun 01, 2006 at 03:29:37PM -0400, Chris Dumoulin wrote:
> Does the idea of creating pinned TLB entries (ones that will never be 
> overwritten) make sense for a PPC4xx (specifically PPC405) 2.6 linux 
> kernel? If so, how would this be accomplished?

44x kernel already pins some TLB entries, 40x may use this approach to 
increase performance (I use this in my internal 2.4 tree 
quite successfully).

Old 2.4 trees (linuxppc-2.4 or devel_2_4) have TLB pinning support 
for 40x, you can look at the implementation there.

-- 
Eugene

  reply	other threads:[~2006-06-01 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 19:29 Pinned TLB entries with 2.6 linux kernel on PPC4xx Chris Dumoulin
2006-06-01 19:51 ` Eugene Surovegin [this message]
2006-06-01 20:53   ` 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=20060601195129.GA15262@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=cdumoulin@ics-ltd.com \
    --cc=linuxppc-embedded@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).