Closed caopeirui closed 4 years ago
With meters, you can only increase the precedence level of the DSCP field. The specification says on page 87:
This band increases the encoded drop precedence by this amount, not the raw DSCP value; it always results in a valid DSCP value, and DSCP values that do not encode a drop precedence are not modified.
Therefore you have to use the tos option to add some initial precedence level.
With meters, you can only increase the precedence level of the DSCP field. The specification says on page 87:
This band increases the encoded drop precedence by this amount, not the raw DSCP value; it always results in a valid DSCP value, and DSCP values that do not encode a drop precedence are not modified.
Therefore you have to use the tos option to add some initial precedence level.
Thank you for your help. I need to research the specification further.
We need to use dscp_remark to split traffic by a rate threshold. A successful case is:
However, we have to use a additional parmeter
--tos 0x8
in iperf test, such as,Looking up https://github.com/CPqD/ofsoftswitch13/blob/master/udatapath/meter_entry.c#L236 , we find the corresponding relationship is
Therefore, there are too many limits. How can we use ofsoftwitch13's dscp_remark function more flexibly? How can we use dscp_remark function without the --tos 0x08 ?