Change CA links to endport links Signed-off-by: Hal Rosenstock <[email protected]> --- doc/current-routing.txt | 19 ++++++++++--------- man/torus-2QoS.8.in | 19 ++++++++++--------- 2 files changed, 20 insertions(+), 18 deletions(-)
diff --git a/doc/current-routing.txt b/doc/current-routing.txt index c984801..dcd64a7 100644 --- a/doc/current-routing.txt +++ b/doc/current-routing.txt @@ -748,21 +748,22 @@ will be ignored, and a warning will be generated. For inter-switch links, Torus-2QoS uses VL values 0-3 to implement one of its supported QoS levels, and VL values 4-7 to implement the other. For -CA links, Torus-2QoS uses VL value 0 for one of its supported QoS -levels and VL value 1 to implement the other. Hard-to-diagnose application -issues may arise if traffic is not delivered fairly across each of these -two VL ranges. For inter-switch links, Torus-2QoS will detect and warn if -VL arbitration is configured unfairly across VLs in the range 0-3, and also -in the range 4-7. Note that the default OpenSM VL arbitration configuration -does not meet this constraint, so all torus-2QoS users should configure VL +endport links (CA, router, switch management port), Torus-2QoS uses VL +value 0 for one of its supported QoS levels and VL value 1 to implement +the other. Hard-to-diagnose application issues may arise if traffic is +not delivered fairly across each of these two VL ranges. For +inter-switch links, Torus-2QoS will detect and warn if VL arbitration is +configured unfairly across VLs in the range 0-3, and also in the range +4-7. Note that the default OpenSM VL arbitration configuration does +not meet this constraint, so all torus-2QoS users should configure VL arbitration via qos_ca_vlarb_high, qos_swe_vlarb_high, qos_ca_vlarb_low, qos_swe_vlarb_low, etc. Note that torus-2QoS maps SL values to VL values differently -for inter-switch and CA links. This is why qos_vlarb_high and +for inter-switch and endport links. This is why qos_vlarb_high and qos_vlarb_low should not be used, as using them may result in VL arbitration for a QoS level being different across inter-switch -links vs. across CA links. +links vs. across endport links. Operational Considerations: diff --git a/man/torus-2QoS.8.in b/man/torus-2QoS.8.in index d62beba..f192066 100644 --- a/man/torus-2QoS.8.in +++ b/man/torus-2QoS.8.in @@ -406,21 +406,22 @@ torus-2QoS, any configuration via qos_sl2vl, qos_swe_sl2vl, .P For inter-switch links, Torus-2QoS uses VL values 0-3 to implement one of its supported QoS levels, and VL values 4-7 to implement the other. For -CA links, Torus-2QoS uses VL value 0 for one of its supported QoS -levels and VL value 1 to implement the other. Hard-to-diagnose application -issues may arise if traffic is not delivered fairly across each of these -two VL ranges. For inter-switch links, Torus-2QoS will detect and warn if -VL arbitration is configured unfairly across VLs in the range 0-3, and also -in the range 4-7. Note that the default OpenSM VL arbitration configuration -does not meet this constraint, so all torus-2QoS users should configure VL +endport links (CA, router, switch management port), Torus-2QoS uses VL +value 0 for one of its supported QoS levels and VL value 1 to implement +the other. Hard-to-diagnose application issues may arise if traffic is +not delivered fairly across each of these two VL ranges. For +inter-switch links, Torus-2QoS will detect and warn if VL arbitration is +configured unfairly across VLs in the range 0-3, and also in the range +4-7. Note that the default OpenSM VL arbitration configuration does +not meet this constraint, so all torus-2QoS users should configure VL arbitration via qos_ca_vlarb_high, qos_swe_vlarb_high, qos_ca_vlarb_low, qos_swe_vlarb_low, \fIetc.\fR .P Note that torus-2QoS maps SL values to VL values differently -for inter-switch and CA links. This is why qos_vlarb_high and +for inter-switch and endport links. This is why qos_vlarb_high and qos_vlarb_low should not be used, as using them may result in VL arbitration for a QoS level being different across inter-switch -links vs. across CA links. +links vs. across endport links. . .SH OPERATIONAL CONSIDERATIONS . -- 1.7.8.2 -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
