[LU-16078] Use different comp_vector with multiple conns_per_peer Created: 05/Aug/22 Updated: 19/Aug/22 Resolved: 19/Aug/22 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Chris Horn | Assignee: | Chris Horn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 9223372036854775807 |
| 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. |
| Comments |
| Comment by Gerrit Updater [ 05/Aug/22 ] |
|
"Chris Horn <chris.horn@hpe.com>" uploaded a new patch: https://review.whamcloud.com/48148 |
| Comment by Gerrit Updater [ 19/Aug/22 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/48148/ |
| Comment by Peter Jones [ 19/Aug/22 ] |
|
Landed for 2.16 |