All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Joosten <michael.joosten@c-lab.de>
To: Jeremy Higdon <jeremy@sgi.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Michael Reed <mdr@sgi.com>,
	pazke@donpac.ru, linux-scsi@vger.kernel.org
Subject: Re: [PATCH]: Re: qla1280.c broken on SGI visws,	PCI	coherency	problem
Date: Thu, 15 Dec 2005 17:21:24 +0100	[thread overview]
Message-ID: <43A19804.1050100@c-lab.de> (raw)
In-Reply-To: <20051215022021.GC192359@sgi.com>

Jeremy Higdon wrote:

>On Thu, Dec 15, 2005 at 02:17:38AM +0100, Michael Joosten wrote:
>  
>
>>>Btw, the VisWS Linux port apparently uses non-coherent DMA.  Perhaps it
>>>should be switched to coherent DMA, as there could be bugs in that area
>>>with qla1280.
>>>      
>>>
>>Aha, so we are back at coherence, but it's not MP, but DMA one...
>>(I'm not sure what is meant with DMA coherence - make sure that before a 
>>DMA transfer is started at least the related CPU cache lines (in the DMA 
>>address range) are written back?)
>>    
>>
>
>For a start.  You need to invalidate before read into memory and write
>back before write to disk.  You also need to make sure that the memory
>stays out of the CPU cache during the DMA (so you need to make sure that
>when you DMA into memory that nothing is loading or storing to a cacheline
>that you're DMA'ing into.  On a speculative execution CPU, this is really
>hard.
>  
>
Aha. Thanks for the info, now I can figure what's going on.

>>in qla1280_32/64bit_start_scsi().
>>    
>>
>
>We're going to work on an API change to mmiowb() instead.
>
>  
>
OK. From my point, this has been settled and I'll stay tuned to test a 
patch. It's not urgent.

Thanks for the lively discussion and some insights, Michael


  reply	other threads:[~2005-12-15 16:28 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 [this message]
2005-12-14  1:39             ` Jeremy Higdon
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=43A19804.1050100@c-lab.de \
    --to=michael.joosten@c-lab.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=jeremy@sgi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdr@sgi.com \
    --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.