Page MenuHomeFreeBSD

nvmecontrol: Only do name resolution once for Fabrics connections
ClosedPublic

Authored by jhb on Jan 14 2025, 5:33 PM.
Tags
None
Referenced Files
F174876623: D48456.id150200.diff
Tue, Oct 6, 5:27 PM
Unknown Object (File)
Sat, Oct 3, 12:17 AM
Unknown Object (File)
Tue, Sep 29, 2:30 PM
Unknown Object (File)
Sat, Sep 19, 12:16 PM
Unknown Object (File)
Fri, Sep 11, 3:05 PM
Unknown Object (File)
Sep 3 2026, 2:11 AM
Unknown Object (File)
Aug 28 2026, 2:30 AM
Unknown Object (File)
Aug 22 2026, 10:41 AM
Subscribers

Details

Summary

Reuse the addrinfo structure from the admin queue to establish
connections to I/O queues for the TCP transport.

Sponsored by: Chelsio Communications

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jhb requested review of this revision.Jan 14 2025, 5:33 PM
This revision is now accepted and ready to land.Jan 14 2025, 10:08 PM
dab requested changes to this revision.Jan 18 2025, 1:46 AM
dab added inline comments.
sbin/nvmecontrol/fabrics.c
500–501

Isn't a freeaddrinfo(list); needed here before the return?

Perhaps a new error-out goto label to consolidate the error cases where just that is needed.

This revision now requires changes to proceed.Jan 18 2025, 1:46 AM
sbin/nvmecontrol/fabrics.c
500–501

oh my! I missed this, but I think you're right.

sbin/nvmecontrol/fabrics.c
500–501

Isn't a freeaddrinfo(list); needed here before the return?

Perhaps a new error-out goto label to consolidate the error cases where just that is needed.

Hmmm, if I clear the io[] array earlier, then the existing out label can work for most of these.

This revision is now accepted and ready to land.Jan 24 2025, 1:12 AM