From: Dan Malek <dan@embeddededge.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: CONFIG_PIN_TLB experiments
Date: Tue, 3 May 2005 14:47:28 -0400 [thread overview]
Message-ID: <d81a525fa15c1adfc6774a1e445dde8c@embeddededge.com> (raw)
In-Reply-To: <20050502204259.GB4065@logos.cnet>
On May 2, 2005, at 4:42 PM, Marcelo Tosatti wrote:
> I've been testing the CONFIG_PIN_TLB option under v2.6, results are
> not good.
As you pointed out before, the implementation looks incorrect,
so I'll take a look at it and verify with tests. I'm currently
debugging
some hardware problems with a new 8xx board, when I get over
that I'll look at it.
Thanks.
-- Dan
prev parent reply other threads:[~2005-05-03 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 20:42 CONFIG_PIN_TLB experiments Marcelo Tosatti
2005-05-03 18:14 ` Conn Clark
2005-05-04 19:22 ` Marcelo Tosatti
2005-05-05 16:10 ` Dan Malek
2005-05-05 17:06 ` Conn Clark
2005-05-05 14:11 ` Marcelo Tosatti
2005-05-03 18:47 ` Dan Malek [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=d81a525fa15c1adfc6774a1e445dde8c@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=marcelo.tosatti@cyclades.com \
/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).