Re: [PATCH] mlx4_core: enable changing HCA default max resource limits

On Tue, Nov 22, 2011 at 12:52 PM, Hefty, Sean [off-list ref] wrote:

Is there some easy way for nodes to discover the size of the fabric, so that drivers and applications can adjust their algorithms accordingly?  If not, would such a feature be useful enough to consider approaching the IBTA?

I don't think there's a good correlation between per-HCA resources and size of
the fabric anyway; for example nodes with a lot of memory probably would want
to register a lot of memory independent of the size of the fabric.

(So maybe the limits on memory registration should scale based on system
memory?)

# of QPs, multicast groups etc. is hard to know how to tune... They seem to
be app dependent, rather than dependent on the size of the fabric or the size
of the individual nodes.

But is anyone going to know what RDMARC per QP even means, let along how
to set the value?

As I said before, it's pretty ugly to force users to learn about what
these values
mean, although I don't really have a better solution in mind.

 - R.
--
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