From patchwork Thu Nov 8 16:22:37 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ira Weiny X-Patchwork-Id: 1716441 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 6A5D6DF280 for ; Thu, 8 Nov 2012 16:22:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756286Ab2KHQWi (ORCPT ); Thu, 8 Nov 2012 11:22:38 -0500 Received: from prdiron-2.llnl.gov ([128.15.143.172]:48036 "EHLO prdiron-2.llnl.gov" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756284Ab2KHQWi (ORCPT ); Thu, 8 Nov 2012 11:22:38 -0500 X-Attachments: Received: from eris.llnl.gov (HELO trebuchet.chaos) ([128.115.7.7]) by prdiron-2.llnl.gov with SMTP; 08 Nov 2012 08:22:37 -0800 Date: Thu, 8 Nov 2012 08:22:37 -0800 From: Ira Weiny To: "linux-rdma@vger.kernel.org" Cc: Alex Netes Subject: [PATCH] opensm: update performance manager documentation Message-Id: <20121108082237.74d8a7fe8b310be6cbfd68a0@llnl.gov> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.18.9; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Sender: linux-rdma-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org Signed-off-by: Ira Weiny --- doc/performance-manager-HOWTO.txt | 35 ++++++++--------------------------- 1 files changed, 8 insertions(+), 27 deletions(-) diff --git a/doc/performance-manager-HOWTO.txt b/doc/performance-manager-HOWTO.txt index 11f4185..7471c6f 100644 --- a/doc/performance-manager-HOWTO.txt +++ b/doc/performance-manager-HOWTO.txt @@ -45,23 +45,13 @@ Using the Performance Manager consists of 3 steps: Step 1: Compile in support for the Performance Manager ------------------------------------------------------ -Because of the performance manager's experimental status, it is not enabled at -compile time by default. (This will hopefully soon change as more people use -it and confirm that it does not break things... ;-) The configure option is -"--enable-perf-mgr". - At this time it is really best to enable the console socket option as well. -OpenSM can be run in an "interactive" mode. But with the console socket option -turned on one can also make a connection to a running OpenSM. The console -option is "--enable-console-socket". This option requires the use of -tcp_wrappers to ensure security. Please be aware of your configuration for -tcp_wrappers as the commands presented in the console can affect the operation -of your subnet. - -The following configure line includes turning on the performance manager as -well as the console: - - ./configure --enable-perf-mgr --enable-console-socket +OpenSM can be run in an "interactive" mode. But with the console socket +option turned on one can also make a connection to a running OpenSM. By +default only "loopback" is enabled with the console with socket being a +compile time option. Regardless, please be aware of your network security +configuration for as the commands presented in the console can affect the +operation of your subnet. Step 2: Enable the perfmgr and console in opensm.conf @@ -83,23 +73,14 @@ the opensm.conf config file. (Default location is Also enable the console socket and configure the port for it to listen to if desired. - # console [off|local|socket] + # console [off|local|loopback] console socket # Telnet port for console (default 10000) console_port 10000 -As noted above you also need to set up tcp_wrappers to prevent unauthorized -users from connecting to the console.[*] - - [*] As an alternate you can use the loopback mode but I noticed when - writing this (OpenSM v3.1.10; OFED 1.3) that there are some bugs in - specifying the loopback mode in the opensm.conf file. Look for this to - be fixed in newer versions. + "local" is only useful if you run OpenSM in the foreground. - [**] Also you could use "local" but this is only useful if you run - OpenSM in the foreground of a terminal. As OpenSM is usually started - as a daemon I left this out as an option. Step 3: retrieve data which has been collected ----------------------------------------------