25. MVPP2 Poll Mode Driver

25.5.1. Configuration syntax

[port <portnum> default]
default_tc = <default_tc>
mapping_priority = <mapping_priority>
policer_enable = <policer_enable>
token_unit = <token_unit>
color = <color_mode>
cir = <cir>
ebs = <ebs>
cbs = <cbs>

rate_limit_enable = <rate_limit_enable>
rate_limit = <rate_limit>
burst_size = <burst_size>

[port <portnum> tc <traffic_class>]
rxq = <rx_queue_list>
pcp = <pcp_list>
dscp = <dscp_list>
default_color = <default_color>

[port <portnum> tc <traffic_class>]
rxq = <rx_queue_list>
pcp = <pcp_list>
dscp = <dscp_list>

[port <portnum> txq <txqnum>]
sched_mode = <sched_mode>
wrr_weight = <wrr_weight>

rate_limit_enable = <rate_limit_enable>
rate_limit = <rate_limit>
burst_size = <burst_size>

Where:

• <portnum>: DPDK Port number (0..n).
• <default_tc>: Default traffic class (e.g. 0)
• <mapping_priority>: QoS priority for mapping (ip, vlan, ip/vlan or vlan/ip).
• <traffic_class>: Traffic Class to be configured.
• <rx_queue_list>: List of DPDK RX queues (e.g. 0 1 3-4)
• <pcp_list>: List of PCP values to handle in particular TC (e.g. 0 1 3-4 7).
• <dscp_list>: List of DSCP values to handle in particular TC (e.g. 0-12 32-48 63).
• <policer_enable>: Enable ingress policer.
• <token_unit>: Policer token unit (bytes or packets).
• <color_mode>: Policer color mode (aware or blind).
• <cir>: Committed information rate in unit of kilo bits per second (data rate) or packets per second.
• <cbs>: Committed burst size in unit of kilo bytes or number of packets.
• <ebs>: Excess burst size in unit of kilo bytes or number of packets.
• <default_color>: Default color for specific tc.
• <rate_limit_enable>: Enables per port or per txq rate limiting.
• <rate_limit>: Committed information rate, in kilo bits per second.
• <burst_size>: Committed burst size, in kilo bytes.
• <sched_mode>: Egress scheduler mode (wrr or sp).
• <wrr_weight>: Txq weight.

Setting PCP/DSCP values for the default TC is not required. All PCP/DSCP values not assigned explicitly to particular TC will be handled by the default TC.

[port 0 default]
default_tc = 0
mapping_priority = ip

rate_limit_enable = 1
rate_limit = 1000
burst_size = 2000

[port 0 tc 0]
rxq = 0 1

[port 0 txq 0]
sched_mode = wrr
wrr_weight = 10

[port 0 txq 1]
sched_mode = wrr
wrr_weight = 100

[port 0 txq 2]
sched_mode = sp

[port 0 tc 1]
rxq = 2
pcp = 5 6 7
dscp = 26-38

[port 1 default]
default_tc = 0
mapping_priority = vlan/ip

policer_enable = 1
token_unit = bytes
color = blind
cir = 100000
ebs = 64
cbs = 64

[port 1 tc 0]
rxq = 0
dscp = 10

[port 1 tc 1]
rxq = 1
dscp = 11-20

[port 1 tc 2]
rxq = 2
dscp = 30

[port 1 txq 0]
rate_limit_enable = 1
rate_limit = 10000
burst_size = 2000

./testpmd --vdev=eth_mvpp2,iface=eth0,iface=eth2,cfg=/home/user/mrvl.conf \
  -c 7 -- -i -a --disable-hw-vlan-strip --rxq=3 --txq=3

25.7.1. Supported flow actions

Following flow action items are supported by the driver:

• DROP
• QUEUE

25.7.2. Supported flow items

Following flow items and their respective fields are supported by the driver:

• ETH
  • source MAC
  • destination MAC
  • ethertype
• VLAN
  • PCP
  • VID
• IPV4
  • DSCP
  • protocol
  • source address
  • destination address
• IPV6
  • flow label
  • next header
  • source address
  • destination address
• UDP
  • source port
  • destination port
• TCP
  • source port
  • destination port

25.7.3. Classifier match engine

Classifier has an internal match engine which can be configured to operate in either exact or maskable mode.

Mode is selected upon creation of the first unique flow rule as follows:

• maskable, if key size is up to 8 bytes.
• exact, otherwise, i.e for keys bigger than 8 bytes.

Where the key size equals the number of bytes of all fields specified in the flow items.

From the user perspective maskable mode means that masks specified via flow rules are respected. In case of exact match mode, masks which do not provide exact matching (all bits masked) are ignored.

If the flow matches more than one classifier rule the first (with the lowest index) matched takes precedence.

25.7.4. Flow rules usage example

Before proceeding run testpmd user application:

./testpmd --vdev=eth_mvpp2,iface=eth0,iface=eth2 -c 3 -- -i --p 3 -a --disable-hw-vlan-strip

testpmd> flow create 0 ingress pattern eth src is 10:11:12:13:14:15 / end actions drop / end

testpmd> flow create 0 ingress pattern ipv4 src spec 10.10.10.0 src mask 255.255.255.0 / tcp src spec 0x10 src mask 0x10 / end action drop / end

testpmd> flow create 0 ingress pattern vlan vid spec 0x10 vid mask 0x10 / ipv4 src spec 10.10.1.1 src mask 255.255.0.0 dst spec 11.11.11.1 dst mask 255.255.255.0 / end actions drop / end

25.7.5. Limitations

Following limitations need to be taken into account while creating flow rules:

• For IPv4 exact match type the key size must be up to 12 bytes.
• For IPv6 exact match type the key size must be up to 36 bytes.
• Following fields cannot be partially masked (all masks are treated as if they were exact):
  • ETH: ethertype
  • VLAN: PCP, VID
  • IPv4: protocol
  • IPv6: next header
  • TCP/UDP: source port, destination port
• Only one classifier table can be created thus all rules in the table have to match table format. Table format is set during creation of the first unique flow rule.
• Up to 5 fields can be specified per flow rule.
• Up to 20 flow rules can be added.

For additional information about classifier please consult doc/musdk_cls_user_guide.txt.