From patchwork Wed Nov 28 19:03:39 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Hal Rosenstock X-Patchwork-Id: 1817931 X-Patchwork-Delegate: alexne@voltaire.com Return-Path: X-Original-To: patchwork-linux-rdma@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork2.kernel.org (Postfix) with ESMTP id D7F3ADF26F for ; Wed, 28 Nov 2012 19:03:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754977Ab2K1TDn (ORCPT ); Wed, 28 Nov 2012 14:03:43 -0500 Received: from mail-bk0-f46.google.com ([209.85.214.46]:61131 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754448Ab2K1TDm (ORCPT ); Wed, 28 Nov 2012 14:03:42 -0500 Received: by mail-bk0-f46.google.com with SMTP id q16so5900875bkw.19 for ; Wed, 28 Nov 2012 11:03:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding:x-gm-message-state; bh=1Jyc+vUQB9bV3tZPMkyhlnAigOq7BAMbdcgWQu5yl3s=; b=cX0waO9JKQoh3D7hrJ++HpJN/knSJ7Xada25eX++CBYo4kU+E/S1+8jMH12OYNKAIy wvxNw7258RwqgLXnJ+aB1UtAzqCl6/Pxtpcb69eCcoJDXy9mjkGRGJTCNsNRxoQopTjm X5saVUVNKV59Z+p1ogIBxPJgfm7knPWBQx8vuzGji0UCclv8zJtLL6aFOxI5ti235RrZ iw5rY41xAg8Y/doqQzOr1V1Nch85zaXaibjmw6JgTIJOiV2G8wIWajZRFn2RBwgR1IYO nxvRU4YBaWWdIzhObj/00DO7JPCjuzFrOBfXwx14BsBLPHIi4iSvlmQB4HVpgNoxQMql VokQ== Received: by 10.204.6.21 with SMTP id 21mr6226979bkx.77.1354129421930; Wed, 28 Nov 2012 11:03:41 -0800 (PST) Received: from [192.168.1.102] (c-71-192-10-85.hsd1.ma.comcast.net. [71.192.10.85]) by mx.google.com with ESMTPS id v8sm13528166bku.6.2012.11.28.11.03.40 (version=SSLv3 cipher=OTHER); Wed, 28 Nov 2012 11:03:41 -0800 (PST) Message-ID: <50B6600B.7040504@dev.mellanox.co.il> Date: Wed, 28 Nov 2012 14:03:39 -0500 From: Hal Rosenstock User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Alex Netes CC: "linux-rdma (linux-rdma@vger.kernel.org)" , Jim Schutt Subject: [PATCH 7/8] opensm: Update doc for changes to torus routing for, endport support X-Gm-Message-State: ALoCoQmfugy+u18H18K8oqA5Z0LABAKxD7knI/+L0YP2bAzNfCLKJHtfkmDqBCv2iM4RwrzaHlkb Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org Change CA links to endport links Signed-off-by: Hal Rosenstock --- 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 .