[openib-general] QoS RFC - Resend using a friendly mailer
Sasha Khapyorsky
sashak at voltaire.com
Tue May 30 12:09:36 PDT 2006
Hi Eitan,
First comments...
On 17:53 Tue 30 May , Eitan Zahavi wrote:
>
> 3. Supported Policy
> --------------------
>
> The QoS policy supported by this proposal is divided into 4 sub sections:
>
> * Node Group: a set of HCAs, Routers or Switches that share the same settings.
> A node groups might be a partition defined by the partition manager policy in
> terms of GUIDs. Future implementations might provide support for NodeDescription
> based definition of node groups.
Port/Node groups could be defined as separate configuration, then those
definitions will be shared by different policies like Partitions, QoS (and
maybe others in future).
> * Fabric Setup:
> Defines how the SL2VL and VLArb tables should be setup. This policy definition
> assumes the computation of target behavior should be performed outside of
> OpenSM.
>
> * QoS-Levels Definition:
> This section defines the possible sets of parameters for QoS that a client might
> be mapped to. Each set holds: SL and optionally: Max MTU, Max Rate, Path Bits
> (in case LMC > 0 is used for QoS) and TClass.
>
> * Matching Rules:
> A list of rules that match an incoming PathRecord request to a QoS-Level. The
> rules are processed in order such as the first match is applied. Each rule is
> built out of set of match expressions which should all match for the rule to
> apply. The matching expressions are defined for the following fields
> ** SRC and DST to lists of node groups
> ** Service-ID to a list of Service-ID or Service-ID ranges
> ** TClass to a list of TClass values or ranges
>
> XML style syntax is provided for the policy file.
Why XML? It is not too much readable and writable (by human) format.
Sasha
More information about the general
mailing list