| commit | dce22c864612659793342bb99bd3d7a91f31afd6 | |
| author | Klaus Jensen <k.jensen@samsung.com> | |
| Tue, 9 Jun 2020 19:03:19 +0000 (9 21:03 +0200) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Wed, 17 Jun 2020 12:53:40 +0000 (17 14:53 +0200) | ||
| tree | 3c5f25a49e8c19d3daf2254679972c56d80d70a7 | treesnapshot (tar.gz zip) |
| parent | ca247d35098d396db25233d5f554bd3098949d60 | commitdiff |
hw/block/nvme: add max_ioqpairs device parameter
The num_queues device paramater has a slightly confusing meaning because
it accounts for the admin queue pair which is not really optional.
Secondly, it is really a maximum value of queues allowed.
Add a new max_ioqpairs parameter that only accounts for I/O queue pairs,
but keep num_queues for compatibility.
Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Keith Busch <kbusch@kernel.org>
Message-Id: <20200609190333.59390-9-its@irrelevant.dk>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
The num_queues device paramater has a slightly confusing meaning because
it accounts for the admin queue pair which is not really optional.
Secondly, it is really a maximum value of queues allowed.
Add a new max_ioqpairs parameter that only accounts for I/O queue pairs,
but keep num_queues for compatibility.
Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Keith Busch <kbusch@kernel.org>
Message-Id: <20200609190333.59390-9-its@irrelevant.dk>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
| hw/block/nvme.c | diffblobblamehistory | |
| hw/block/nvme.h | diffblobblamehistory |