d/numam-spdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

nvme: delete outdated comments about xfer size

Browse Source 
This is calculated elsewhere now, so remove the comments around
nvme_qpair_construct calls.

Change-Id: I2dc4956a9e250b88e62038bc55cdd315940ad391
Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
This commit is contained in:
Daniel Verkamp 2015-09-22 09:40:53 -07:00
parent 4f939758ea
commit d7dda8ec63
1 changed files with 0 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
lib/nvme/nvme_ctrlr.c
View File

@ -49,10 +49,6 @@ nvme_ctrlr_construct_admin_qpair(struct nvme_controller *ctrlr)
qpair = &ctrlr->adminq;
/*
* The admin queue's max xfer size is treated differently than the
* max I/O xfer size. 16KB is sufficient here - maybe even less?
*/
rc = nvme_qpair_construct(qpair,
0, /* qpair ID */
NVME_ADMIN_ENTRIES,
@ -106,9 +102,6 @@ nvme_ctrlr_construct_io_qpairs(struct nvme_controller *ctrlr)
/*
* Admin queue has ID=0. IO queues start at ID=1 -
* hence the 'i+1' here.
*
* For I/O queues, use the controller-wide max_xfer_size
* calculated in nvme_attach().
*/
rc = nvme_qpair_construct(qpair,
i + 1, /* qpair ID */