On 08:25 Sat 16 Jan , Al Chu wrote:
> > > @@ -317,6 +322,11 @@ int main(int argc, char **argv)
> > > mad_rpc_set_timeout(ibmad_port, ibd_timeout);
> > >
> > > node_name_map = open_node_name_map(node_name_map_file);
> > > +
> > > + if (dr_path && load_cache_file) {
> > > + fprintf(stderr, "Cannot specify cache and direct route path\n");
> > > + exit(1);
> > > + }
> >
> > Why is this limitation needed really?
>
> I spoke to Ira about it awhile ago. I think what we decided was that
> while technically you can do a DR path, b/c you can load a cache from
> anywhere in the cluster, you won't know if the DR path is legal or
> correct at point A vs point B. In contrast, the node_guid input is
> valid anywhere you are on the cluster.
But OTOH you have "from" field in the cache. Isn't it used to save an
original discovery point?
> I suppose we could just allow it and the user has to understand this
> fact??
First we need to decide about what this would mean - a path from an
original discovery point or path from a current one.
In any case I think that we can start with disabled direct path option
and re-enable later if it would be useful.
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
