From: Ben Gardiner <BenGardiner@nanometrics.ca>
To: Dan Malek <dan@embeddedalley.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 8xx: Work around CPU15 erratum.
Date: Wed, 14 May 2008 16:17:30 -0400 [thread overview]
Message-ID: <482B48DA.5080300@nanometrics.ca> (raw)
In-Reply-To: <07769C41-66EB-48C5-9494-3BBE34447BBD@embeddedalley.com>
Dan Malek wrote:
>
> On May 14, 2008, at 10:52 AM, Ben Gardiner wrote:
>
>> So there likely are reasons why the following is not possible:
>
> That's way too much code for a tlb exception handler.
> From a system resource perspective, you are much better
> off with a small and efficient piece of tlb loading code,
> always invalidating pages on both ends and taking the
> tlb exception fault. Unfortunately, this could cause some
> thrashing edge cases, so a little intelligence would be
> needed. Exception processing isn't free, and it quickly
> destroys the cache footprint of your application, further
> slowing down the entire system. The tlb reload handler
> goal should be maximum of 8 instructions and 4 memory
> accesses, not 4K of elaborate conditional testing. :-)
>
> Thanks.
>
> -- Dan
>
Hi Dan,
Thanks for the rapid reply :) I really appreciate you giving me an
answer "from the horse's mouth." I would still like to experiment a
little and I'm not really sure it is safe to use any bits in a PTE.
Assuming I was crazy enough to ruin my cache footprint; are there any
three bits in the PTE that are safe to use for some page status
information?
Best Regards,
Ben
prev parent reply other threads:[~2008-05-14 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 14:52 8xx: Work around CPU15 erratum Ben Gardiner
2008-05-14 16:23 ` Dan Malek
2008-05-14 20:17 ` Ben Gardiner [this message]
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=482B48DA.5080300@nanometrics.ca \
--to=bengardiner@nanometrics.ca \
--cc=dan@embeddedalley.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.