public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Evers <revers@redhat.com>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Matthew Wilcox <matthew@wil.cx>,
	Grant Grundler <grundler@google.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/11] mpt2sas: mpt2sas_base sources
Date: Tue, 03 Mar 2009 22:22:42 -0500	[thread overview]
Message-ID: <49ADF402.4050504@redhat.com> (raw)
In-Reply-To: <660360F4F2570145BD872F298951B17A7689E415@cosmail03.lsi.com>

Moore, Eric wrote:
> On Tuesday, March 03, 2009 2:29 PM, James Bottomley wrote: 
>   
>> On Wed, 2009-02-25 at 14:12 -0700, Matthew Wilcox wrote:
>>     
>>> On Wed, Feb 25, 2009 at 01:27:00PM -0700, Moore, Eric wrote:
>>>       
>>>> What are you suggesting?   Calling wmb()?
>>>>         
>>> PCI writes can be posted, so the him_register writel() may 
>>>       
>> not complete
>>     
>>> for a few thousand cycles.  wmb() isn't going to solve the 
>>>       
>> problem.  A
>>     
>>> readl() from the device would, as would your current solution of
>>> ignoring subsequent interrupts.
>>>       
>> This seems to be the most serious issue with the current 
>> patch set.  If
>> you repost with that fixed, I can put it into scsi-misc and we can
>> address the other issues later.
>>
>>     
>
> I will repost the patch set tommorrow with the following changes
>
> (1) Add readl following writel from the function that disables interrupts
>   
Is a memory barrier required after the writel and before the readl to ensure that 
the writel executes before the readl on processors other than x86_64 and ia32?

> (2) Replace 0xFFFFFFFFFFFFFFFFULL with ~0ULL
>
> (3) when calling pci_enable_msix, only pass one msix entry (instead of 15).  
>
> (4) remove the "current HW implementation uses..... " comment in the sources
>
> (5) merge in a bug fix for SIGIO/POLLIN notifcation reported by the storlib team.
>
> Eric Moore--
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  reply	other threads:[~2009-03-04  3:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  9:32 [PATCH 1/11] mpt2sas: mpt2sas_base sources Eric Moore
2009-02-25  0:00 ` Grant Grundler
2009-02-25 20:27   ` Moore, Eric
2009-02-25 21:12     ` Matthew Wilcox
2009-02-25 22:12       ` Moore, Eric
2009-03-03 18:33         ` Matthew Wilcox
2009-03-03 21:29       ` James Bottomley
2009-03-03 21:49         ` Matthew Wilcox
2009-03-04  0:29         ` Moore, Eric
2009-03-04  3:22           ` Rob Evers [this message]
2009-03-04  3:54             ` Matthew Wilcox
2009-03-03 22:37     ` Grant Grundler

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=49ADF402.4050504@redhat.com \
    --to=revers@redhat.com \
    --cc=Eric.Moore@lsi.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=grundler@google.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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