From: Grant Grundler <grundler@parisc-linux.org>
To: Joel Soete <jsoe0708@tiscali.be>
Cc: Jim Hull <jim.hull@hp.com>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: [parisc-linux-cvs] linux carlos
Date: Fri, 29 Aug 2003 10:13:32 -0600 [thread overview]
Message-ID: <20030829161332.GA22468@dsl2.external.hp.com> (raw)
In-Reply-To: <3F4D78B0000005EE@ocpmta3.freegates.net>
On Fri, Aug 29, 2003 at 05:59:53PM +0200, Joel Soete wrote:
> I just noticed the two following loops:
> flush_data_cache_local:
Note the names of the routines!
ie should only be called when we know only the local CPU is touching
data that needs to be flushed. This sounds like a risky
strategy to me given prefetching can occur to page
that's mapped cacheable.
> Do you think that could be there where the pb occurs?
I don't. There are likely other problems hidden there though.
grant
next prev parent reply other threads:[~2003-08-29 16:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 15:59 [parisc-linux] Re: [parisc-linux-cvs] linux carlos Joel Soete
2003-08-29 16:13 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 16:08 Joel Soete
2003-08-28 16:34 ` Jim Hull
2003-08-29 7:27 ` Joel Soete
2003-08-28 7:04 Joel Soete
2003-08-28 15:12 ` Grant Grundler
2003-08-25 10:03 Joel Soete
2003-08-25 16:45 ` Grant Grundler
2003-08-25 16:50 ` James Bottomley
2003-08-25 19:19 ` Grant Grundler
2003-08-25 19:48 ` James Bottomley
2003-08-26 17:17 ` Carlos O'Donell
2003-08-26 17:54 ` Joel Soete
2003-08-23 15:54 Joel Soete
2003-08-23 19:28 ` Grant Grundler
2003-08-24 12:51 ` Joel Soete
2003-08-24 17:19 ` Grant Grundler
2003-08-25 17:26 ` Joel Soete
2003-08-28 6:08 ` Joel Soete
[not found] <20030820192919.0C20349401C@palinux.hppa>
2003-08-20 19:41 ` Carlos O'Donell
2003-08-21 6:21 ` Joel Soete
[not found] <20021104004626.651BC4829@dsl2.external.hp.com>
2002-11-04 0:58 ` Carlos O'Donell
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=20030829161332.GA22468@dsl2.external.hp.com \
--to=grundler@parisc-linux.org \
--cc=jim.hull@hp.com \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.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.