Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] O_DIRECT on devices
Date: Mon, 15 Jul 2002 12:29:19 +0100	[thread overview]
Message-ID: <20020715122919.F27706@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20020715074219.18CD54861@dsl2.external.hp.com>; from grundler@dsl2.external.hp.com on Mon, Jul 15, 2002 at 01:42:19AM -0600

On Mon, Jul 15, 2002 at 01:42:19AM -0600, Grant Grundler wrote:
> Randolph and I think most SMP bugs reported (and we seen ourselves)
> suggest a D-cache problem.

Entirely plausible.  PA has bigger virtually indexed caches than anyone
else, so we're more susceptible to cache aliasing bugs than anyone else.
It could be a missing flush somewhere in the arch-independent code.

> My theory is virtual addresses are flushed on one CPU but any data 
> accessed through an aliases on another CPU are not flushed. And then
> we end up with an inconsistency.

it's certainly possible... i don't claim to understand exactly how this
works, but my recollection is that some of the flush instructions are
cpu-local whereas others are global to the system.  you'd have to ask
jsm about it, really.

> We've been reading Documentation/cachetlb.txt and trying
> to understand what it says about virtually indexed caches.

It seems pretty straightforward to me... am I missing something?

> The other thing is we don't hit the problems with PA8500 - only PA8700.
> I'm guessing the aliasing or timing is quite different betweem the two.
> Maybe someone else knows more?

8700 has bigger caches than 8500 and more TLB entries, so it may be
easier to hit problems.

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2002-07-15 11:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11  8:22 [parisc-linux] O_DIRECT on devices Patrick Caulfield
     [not found] ` <3D2D4B4B.4010705@deaprofessionale.it>
2002-07-11  9:35   ` Patrick Caulfield
2002-07-15  2:46 ` Matthew Wilcox
2002-07-15  7:42   ` Grant Grundler
2002-07-15 11:29     ` Matthew Wilcox [this message]
2002-07-15 13:57       ` Patrick Caulfield
2002-07-15 14:10         ` Matthew Wilcox
2002-07-15 14:23           ` Patrick Caulfield
  -- strict thread matches above, loose matches on Subject: below --
2002-08-13 13:23 [parisc-linux] HP9000/L2000 + FC60 Fiber Support António Ribeiro
2002-08-13 13:29 ` Matthew Wilcox
2002-08-15  6:01   ` Grant Grundler
2003-07-18  5:27 [parisc-linux] cvs [login aborted]? Joel Soete
2003-07-18 11:21 ` Matthew Wilcox
2003-07-18 14:44   ` bame

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=20020715122919.F27706@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=grundler@dsl2.external.hp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox