From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Khapyorsky Subject: Re: [PATCH] tests/subnet_discover: discover test utility Date: Mon, 21 Dec 2009 09:35:50 +0200 Message-ID: <20091221073550.GB18524@me> References: <20090813204306.dffc3237.weiny2@llnl.gov> <20090816110200.GS25501@me> <20090817083023.da17378b.weiny2@llnl.gov> <20090823120609.GG9547@me> <20090826164026.8dcce4b2.weiny2@llnl.gov> <20091023234349.GK5764@me> <20091220121406.GF5262@me> <20091220182809.f7e17fae.weiny2@llnl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20091220182809.f7e17fae.weiny2-i2BcT+NCU+M@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Ira Weiny Cc: linux-rdma , Al Chu List-Id: linux-rdma@vger.kernel.org Hi Ira, On 18:28 Sun 20 Dec , Ira Weiny wrote: > > Yes, a similar mechanism would work in libibnetdisc. However, it looks like you are doing a depth first search I wouldn't call it so, it is rather "parallel" than "first" depth or breath - discovery continues at first responding node doesn't matter how was it queried in depth or in breath. > which I fear might exceed the path count limit in a DR path? Right, hops count should be limited. I will add this. > Is this how OpenSM works? I think so. The difference is that OpenSM has a limit of outstanding MADs on the wire and subnet_discover doesn't (and there could be a lot of MADs). > I was trying to do a breath first search like ibnetdiscover does. > > > > > Would you like to look at this? > > No problem, I have enclosed the output from a run on Hyperion. > There appears to be a lot of errors. I am not sure what the issue is right off. I have included an ibnetdiscover output for comparision. Thanks. An errors are response timeouts. I guess that most of them are due to switches' VL15 overflow (could be verified by VL15Dropped counter evaluation). Will look at this deeply. Sasha -- 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