Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NetworkPkg/NvmeOfDxe: Fix SSNS Primary HFI Descriptor Index assignment #33

Conversation

tbzatek
Copy link

@tbzatek tbzatek commented Mar 5, 2024

HfiHeader was always pointing to a head of the HFI Descriptor List and its index was assigned to a SSNS Primary HFI Descriptor Index, effectively always filling it with a value of '1'. The real HFI index to be used was added only as a first Secondary HFI Descriptor Index.

In a multipath scenario where separate SSNS records were defined for every NIC/HFI, this led to connection failures due to mismatched network subnets.

HfiHeader was always pointing to a head of the HFI Descriptor List
and its index was assigned to a SSNS Primary HFI Descriptor Index,
effectively always filling it with a value of '1'. The real HFI
index to be used was added only as a first Secondary HFI
Descriptor Index.

In a multipath scenario where separate SSNS records were defined
for every NIC/HFI, this led to connection failures due
to mismatched network subnets.

Signed-off-by: Tomas Bzatek <tbzatek@redhat.com>
@tbzatek
Copy link
Author

tbzatek commented Mar 5, 2024

This is based on Martin's comment in linux-nvme/libnvme#766 (comment) (as referenced in #29) and I created this patch as an experiment. Turns out it did the trick and made a multipath scenario with separate SSNS records for each HFI testable in Linux at least.

I'm not sure this is entirely correct and only tested the multipath scenario so far.

@rahlvers
Copy link

Fixed in #35 instead.

@rahlvers rahlvers closed this Aug 29, 2024
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.

2 participants