From: keith.busch@intel.com (Keith Busch)
Subject: guaranteed progress for NVME commands?
Date: Tue, 22 Mar 2016 17:57:28 +0000 [thread overview]
Message-ID: <20160322175727.GA4188@localhost.localdomain> (raw)
In-Reply-To: <20160322144615.GA24460@localhost.localdomain>
On Tue, Mar 22, 2016@02:46:16PM +0000, Keith Busch wrote:
> I'm not sure why the driver is even considering that.
> The transfer size doesn't matter; only nr_phys_segments should determine how
> many elements the nvme_iod sgl needs to have.
err, scratch that. The size has to be accounted for when considering
PRP lists, which are unnamed fields in struct nvme_iod.
prev parent reply other threads:[~2016-03-22 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 7:45 guaranteed progress for NVME commands? Christoph Hellwig
2016-03-22 14:46 ` Keith Busch
2016-03-22 17:57 ` Keith Busch [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=20160322175727.GA4188@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