[LU-13385] lnetctl: calculate Lustre traffic service-id Created: 24/Mar/20 Updated: 07/Apr/20 Resolved: 07/Apr/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Amir Shehata (Inactive) | Assignee: | Amir Shehata (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
In order to apply QoS on Lustre traffic , the service-id of the Lustre traffic needs to be added to qos-policy.conf and then mapped to the appropriate service level. There is no good way to identify what the service-id of the Lustre traffic is. This feature adds the ability to find the service-id from lnetctl by doing: lnetctl service-id |
| Comments |
| Comment by Gerrit Updater [ 24/Mar/20 ] |
|
Amir Shehata (ashehata@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/38045 |
| Comment by Gerrit Updater [ 07/Apr/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/38045/ |
| Comment by Peter Jones [ 07/Apr/20 ] |
|
Landed for 2.14 |