Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe: Re-introduce polling for completions
Date: Tue, 5 Apr 2016 17:54:37 +0000	[thread overview]
Message-ID: <20160405175437.GC12625@localhost.localdomain> (raw)
In-Reply-To: <20160405123523.GA19495@infradead.org>

On Tue, Apr 05, 2016@05:35:23AM -0700, Christoph Hellwig wrote:
> So how do any other PCIe device work given that almost no driver does
> unconditionaly polling?

I honestly don't have a good answer to that, and I agree with you
that this shouldn't be necessary ... but this is a harmless way to not
frustrate people who purchase these devices.

I suspect other PCI device drivers either at least try to never use the
legacy IRQ, or they've never been tested in platforms that break them.

> > +	spin_lock_irq(&admin_q->q_lock);
> > +	nvme_process_cq(admin_q);
> > +	spin_unlock_irq(&admin_q->q_lock);
> 
> Add a comment on why this is done.  Given that only the admin queue
> is polled it's going to be a really convoluted explanation which should
> be spelled out in detail.

Sounds good.

  reply	other threads:[~2016-04-05 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 22:24 [PATCH] NVMe: Re-introduce polling for completions Keith Busch
2016-04-05  7:32 ` Johannes Thumshirn
2016-04-05 12:35 ` Christoph Hellwig
2016-04-05 17:54   ` Keith Busch [this message]
2016-04-05 21:39     ` Keith Busch
2016-04-05 22:04       ` Judy Brock-SSI
2016-04-05 22:29         ` Keith Busch
2016-04-06  5:22           ` Judy Brock-SSI
2016-04-06  6:56         ` Christoph Hellwig
2016-04-06  6:56       ` Christoph Hellwig
2016-04-12 19:00       ` Christoph Hellwig
2016-04-12 19:02         ` Christoph Hellwig

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=20160405175437.GC12625@localhost.localdomain \
    --to=keith.busch@intel.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