Skip to content

nvmf/rdma: apply TOS on listen and accept - #4

Merged
jleeh merged 2 commits into
rebase/v26.05from
feat/rdma-dscp-priority
Aug 28, 2026
Merged

nvmf/rdma: apply TOS on listen and accept#4
jleeh merged 2 commits into
rebase/v26.05from
feat/rdma-dscp-priority

Conversation

@jleeh

@jleeh jleeh commented Aug 28, 2026

Copy link
Copy Markdown

Summary

  • Add tos to nvmf_create_transport for the RDMA transport (IPv4 TOS / IPv6 TCLASS).
  • Apply it on the listen CM ID before rdma_listen() and on each accepted QP before rdma_accept(), so replica return traffic can share the initiator's DSCP class.
  • 0 keeps the rdma-core default (untagged).

Test plan

  • Build SPDK with --with-rdma=mlx5_dv and confirm nvmf_create_transport accepts tos.
  • nvmf_get_transports reports the configured tos.
  • With tos=96 (priority 3), outbound target packets are DSCP 24; with tos=0 they are untagged.

Made with Cursor

jleeh and others added 2 commits August 28, 2026 09:16
Lets nvmf_create_transport set the IPv4 TOS / IPv6 TCLASS on RDMA listen
IDs and accepted QPs so replica return traffic can share the initiator's
DSCP class. 0 keeps the rdma-core default.

Co-authored-by: Cursor <cursoragent@cursor.com>
JSON decode, rdma_set_option on listen/accept, and dump_opts so the nvmf RDMA TOS path cannot land untested.

Co-authored-by: Cursor <cursoragent@cursor.com>
@jleeh
jleeh merged commit c3ae107 into rebase/v26.05 Aug 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant