diff options
author | Damien Le Moal <dlemoal@kernel.org> | 2025-01-04 07:59:42 +0300 |
---|---|---|
committer | Keith Busch <kbusch@kernel.org> | 2025-01-11 06:30:48 +0300 |
commit | 1eb380caf5275bba1d3d6182dde1fd740f331743 (patch) | |
tree | 7cc84038b872e10e4aec2e1f86f660d0d9acf0f2 /tools/perf/scripts/python/export-to-sqlite.py | |
parent | 43043c9b97258a008b3402cfbbf1c5d82151c77f (diff) | |
download | linux-1eb380caf5275bba1d3d6182dde1fd740f331743.tar.xz |
nvmet: Introduce nvmet_sq_create() and nvmet_cq_create()
Introduce the new functions nvmet_sq_create() and nvmet_cq_create() to
allow a target driver to initialize and setup admin and IO queues
directly, without needing to execute connect fabrics commands.
The helper functions nvmet_check_cqid() and nvmet_check_sqid() are
implemented to check the correctness of SQ and CQ IDs when
nvmet_sq_create() and nvmet_cq_create() are called.
nvmet_sq_create() and nvmet_cq_create() are primarily intended for use
with PCI target controller drivers and thus are not well integrated
with the current queue creation of fabrics controllers using the connect
command. These fabrices drivers are not modified to use these functions.
This simple implementation of SQ and CQ management for PCI target
controller drivers does not allow multiple SQs to share the same CQ,
similarly to other fabrics transports. This is a specification
violation. A more involved set of changes will follow to add support for
this required completion queue sharing feature.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Tested-by: Rick Wertenbroek <rick.wertenbroek@gmail.com>
Tested-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions