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

[Vu Pham <vuhuong-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>]

Hefty, Sean wrote:
>> Yeah, I guess it's sort of OK.  But is there really no better way to
>> handle this than making users deal with 7 more module parameters?

Do you have other suggestion?

We could have larger default profile which covers *most* known cases with the cost of memory for maintaining ICM page tables; however, there will be still some corner cases with large fabric.


> 
> Is it theoretically possible for these limits to change dynamically?

It requires extra code to clean up resources + reset HCA fw command (same thing to unload/reload driver)

> 
> 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 know if there is an easy way.

For in-band solution, query_sa for total port info records of the fabric would do; however, the driver first need to be up & running with some default profile, then it need to clean up and reset HCA with new learn profile. 

-vu
--
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