User Manual

Features Overview and ConfigurationRev 2.3-1.0.1
Mellanox Technologies
102
Simple QoS Policy Definition
Simple QoS policy definition comprises of a single section denoted by qos-ulps. Similar to the
advanced QoS policy
, it has a list of match rules and their QoS Level, but in this case a match
rule has only one criterion - its goal is to match a certain ULP (or a certain application on top of
this ULP) PR/MPR request, and QoS Level has only one constraint - Service Level (SL).
The simple policy section may appear in the policy file in combine with the advanced policy, or
as a stand-alone policy definition. See more details and list of match rule criteria below
.
Policy File Syntax Guidelines
• Leading and trailing blanks, as well as empty lines, are ignored, so the indentation in the
example is just for better readability
.
• Comments are started with the pound sign (#) and terminated by EOL.
• Any keyword should be the first non-blank in the line, unless it's a comment.
• Keywords that denote section/subsection start have matching closing keywords.
• Having a QoS Level named "DEFAULT" is a must - it is applied to PR/MPR requests
that didn't match any of the matching rules.
• Any section/subsection of the policy file is optional.
Examples of Advanced Policy File
As mentioned earlier, any section of the policy file is optional, and the only mandatory part of the
policy file is a default QoS Level.
Here's an example of the shortest policy file:
qos-levels
qos-level
name: DEFAULT
sl: 0
end-qos-level
end-qos-levels
Port groups section is missing because there are no match rules, which means that port groups are
not referred anywhere, and there is no need defining them. And since this policy file doesn't have
any matching rules, PR/MPR query will not match any rule, and OpenSM will enforce default
QoS level. Essentially, the above example is equivalent to not having a QoS policy file at all.
The following example shows all the possible options and keywords in the policy file and their
syntax:
#
# See the comments in the following example.
# They explain different keywords and their meaning.
#
port-groups
port-group # using port GUIDs