From patchwork Tue Jul 31 16:04:29 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alex Netes X-Patchwork-Id: 1260801 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 A0A26DF26F for ; Tue, 31 Jul 2012 16:05:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755085Ab2GaQF3 (ORCPT ); Tue, 31 Jul 2012 12:05:29 -0400 Received: from mail-vb0-f46.google.com ([209.85.212.46]:52279 "EHLO mail-vb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753818Ab2GaQF2 (ORCPT ); Tue, 31 Jul 2012 12:05:28 -0400 Received: by vbbff1 with SMTP id ff1so5916588vbb.19 for ; Tue, 31 Jul 2012 09:05:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:to:cc:subject:date:message-id:x-mailer :x-gm-message-state; bh=RNcppCRC77EVh7bNVI6aCWThPlcXBlFarVKSik06rw0=; b=JOs/lMgMBNJk2BT84s9DRikNforz/MNn4PS4HM8j5RIu88BfKHs3Tx57JSSpf3+UIA b3d5Q0LORLry/VsFW1njEt14x/lPLoVRxxiwdD/ZRFmOPC3nUGUuvG0dJffxGosC/9xK UNashNYtB3rT3qKKo08xPcWxg3PaAaYvHyxaJ8kaXpj6q9/oX6XkkP/Pu4yhqOS9PChS lt2SgwXZBVzmF+3K81LrnYngWWcNednuVcc49TSf1Bnmfl8mMnnrEmp/epBDdUiKP24w gV+bnDzIs0uTpVa6iHBYs9wPvwcERT7bfJqNItskl7/C1tcmExPIGCEPNq+RTIAvFyAH nuNw== Received: by 10.52.64.146 with SMTP id o18mr12754945vds.55.1343750728024; Tue, 31 Jul 2012 09:05:28 -0700 (PDT) Received: from localhost ([193.47.165.251]) by mx.google.com with ESMTPS id bj6sm415787vdc.12.2012.07.31.09.05.26 (version=SSLv3 cipher=OTHER); Tue, 31 Jul 2012 09:05:27 -0700 (PDT) From: Alex Netes To: linux-rdma@vger.kernel.org Cc: Hal Rosenstock , Alex Netes Subject: [PATCH 01/27] opensm/torus-2QoS: Fix some typos in documentation Date: Tue, 31 Jul 2012 19:04:29 +0300 Message-Id: <1343750695-28063-1-git-send-email-alexne@mellanox.com> X-Mailer: git-send-email 1.7.11.2 X-Gm-Message-State: ALoCoQmfC5kkmZ9/c8pYGTt8UXY+2lO+INwshyCgwMyASPGbm0+kDcQ1rXGWxAnyL35Y4oR73hFy Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org From: Hal Rosenstock Signed-off-by: Hal Rosenstock Signed-off-by: Alex Netes --- doc/current-routing.txt | 6 +++--- man/torus-2QoS.8.in | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/current-routing.txt b/doc/current-routing.txt index 8cc5154..495a0d2 100644 --- a/doc/current-routing.txt +++ b/doc/current-routing.txt @@ -696,7 +696,7 @@ broken by a failure, as in the above example. Torus Topolgy Discovery: -The algorithm used by torus-2QoS to contruct the torus topology from the +The algorithm used by torus-2QoS to construct the torus topology from the undirected graph representing the fabric requires that the radix of each dimension be configured via torus-2QoS.conf. It also requires that the torus topology be "seeded"; for a 3D torus this requires configuring four @@ -710,7 +710,7 @@ links to find the one that is consistent with a face of the cube of switch locations, and adds its swiches to the discovered topology in the correct locations. -Because the algorithm is based on examing the topology of 4-loops of links, +Because the algorithm is based on examining the topology of 4-loops of links, a torus with one or more radix-4 dimensions requires extra initial seed configuration. See torus-2QoS.conf(5) for details. Torus-2QoS will detect and report when it has insufficient configuration for a torus with radix-4 @@ -718,7 +718,7 @@ dimensions. In the event the torus is significantly degraded, i.e., there are many missing switches or links, it may happen that torus-2QoS is unable to place -into the torus some switches and/or links that were discoverd in the +into the torus some switches and/or links that were discovered in the fabric, and will generate a warning in that case. A similar condition occurs if torus-2QoS is misconfigured, i.e., the radix of a torus dimension as configured does not match the radix of that torus dimension as wired, diff --git a/man/torus-2QoS.8.in b/man/torus-2QoS.8.in index c14278a..be74f26 100644 --- a/man/torus-2QoS.8.in +++ b/man/torus-2QoS.8.in @@ -348,7 +348,7 @@ broken by a failure, as in the above example. . .SH TORUS TOPOLOGY DISCOVERY . -The algorithm used by torus-2QoS to contruct the torus topology from +The algorithm used by torus-2QoS to construct the torus topology from the undirected graph representing the fabric requires that the radix of each dimension be configured via torus-2QoS.conf. It also requires that the torus topology be "seeded"; for a 3D torus this @@ -363,7 +363,7 @@ locations, the algorithm examines 4-loops of inter-switch links to find the one that is consistent with a face of the cube of switch locations, and adds its swiches to the discovered topology in the correct locations. .P -Because the algorithm is based on examing the topology of 4-loops of links, +Because the algorithm is based on examining the topology of 4-loops of links, a torus with one or more radix-4 dimensions requires extra initial seed configuration. See torus-2QoS.conf(5) for details. @@ -372,7 +372,7 @@ for a torus with radix-4 dimensions. .P In the event the torus is significantly degraded, \fIi.e.\fR, there are many missing switches or links, it may happen that torus-2QoS is unable -to place into the torus some switches and/or links that were discoverd +to place into the torus some switches and/or links that were discovered in the fabric, and will generate a warning in that case. A similar condition occurs if torus-2QoS is misconfigured, \fIi.e.\fR, the radix of a torus dimension as configured does not match the radix