All of lore.kernel.org
 help / color / mirror / Atom feed
From: jgg@ziepe.ca (Jason Gunthorpe)
Subject: [PATCH rfc] nvme-pci: make sure to flush sqe writes before db record update
Date: Thu, 8 Mar 2018 10:20:18 -0700	[thread overview]
Message-ID: <20180308172018.GA6785@ziepe.ca> (raw)
In-Reply-To: <20180308155147.GD3766@localhost.localdomain>

On Thu, Mar 08, 2018@08:51:47AM -0700, Keith Busch wrote:
> On Wed, Mar 07, 2018@07:56:26PM +0200, Sagi Grimberg wrote:
> > @@ -437,8 +437,14 @@ static void __nvme_submit_cmd(struct nvme_queue *nvmeq,
> >  	if (++tail == nvmeq->q_depth)
> >  		tail = 0;
> >  	if (nvme_dbbuf_update_and_check_event(tail, nvmeq->dbbuf_sq_db,
> > -					      nvmeq->dbbuf_sq_ei))
> > +					      nvmeq->dbbuf_sq_ei)) {
> > +		/*
> > +		 * Make sure that descriptors are written before
> > +		 * doorbell record.
> > +		 */
> > +		wmb();
> >  		writel(tail, nvmeq->q_db);
> > +	}
> >  	nvmeq->sq_tail = tail;
> >  }
> 
> If this really is necessary, we'd need this before updating the event
> shadow registers too.
> 
> I'd like to understand this a bit more as we haven't done this in eight
> years and I can't recall any issues around this section. Have we just
> been fortunate that the problem this fixes is extraordinarily unlikely,
> or is something else implicitly ordering within this critical section?

Well, there is a wmb() already inside
nvme_dbbuf_update_and_check_event so any failure would only
be related to dbbuf_sq_db being wrong when tail is written to q_db.

Guessing that might be a basically undetectable situation, maybe some
temporary higher latency or something?

Jason

  reply	other threads:[~2018-03-08 17:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 17:56 [PATCH rfc] nvme-pci: make sure to flush sqe writes before db record update Sagi Grimberg
2018-03-08  7:56 ` Christoph Hellwig
2018-03-08 15:51 ` Keith Busch
2018-03-08 17:20   ` Jason Gunthorpe [this message]
2018-03-08 17:37     ` Keith Busch
2018-03-08 17:56     ` Sagi Grimberg
2018-03-08 18:36       ` Jason Gunthorpe
2018-03-08 18:42         ` Keith Busch
2018-05-30 23:34       ` Sagi Grimberg
2018-05-31  5:47         ` Christoph Hellwig
2018-05-31  7:53           ` Sagi Grimberg
2018-05-31 15:20             ` Jason Gunthorpe

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=20180308172018.GA6785@ziepe.ca \
    --to=jgg@ziepe.ca \
    /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.