[PATCH 0/3] Add support for specific Lustre Qos

[sebastien dugue]

  These patches allow to have a specific QoS for Lustre traffic.

   - Patch 1 adds a new Lustre port space to the rdma_cm kernel module

   - Patch 2 defines a new Lustre service ID (matching the new RDMA CMA port
     space) and a new 'lustre' keyword in the OpenSM QoS policy parser.

   - Patch 3 adds a new port_space parameter for the Lustre ko2iblnd kernel
     module that allows to specify the port space to be used by LNET. This
     patch has already been submitted to the Lustre community and is only
     given here as a reference. The relevant discussion is at
     https://bugzilla.lustre.org/show_bug.cgi?id=21732

  In order the exercise QoS using this Lustre port space, the following setup
may be used:

  1. OpenSM configuration - etc/opensm/opensm.conf

    #
    # QoS OPTIONS
    #
    # Enable QoS setup
    qos TRUE
    # QoS policy file to be used
    qos_policy_file /etc/opensm/qos­policy.conf
    # QoS default options
    qos_max_vls    8
    qos_high_limit 1
    qos_vlarb_high 0:0,1:0,2:0,3:0,4:0,5:0
    qos_vlarb_low  0:1,1:16,2:32,3:64,4:1,5:0
    qos_sl2vl      0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15

    The VLARB weights are only indicative.


  2. OpenSM QoS policy configuration - /etc/opensm/qos-policy.conf:

    qos­ulps 
        default                         : 0 # default SL
        lustre, target­port­guid 0x1234 : 1 # lustre traffic to a specific
                                            # port guid (ex MDS traffic)
        lustre                          : 2 # lustre default traffic
    end­qos­ulps 

  3. Lustre module configuration - /etc/modprobe.d/lustre.conf

     Add the following line to all the Lustre nodes:

     options ko2iblnd port_space=339


  Sebastien.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html