From: keith.busch@intel.com (Keith Busch)
Subject: A NVME command always generates some additional commands?
Date: Mon, 2 Jun 2014 14:08:26 -0600 (MDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1406021342500.11244@AMR> (raw)
In-Reply-To: <CAMjVwgQZQ9R+FD2sPhdLraGhdf-8OrwZngMTQVfVMh1__5QFhg@mail.gmail.com>
On Mon, 2 Jun 2014, Angelo Brito wrote:
> We are developing a NVMe device and your device is under tests right
> now. So we are monitoring what is requested, what is executed and what
> are the answers. Then every time we request a NVMe I/O Command some
> additional 23 I/O Read Commands are generated to read some blocks next
> to the end of our memory or next to the start. Is it an expected
> behavior? I didn't find a reason at the driver for these commands to
> be generated.
Reads are generated everytime you close a block device opened for writing.
next prev parent reply other threads:[~2014-06-02 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 19:32 A NVME command always generates some additional commands? Angelo Brito
2014-06-02 20:08 ` Keith Busch [this message]
2014-06-02 20:51 ` Angelo Brito
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=alpine.LRH.2.03.1406021342500.11244@AMR \
--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