[LU-16078] Use different comp_vector with multiple conns_per_peer

• Type: Improvement
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.16.0
• Assignee: Chris Horn
• Reporter: Chris Horn

Description

kiblnd_get_completion_vector() will always hash multiple connections to the same peer to the same comp_vector. One strategy being deployed in RXE to spread out work is to schedule work based on the comp_vector value. This approach requires o2iblnd to use a different comp_vector with muliple connections going to the same peer.