From: "Jim Schutt" <jaschut-4OHPYypu0djtX7QSmKvirg@public.gmane.org>
To: Albert Chu <chu11-i2BcT+NCU+M@public.gmane.org>
Cc: "alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org"
<alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [opensm] routing segfault + LMC > 0 routing bug?
Date: Wed, 23 Mar 2011 11:51:47 -0600 [thread overview]
Message-ID: <4D8A3333.4040508@sandia.gov> (raw)
In-Reply-To: <1300902112.3128.147.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
Albert Chu wrote:
> Hey Jim,
>
> On Wed, 2011-03-23 at 09:01 -0700, Jim Schutt wrote:
>> Hi Al,
>>
>> Torus-2QoS's use of port->priv is unique because it persists
>> between routing sweeps. So if another routing engine runs
>> after torus-2QoS and uses port->priv without having ensured
>> that it set it itself, there will be trouble. 9ddcf3419ea
>> was fixing such an issue.
>>
>> I can find only two calls of osm_switch_recommend_path(),
>> and both seem to be to do the right thing, so I think
>> your patch is OK.
>
> Sounds good. When reading over your comments about the 2Qos patches
> that affected this area, I wasn't quite sure how you were dealing with
> the p_port->priv, so I was unsure how my patch would affect things.
>
There's some comments at the top of osm_torus.c,
in the definitions of struct endpoint and struct t_switch,
that describe the rules for how torus-2QoS code can
safely use ->priv.
They may shed some extra light...
-- Jim
--
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:[~2011-03-23 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 1:23 [opensm] routing segfault + LMC > 0 routing bug? Albert Chu
[not found] ` <1300843412.3128.135.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-03-23 13:25 ` Hal Rosenstock
2011-03-23 16:01 ` Jim Schutt
[not found] ` <4D8A1965.40805-4OHPYypu0djtX7QSmKvirg@public.gmane.org>
2011-03-23 17:41 ` Albert Chu
[not found] ` <1300902112.3128.147.camel-akkeaxHeDKRliZ7u+bvwcg@public.gmane.org>
2011-03-23 17:51 ` Jim Schutt [this message]
2011-04-17 14:34 ` Alex Netes
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=4D8A3333.4040508@sandia.gov \
--to=jaschut-4ohpyypu0djtx7qsmkvirg@public.gmane.org \
--cc=alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=chu11-i2BcT+NCU+M@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