A NVME command always generates some additional commands?

[Keith Busch]

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.