From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Eli Dorfman <elid-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
Slava Strebkov <slavas-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
Subject: Re: [PATCH RFC] opensm: compress IPV6 SNM groups to use a single MLID
Date: Thu, 26 Nov 2009 18:36:34 +0200 [thread overview]
Message-ID: <20091126163634.GJ13817@me> (raw)
In-Reply-To: <f0e08f230911160735i69ad3671m9a2667900b933e13-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 10:35 Mon 16 Nov , Hal Rosenstock wrote:
> >
> > Unlike previous solution where all IPv6 Solicited node multicast (SNM)
> > requests were collapsed into a single multicast group in OpenSM, now
> > each IPv6 SNM group is represented as a separate multicast group and
> > all groups sharing same P_Key and scope values use a same MLID value.
>
> Shouldn't this also ensure groups sharing MLIDs have the same MTU,
> rate, and packet lifetime ?
For IPv6 SNM it was never implemented, so my rework meets an original
plan.
And in general it is an interesting question. Do we really need to care
about those parameters while doing MGID to MLID compression? SA will
reply properly MGID "based" queries, an "extra" packets will be dropped
anyway, likely sooner is better, no?
> > This solution should be fully IBA complaint.
>
> Why the should qualification ?
Only due to insufficient testing, etc..
> Shouldn't the IBA compliant issues fixed be documented here ?
Yes, but I cannot find where. The only needed change I found is in the
usage message and man page, but there is nothing about IBA compliance.
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:[~2009-11-26 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 6:19 [PATCH] opensm/osm_sa_mcmember_record.c: move mgid allocation code Sasha Khapyorsky
2009-11-13 6:21 ` [PATCH] opensm/osm_sa_member_record.c: mlid independent MGID generator Sasha Khapyorsky
2009-11-13 20:11 ` [PATCH] osm_sa_mcmember_record.c: pass MCM Record data to mlid allocator Sasha Khapyorsky
2009-11-13 20:38 ` [PATCH] complib/cl_fleximap: add cl_fmap_match() function Sasha Khapyorsky
2009-11-13 20:40 ` [PATCH RFC] opensm: compress IPV6 SNM groups to use a single MLID Sasha Khapyorsky
2009-11-16 15:35 ` Hal Rosenstock
[not found] ` <f0e08f230911160735i69ad3671m9a2667900b933e13-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-11-26 16:36 ` Sasha Khapyorsky [this message]
2009-11-26 16:37 ` [PATCH] opensm: IPv6 SNM update for man page and usage Sasha Khapyorsky
2009-11-30 19:48 ` [PATCH RFC] opensm: compress IPV6 SNM groups to use a single MLID Hal Rosenstock
[not found] ` <f0e08f230911301148t8d573c7lf1f67972b5438b72-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-01 14:58 ` Sasha Khapyorsky
2009-12-01 16:00 ` Hal Rosenstock
2009-11-16 15:30 ` [PATCH] complib/cl_fleximap: add cl_fmap_match() function Hal Rosenstock
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=20091126163634.GJ13817@me \
--to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=elid-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=slavas-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=weiny2-i2BcT+NCU+M@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