public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: mjacob@feral.com
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Andrew Vasquez <praka@san.rr.com>, Andrew Morton <akpm@digeo.com>
Subject: Re: qla2xxx and feral ISP updates in their respective BK trees
Date: Fri, 20 Jun 2003 17:59:45 -0400	[thread overview]
Message-ID: <3EF383D1.7070900@pobox.com> (raw)
In-Reply-To: <20030620113759.B305@wonky.in0.lcl>

Matthew Jacob wrote:
> a) Historically, MMIO has been buggy on ia32. This is no longer the
> case, but there definitely were a lot of platforms with this broken.

Could you elaborate?

What I've mostly found is (in order of frequency):  coders unfamiliar 
with x86 CPU write coalescing/posting rules, and PCI boards whose 
hardware designs contain inherent races when driven in MMIO mode 
(particularly on CPUs with deeply posted writes).


> b) MMIO is consumption of mapping resources, while PIO isn't.

agreed

	Jeff




  reply	other threads:[~2003-06-20 21:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 21:29 qla2xxx and feral ISP updates in their respective BK trees James Bottomley
2003-06-19 15:51 ` Andrew Vasquez
2003-06-20 17:12 ` Matthew Jacob
2003-06-20 17:19   ` James Bottomley
2003-06-20 17:25     ` Matthew Jacob
2003-06-20 18:17       ` James Bottomley
2003-06-20 18:34         ` Jeff Garzik
2003-06-20 18:39           ` Matthew Jacob
2003-06-20 21:59             ` Jeff Garzik [this message]
2003-06-20 22:06               ` Matthew Jacob

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=3EF383D1.7070900@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@digeo.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mjacob@feral.com \
    --cc=praka@san.rr.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