From: Dan Malek <dan@embeddededge.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Joakim Tjernlund <joakim.tjernlund@lumentis.se>,
linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: How to fix 8xx dcbst bug?
Date: Sat, 7 May 2005 21:10:17 -0400 [thread overview]
Message-ID: <52dc3ae70f883699b1e48b7d742afcaf@embeddededge.com> (raw)
In-Reply-To: <20050506154539.GA6452@logos.cnet>
On May 6, 2005, at 11:45 AM, Marcelo Tosatti wrote:
>
> Hi Dan,
>
> So, restarting this conversation...
One of the things I don't want to lose sight of during
all of this is the real performance problem in 2.6.
Your test results show there is something that needs
attention, regardless of using pinned entries. We
need to continue some of this investigation, it
affects all processors.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-05-08 1:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 15:45 How to fix 8xx dcbst bug? Marcelo Tosatti
2005-05-07 18:24 ` Joakim Tjernlund
2005-05-07 13:57 ` Marcelo Tosatti
2005-05-07 18:39 ` Wolfgang Denk
2005-05-07 22:47 ` Joakim Tjernlund
2005-05-08 1:00 ` Dan Malek
2005-05-08 1:10 ` Dan Malek [this message]
2005-05-07 21:47 ` Marcelo Tosatti
2005-05-09 19:25 ` Dan Malek
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=52dc3ae70f883699b1e48b7d742afcaf@embeddededge.com \
--to=dan@embeddededge.com \
--cc=joakim.tjernlund@lumentis.se \
--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).