From: Rolf Manderscheid <rvm-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ibsim: support LID portions of directed-route SMPs
Date: Thu, 11 Aug 2011 15:27:07 -0600 [thread overview]
Message-ID: <4E44492B.6080101@obsidianresearch.com> (raw)
In-Reply-To: <20110809145018.GA2056-iQai9MGU/dze+A/uUDamNg@public.gmane.org>
Hi Alex,
> route_MAD() breaks the LID route support.
I think the change to route_MAD() is sound, there's no change in
behaviour for LID-routed packets. The path argument is expected to be
NULL in the case of a LID routed MAD, which causes an early
return, but this is only an optimization. Even if you forget to pass
in a NULL path (which I did in one case as you pointed out!), the
path->cnt will be zero for LID routed MADs which causes the
direct_route_*_MAD() functions to just return the same port that was
passed in, so it works either way. I tested this with some simple
topologies, running opensm and then doing a perfquery to each
simulated node. I also used python-rdma with a new python simulator
client which is the motivation for this patch. Without this change,
python-rdma exposes the missing handling of leading and/or trailing LIDs
in directed-route SMPs. I'll send an updated patch which passes a
NULL path for LID-routed packets at the second call site.
Rolf
--
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
prev parent reply other threads:[~2011-08-11 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 23:29 [PATCH] ibsim: support LID portions of directed-route SMPs Rolf Manderscheid
[not found] ` <E1QpTpp-00026I-7p-nLM+XIojDeH72zTlGHhC+rDks+cytr/Z@public.gmane.org>
2011-08-09 14:50 ` Alex Netes
[not found] ` <20110809145018.GA2056-iQai9MGU/dze+A/uUDamNg@public.gmane.org>
2011-08-11 21:27 ` Rolf Manderscheid [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=4E44492B.6080101@obsidianresearch.com \
--to=rvm-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=alexne-VPRAkNaXOzVWk0Htik3J/w@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