From: Jeremy Higdon <jeremy@sgi.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Michael Reed <mdr@sgi.com>,
pazke@donpac.ru, Michael Joosten <michael.joosten@c-lab.de>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH]: Re: qla1280.c broken on SGI visws, PCI coherency problem
Date: Tue, 13 Dec 2005 17:39:38 -0800 [thread overview]
Message-ID: <20051214013938.GB185272@sgi.com> (raw)
In-Reply-To: <1134485413.3356.2.camel@mulgrave>
On Tue, Dec 13, 2005 at 08:50:13AM -0600, James Bottomley wrote:
> On Tue, 2005-12-13 at 07:22 -0600, Michael Reed wrote:
> > I believe the biggest issue with VISWS is that it appears to need
> > mmiowb() and we likely don't know how to implement it. Hence, for
> > that platform, it would make sense to replace the mmiowb() with a
> > posting read.
>
> Well, there's an easy way to tell ... the reason for the mmiowb in the
> qla1280 driver is supposed to be an SMP race, according to the
> description, so if it fails on UP as well there's something else going
> on here ...
The 320 was available with two CPUs, and though the post doesn't say
what this particular one had, it likely had two. The original post
also indicated a problem with a two-cpu motherboard, though I don't
think that was the 320 (VisWS).
> I'm still suspicious because the mmiowb() in this driver replaced a
> posted write flush instruction, which altered the behaviour of the
> driver. The qla1280 is just rare enough that it might have taken this
> long to notice ...
The 12160 is in most Altix machines and behaves just like a 1280.
If there were a problem with it in this context, we'd know about it.
I'm still betting on the old problem (time moves downward):
cpu A lock
posted pio write X
unlock
cpu B lock
posted pio write Y
unlock
PCI bus retire pio write Y
retire pio write X
The Qlogic architecture doesn't like this.
jeremy
next prev parent reply other threads:[~2005-12-14 1:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 19:11 qla1280.c broken on SGI visws, PCI coherency problem Michael Joosten
2005-12-09 23:48 ` Michael Reed
2005-12-12 21:00 ` [PATCH]: " Michael Reed
2005-12-12 21:24 ` Christoph Hellwig
2005-12-12 21:31 ` Jesse Barnes
2005-12-12 21:47 ` James Bottomley
2005-12-12 23:00 ` Michael Reed
2005-12-13 13:22 ` Michael Reed
2005-12-13 14:50 ` James Bottomley
2005-12-13 18:15 ` Michael Reed
2005-12-14 5:00 ` Michael Joosten
2005-12-14 17:29 ` James Bottomley
2005-12-15 1:17 ` Michael Joosten
2005-12-15 2:20 ` Jeremy Higdon
2005-12-15 16:21 ` Michael Joosten
2005-12-14 1:39 ` Jeremy Higdon [this message]
2005-12-14 3:16 ` Michael Reed
2005-12-14 1:28 ` Jeremy Higdon
2005-12-14 4:59 ` James Bottomley
2005-12-14 23:56 ` Jeremy Higdon
2005-12-15 0:14 ` Michael Reed
2005-12-15 1:13 ` Jeremy Higdon
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=20051214013938.GB185272@sgi.com \
--to=jeremy@sgi.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdr@sgi.com \
--cc=michael.joosten@c-lab.de \
--cc=pazke@donpac.ru \
/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.