netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sudarsana.kalluru@qlogic.com
Cc: netdev@vger.kernel.org, Yuval.Mintz@qlogic.com
Subject: Re: [PATCH net 1/1] qed: Protect the doorbell BAR with the write barriers.
Date: Wed, 29 Jun 2016 08:16:18 -0400 (EDT)	[thread overview]
Message-ID: <20160629.081618.2206817138199595643.davem@davemloft.net> (raw)
In-Reply-To: <1467114363-16948-1-git-send-email-sudarsana.kalluru@qlogic.com>

From: Sudarsana Reddy Kalluru <sudarsana.kalluru@qlogic.com>
Date: Tue, 28 Jun 2016 07:46:03 -0400

> SPQ doorbell is currently protected with the compilation barrier. Under the
> stress scenarios, we may get into a state where (due to the weak ordering)
> several ramrod doorbells were written to the BAR with an out-of-order
> producer values. Need to change the barrier type to a write barrier to make
> sure that the write buffer is flushed after each doorbell.
> 
> Signed-off-by: Sudarsana Reddy Kalluru <sudarsana.kalluru@qlogic.com>

Applied.

      reply	other threads:[~2016-06-29 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 11:46 [PATCH net 1/1] qed: Protect the doorbell BAR with the write barriers Sudarsana Reddy Kalluru
2016-06-29 12:16 ` David Miller [this message]

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=20160629.081618.2206817138199595643.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Yuval.Mintz@qlogic.com \
    --cc=netdev@vger.kernel.org \
    --cc=sudarsana.kalluru@qlogic.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;
as well as URLs for NNTP newsgroup(s).