[lustre-devel] New wiki documentation

[lustre-devel] New wiki documentation

[Simmons, James A.]

Hello folks

    I have added new documentation to the wiki. The first doc is about the upstream
client which can be found at:

http://wiki.lustre.org/Development#Upstream_contributing

People have also been approaching me about how to get mlx4 hardware working with
mlx5 hardware so I wrote a wiki about what I did at:

http://wiki.lustre.org/Infiniband_Configuration_Howto

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20160504/7042be76/attachment.htm>

[lustre-devel] New wiki documentation

[Dilger, Andreas]

James,
would it make sense/is it possible to have a default module parameters for MLX4 and/or MLX5 in ko2iblnd.conf that "do the right thing" to avoid the need for users to deal with this, or is that not possible due to conflicting requirements between these two drivers?

Cheers, Andreas
--
Andreas Dilger
Lustre Principal Architect
Intel High Performance Data Division

On 2016/05/04, 09:06, "lustre-devel on behalf of Simmons, James A." <lustre-devel-bounces at lists.lustre.org<mailto:lustre-devel-bounces@lists.lustre.org> on behalf of simmonsja at ornl.gov<mailto:simmonsja@ornl.gov>> wrote:

Hello folks

    I have added new documentation to the wiki. The first doc is about the upstream
client which can be found at:

http://wiki.lustre.org/Development#Upstream_contributing

People have also been approaching me about how to get mlx4 hardware working with
mlx5 hardware so I wrote a wiki about what I did at:

http://wiki.lustre.org/Infiniband_Configuration_Howto

[lustre-devel] New wiki documentation

[James Simmons]

> James,
> would it make sense/is it possible to have a default module parameters for MLX4 and/or MLX5 in ko2iblnd.conf that
> "do the right thing" to avoid the need for users to deal with this, or is that not possible due to conflicting
> requirements between these two drivers?

For the stand alone mlx5 case yes we could have ko2iblnd.conf set 
peer_credits=16. As for making mlx5 <-> mlx4 to work together that
requires setting map_on_demand=256 which normally is turned off.
Since we can never know if someone is creating a system with a mix
environment and if we want it to be automatic for the non-power user
then map_ond_demand=256 would have to be apart of the normal
configuration.

One limitation of using the modprobe config for this setup when compared 
to using the DLC yaml configuration file is that with the DLC approach is 
that you can set the LND tunebles per interface. If you use the modprobe 
config file it is global to all IB interfaces on a node. Especially once
multi-rail becomes reality we need to really rethink how to create a
default configuration for the non-power user using DLC.

> Cheers, Andreas
> --
> Andreas Dilger
> Lustre Principal Architect
> Intel High Performance Data Division
> 
> On 2016/05/04, 09:06, "lustre-devel on behalf of Simmons, James A." <lustre-devel-bounces at lists.lustre.org<mailto:lustre-devel-bounces@lists.lustre.org> on behalf of simmonsja at ornl.gov<mailto:simmonsja@ornl.gov>> wrote:
> 
> Hello folks
> 
>     I have added new documentation to the wiki. The first doc is about the upstream
> client which can be found at:
> 
> http://wiki.lustre.org/Development#Upstream_contributing
> 
> People have also been approaching me about how to get mlx4 hardware working with
> mlx5 hardware so I wrote a wiki about what I did at:
> 
> http://wiki.lustre.org/Infiniband_Configuration_Howto
> 
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>