0001-add-importance-field-to-resource-allocation-type.patch
proto/sandbox/rst/communicationpatterns/ResourceAllocation.proto | ||
---|---|---|
13 | 13 |
* The type is meant to be exchanged between a scheduling component |
14 | 14 |
* and its clients based on the current state in the allocations life |
15 | 15 |
* cycle. Target resources can be specified by one or more string |
16 |
* identifiers. In order to allow a scheduling component to arbitrate |
|
17 |
* between allocations, also an initiator (human or system), and a |
|
18 |
* conflict resolution strategy have to be specified. |
|
16 |
* identifiers. |
|
17 |
* |
|
18 |
* In order to allow a scheduling component to arbitrate |
|
19 |
* between allocations, also an initiator (human or system), a numerical |
|
20 |
* importance value and a conflict resolution strategy have to be specified. |
|
21 |
* Scheduling components are advised to evaluate information in the following |
|
22 |
* order: |
|
23 |
* i) Prefer a higher priority |
|
24 |
* ii) Prefer a human initiator over a system initiator |
|
25 |
* iii) Prefer a higher importance value |
|
19 | 26 |
* |
20 | 27 |
* @author Patrick Holthaus <patrick.holthaus@uni-bielefeld.de> |
21 | 28 |
*/ |
... | ... | |
189 | 196 |
*/ |
190 | 197 |
required Priority priority = 30; |
191 | 198 | |
199 |
/** |
|
200 |
* Importance of resource allocation. |
|
201 |
* |
|
202 |
* Higher importance values indicate that an allocation attempt should be |
|
203 |
* preferred over attempts with lower importance if both have the same |
|
204 |
* priority and initiator. If no importance value is specified, it's value |
|
205 |
* is assumed to be zero. |
|
206 |
*/ |
|
207 |
optional uint32 importance = 45; |
|
208 | ||
192 | 209 |
/** |
193 | 210 |
* Initiator of resource allocation. |
194 | 211 |
*/ |
195 |
- |