All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Chu <chu11-i2BcT+NCU+M@public.gmane.org>
To: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Jared Carr <jared.carr-Y2zl/4KMd60@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [opensm] RFC: new routing options (repost)
Date: Wed, 06 Jul 2011 09:54:34 -0700	[thread overview]
Message-ID: <1309971274.11479.53.camel@auk59.llnl.gov> (raw)
In-Reply-To: <20110706080736.GD18903-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>

Hi Alex,

On Wed, 2011-07-06 at 01:07 -0700, Alex Netes wrote:
> Hi Al,
> 
> On 10:46 Tue 05 Jul     , Albert Chu wrote:
> > Hi Alex,
> > 
> > On Tue, 2011-07-05 at 10:07 -0700, Alex Netes wrote:
> > > Hi Al,
> > > 
> > > On 09:53 Tue 05 Jul     , Albert Chu wrote:
> > > > Hi Alex,
> > > > 
> > > > Thanks.  Are you still reviewing the remote_guid_sorting patch (the 2/4
> > > > patch)?  Or do you feel there is work there that needs to be done?
> > > > 
> > > 
> > > I thought we agreed that same goal could be achieved using
> > > route_port_ordering_file (dimn_ports_file) parameter, which is more general
> > > than remote_guid_sorting.
> > 
> > The route_port_ordering_file is capable of doing it, however the
> > complexity of setting it up would be far past the knowledge base for the
> > average system administrator.  It would be far more difficult than
> > setting up the 'guid_routing_order' file or 'dimn_ports_file' for DOR.
> > 
> > To me, the generic 'route_port_ordering_file' is an option most useful
> > for special cases.
> > 
> > We've been using 'remote_guid_sorting' for almost a year now on multiple
> > clusters.  Without much effort, it gives all the clusters a nice 5-7%
> > speedup.
> > 
> 
> I understand that using guid_routing_order, improves performance. I just
> think, that 'guid_routing_order' can bring benefit in a rear cases. What if
> someone would think that reverse guid routing or any other function on peers
> node GUIDs ports will improve its' performance, should we keep all of these
> options?

Good point.  I suppose we have to draw the line somewhere on cutting off
options.  We'll just keep the patch in-house b/c it'll be easier for the
staff.

Al

> I created a simple script, that prepares route_port_ordering file from
> ibnetdiscover. It sorts switches ports, based on a remote peer GUIDs.
> It's pretty nit, but it does the job.
> 
> #!/bin/bash
> 
> IBNET_OUT="/tmp/port_ordering_ibnetdisocver"
> TMP_FILE="/tmp/port_order_tmp"
> 
> switch=0
> skip=0
> 
> `ibnetdiscover > $IBNET_OUT`
> while read line
> do
> 	is_switch_header=`echo $line | grep -c ^Switch`
> 	if [ $is_switch_header -eq 1 ]; then
> 		guid=`echo $line | awk '{ print "0x" substr($3, 4, 16)}'`
> 		switch=1
> 		skip=0
> 	elif [ $switch -eq 1 -a "$line" == "" ]; then
> 		switch=0
> 		skip=1
> 		echo $guid `sort $TMP_FILE | awk '{print $2}' | xargs`
> 		rm -fr $TMP_FILE
> 	elif [ $switch -eq 1 ]; then
> 		echo $line | grep "S-" | awk '{print "0x" substr($2, 4, 16) " " substr($1,2,match($1,"]")-2)}' >> $TMP_FILE
> 	fi
> done < $IBNET_OUT
> 
> rm -fr $IBNET_OUT
> 
> -- Alex
-- 
Albert Chu
chu11-i2BcT+NCU+M@public.gmane.org
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-07-06 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11  1:33 [opensm] RFC: new routing options (repost) Albert Chu
     [not found] ` <1297388014.18394.302.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-03-23 21:31   ` Albert Chu
     [not found]     ` <1300915898.3128.168.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-04-06 14:09       ` Alex Netes
     [not found]         ` <20110406140929.GA21920-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-04-06 18:14           ` Albert Chu
     [not found]             ` <1302113667.4906.336.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-04-07  0:56               ` Albert Chu
     [not found]                 ` <1302137816.4906.403.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-04-11 21:24                   ` Carr, Jared F
2011-07-04 10:52                   ` Alex Netes
     [not found]                     ` <20110704105259.GA6084-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-07-05 16:53                       ` Albert Chu
     [not found]                         ` <1309884814.11479.29.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-07-05 17:07                           ` Alex Netes
     [not found]                             ` <20110705170738.GC18903-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-07-05 17:46                               ` Albert Chu
     [not found]                                 ` <1309887969.11479.48.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-07-06  8:07                                   ` Alex Netes
     [not found]                                     ` <20110706080736.GD18903-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-07-06 16:54                                       ` Albert Chu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1309971274.11479.53.camel@auk59.llnl.gov \
    --to=chu11-i2bct+ncu+m@public.gmane.org \
    --cc=alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=jared.carr-Y2zl/4KMd60@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.