Skip to content

Commit e503d58

Browse files
authored
Merge pull request #320 from grondo/rfc20-schedspecific
rfc20: expand description of scheduler specific properties
2 parents 8cdc176 + 47f9078 commit e503d58

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

spec_20.rst

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -175,11 +175,15 @@ The ``execution`` key MAY also contain any of the following optional keys:
175175
! & ' " ^ ` | ( )
176176

177177
Additionally, the ``@`` character is reserved for scheduler specific
178-
property use. Any suffix that appears after the ``@`` character in a
179-
property name SHALL be a scheduler-specific string. For example,
180-
``amd-mi50@gpu``, ``amd-mi50`` SHALL be the property string, but a
181-
scheduler MAY use the ``gpu`` suffix to perform scheduling optimization
182-
for gpus of the corresponding ranks.
178+
property use. In this case, the literal property SHALL still apply
179+
to the defined execution target ranks, but the scheduler MAY use the
180+
suffix after ``@`` to apply the property to children resources of the
181+
execution target or for another scheduler specific purpose. For example,
182+
the property ``amd-mi50@gpu`` SHALL apply to the defined execution
183+
target ranks, but a scheduler MAY use the ``gpu`` suffix to perform
184+
scheduling optimization for gpus of the corresponding ranks. This MAY
185+
result in both ``amd-mi50@gpu`` and ``amd-mi50`` being valid properties
186+
for resources in the instance.
183187

184188
**starttime**
185189
The value of the ``starttime`` key, if present, SHALL

0 commit comments

Comments
 (0)