Sean Hefty wrote:
This file has *all* the possible keywords.
The administrator really doesn't have to use them all.
For instance, there are three different ways to define port groups:
 - by guid list
 - by node type
 - by port names
You could stick with the guids only - this gives you all the functionality
you need, but by doing so you loose some flexibility.

Beyond referring to port GUIDs, I'm also referring to items like:

sl: 0
mtu-limit: 1
rate-limit: 1
packet-life: 12
path-bits: 2,4,8-32

vlarb-high: 0:255,1:127,2:63,3:31,4:15,5:7,6:3,7:1
vlarb-low: 8:255,9:127,10:63,11:31,12:15,13:7,14:3
vl-high-limit: 10

sl2vl-table: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,7
sl2vl-table: 0,1,1,1,1,1,1,1,1,1,1,1,1,1,1,0

sl: 0
mtu-limit: 1
rate-limit: 1
packet-life: 12
path-bits: 2,4,8-32

This is really low level data, akin to the administrator manually programming the switch tables. My take is that we should drop tons of this flexibility in favor of something much simpler for the administrator.

But again, the administrator doesn't *have* to use all these.
He can simply define sl2vl-tables, and then match service-id
(in qos-match-rules) to a certain sl (in qos-levels).
That's it.
No MTU, rate, packet lifetime or any other low level data.
Does the following file look better?

    port-groups
        port-group
            name: Part1
            port-guid: 0x1000000000000001
            port-guid: 0x1000000000000002
        end-port-group

        port-group
            name: Part2
            port-guid: 0x1000000000000005
            port-guid: 0x1000000000000006
        end-port-group
    end-port-groups

    qos-setup
        sl2vl-tables
            sl2vl-scope
                group: Part1
                from: *
                to: *
                sl2vl-table: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,7
            end-sl2vl-scope
            sl2vl-scope
                group: Part2
                from: *
                to: *
                sl2vl-table: 0,1,2,3,4,5,6,7,8,0,1,2,3,4,0
            end-sl2vl-scope
        end-sl2vl-tables
    end-qos-setup

    qos-levels
        qos-level
            sl: 2
        end-qos-level
        qos-level
            sl: 5
        end-qos-level
    end-qos-levels

    qos-match-rules
        qos-match-rule
            service-id: 4001-5000
            qos-level-sn: 1
        end-qos-match-rule
        qos-match-rule
            service-id: 5001-6000
            qos-level-sn: 2
        end-qos-match-rule
    end-qos-match-rules

-- Yevgeny


- Sean


_______________________________________________
general mailing list
general@lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Reply via email to