Table of Contents
Advertisement
If the adaptation rule is closest, the operational CIR and PIR values will be 87 Kbps and 149 Kbps,
respectively, as those are the closest matches for the administrative values that are even multiples
of the 12.359619 Kbps rate step.
Queue Priority and Weight
On 7210 SAS-X, the priority for the queue can be specified by using the cir-level parameter. The
system maps the cir-level to a pir-level and it is not user configurable. Cir-level parameter defines
the scheduling priority of the queue in the CIR loop and the PIR loop (the system assigns the
priority for the queue based on its cir-level).
Cir-level value of 8, represents the highest priority. Additionally, the scheduler always provides
the configured bandwidth (CIR = PIR) for the queues assigned value (if bandwidth is available),
irrespective of whether the CIR of other queues are met or not. In other words, CIR rate of level-8
queues in the system are provisioned before provisioning the CIR rate of queues at the other levels.
PIR configured for queues at this level are ignored by the system. The user can also specify the
weight for the queue. The weight parameter is used to determine the proportion of the available
bandwidth that is allocated to the queues vying for bandwidth at the same priority.
On 7210 SAS-R6, the user has an option to specify whether the SAP egress queue is a strict queue
or a weighted queue. The priority of the queue is determined by the FC of the queue, with higher
priority FC being at a higher priority. The user can specify the weight of the queue for weighted
queue. The weight parameter is used to determine the proportion of the available bandwidth that is
allocated to the queues vying for bandwidth at the same priority.
7210 SAS-X and 7210 SAS-R6 OS Quality of Service Guide
QoS Policies
Page 43
Advertisement
Table of Contents
