Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
9223372036854775807
Description
Currently lctl only accepts contiguous LNet ranges for lctl nodemap_add_range and nodemap_del_range. Having lctl translate a user provided non-contiguous LNet range into multiple separate contiguous ranges on the backend could improve the ease of use for the user.
Attachments
Issue Links
Activity
Link | New: This issue is related to EXR-398 [ EXR-398 ] |
Description | Original: Currently lctl only accepts contiguous LNET ranges for nodemap_add_range and nodemap_del_range. Having lctl translate a user provided non-contiguous LNET range into multiple separate contiguous ranges on the backend could improve the ease of use for the user. | New: Currently lctl only accepts contiguous LNet ranges for {{lctl nodemap_add_range}} and {{nodemap_del_range}}. Having {{lctl}} translate a user provided non-contiguous LNet range into multiple separate contiguous ranges on the backend could improve the ease of use for the user. |
Labels | New: nodemap |
Description | Original: Currently lctl only accepts contiguous LNET ranges for nodemap_add_range and nodemap_del_range. Having lctl translate a user provided non-contiguous LNET range into multiple separate contiguous ranges on the backend could increase the ease of use for the user. | New: Currently lctl only accepts contiguous LNET ranges for nodemap_add_range and nodemap_del_range. Having lctl translate a user provided non-contiguous LNET range into multiple separate contiguous ranges on the backend could improve the ease of use for the user. |