public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Yevgeny Kliteynik <kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 3/3 v2] opensm: connect switches in tree - implemented in up/down
Date: Sun, 06 Dec 2009 11:08:43 +0200	[thread overview]
Message-ID: <4B1B749B.3000506@dev.mellanox.co.il> (raw)
In-Reply-To: <4B1B6CE1.4050802-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>

Yevgeny Kliteynik wrote:
> Hi Sasha,
> 
> Sasha Khapyorsky wrote:
>> On 13:09 Wed 04 Nov     , Yevgeny Kliteynik wrote:
>>> This patch implements connect_switches option in up/down
>>> routing. Also, connect_roots is now handled as a special
>>> case of connect_switches.
>>>
>>> The idea is the following: when clearing hops, preserve
>>> the entries for switches that are above the highest leaf
>>> in the tree.
>>> So if the highest leaf in the tree has rank N, preserve
>>> hops to all the switches with ranks 0 to (N-1).
>>> When connecting roots (--connect_roots option), just set
>>> N to 1.
>>
>> Would this affect multicast routing in sense of a credit loop
>> generation?
> 
> Since I sent these patches, I had it running in various
> simulations and setups, and there are couple of fundamental
> issue with this approach. Basically, what I did here (in up/dn)
> is wrong. Not only for multicast, but for unicast too.
> It interferes with the usual up/down paths routing.
> 
> I will issue V3 of the patches, and it will be only
> connect_roots implementation for fat-tree with the
> two small remarks that you found.

It won't be V3 - it's just one patch that implements
connect_roots in ftree routing.

-- Yevgeny
--
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:[~2009-12-06  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 11:09 [PATCH 3/3 v2] opensm: connect switches in tree - implemented in up/down Yevgeny Kliteynik
     [not found] ` <4AF160D8.9040801-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2009-11-26 15:46   ` Sasha Khapyorsky
2009-12-06  8:35     ` Yevgeny Kliteynik
     [not found]       ` <4B1B6CE1.4050802-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2009-12-06  9:08         ` Yevgeny Kliteynik [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=4B1B749B.3000506@dev.mellanox.co.il \
    --to=kliteyn-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sashak-smomgflXvOZWk0Htik3J/w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox