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
Unknown Object (File)
Fri, Mar 7, 7:01 PM
Unknown Object (File)
Wed, Mar 5, 6:47 PM
Unknown Object (File)
Sun, Mar 2, 11:36 AM
Unknown Object (File)
Fri, Feb 21, 5:28 PM
Unknown Object (File)
Feb 18 2025, 5:52 PM
Unknown Object (File)
Feb 13 2025, 7:32 PM
Unknown Object (File)
Feb 8 2025, 11:16 PM
Unknown Object (File)
Feb 5 2025, 7:24 PM
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