From: Chris Dumoulin <cdumoulin@ics-ltd.com>
To: linuxppc-embedded@ozlabs.org
Subject: Pinned TLB entries with 2.6 linux kernel on PPC4xx
Date: Thu, 01 Jun 2006 15:29:37 -0400 [thread overview]
Message-ID: <447F4021.5030109@ics-ltd.com> (raw)
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?
Regards,
Chris
--
*--Christopher Dumoulin--*
Software Team Leader
<http://ics-ltd.com/>
<http://ics-ltd.com/>
Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)
------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only.
If misdirected, please notify us by telephone and confirm that it has
been deleted from your system and any hard copies destroyed. You are
strictly prohibited from using, printing, distributing or disseminating
it or any information contained in it save to the intended recipient.
next reply other threads:[~2006-06-01 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 19:29 Chris Dumoulin [this message]
2006-06-01 19:51 ` Pinned TLB entries with 2.6 linux kernel on PPC4xx Eugene Surovegin
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=447F4021.5030109@ics-ltd.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.