From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Line Holen <Line.Holen-UdXhSnd/wVw@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] opensm/osm_sa_path_record.c: livelock in pr_rcv_get_path_parms
Date: Wed, 21 Apr 2010 13:16:42 +0300 [thread overview]
Message-ID: <20100421101641.GD23994@me> (raw)
In-Reply-To: <4BCCA1C5.5000904-UdXhSnd/wVw@public.gmane.org>
On 20:32 Mon 19 Apr , Line Holen wrote:
> >> @@ -69,6 +70,9 @@
> >> #include <opensm/osm_prefix_route.h>
> >> #include <opensm/osm_ucast_lash.h>
> >>
> >> +
> >> +#define MAX_HOPS 128
> >
> > IB spec defines maximal number of hops for a fabric which is 64. Would
> > it be netter to use this value here?
> >
> > Sasha
>
> The value of 128 was chosen as 2x max DR path allowing the SM to be in
> the middle of a fabric. But I have no problem lowering to 64.
The path in this calculation is between ports and SM is not part of the
game.
For me it seems that 64 would be better number. Hypothetically it could
be even unrelated to LFTs transition issue - when path exceeds 64 hops
SA can return NOT FOUND just well.
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
next prev parent reply other threads:[~2010-04-21 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 9:15 [PATCH] opensm/osm_sa_path_record.c: livelock in pr_rcv_get_path_parms Line Holen
[not found] ` <4BCC1F3F.5080000-UdXhSnd/wVw@public.gmane.org>
2010-04-19 15:34 ` Sasha Khapyorsky
2010-04-19 18:32 ` Line Holen
[not found] ` <4BCCA1C5.5000904-UdXhSnd/wVw@public.gmane.org>
2010-04-21 10:16 ` Sasha Khapyorsky [this message]
2010-04-21 10:21 ` Sasha Khapyorsky
2010-04-21 10:40 ` Line Holen
2010-04-19 18:20 ` Hal Rosenstock
[not found] ` <j2uf0e08f231004191120oc1e78130l683b9ae0ca51003a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-04-19 18:48 ` Line Holen
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=20100421101641.GD23994@me \
--to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=Line.Holen-UdXhSnd/wVw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox