Transition DCTCP to use ECT1 marks for elegible segments

[rscheff]

Summary

This adds the capability for a modular congestion control
to select which variant of ECN-capable-transport is wants to use
when sending out elegible segments. As an initial CC to utilize
this, DCTCP was selected.

In conjunction with a classifier in the switch, DCTCP traffic
can easily be placed into a Queue, where the switch performs
the more aggressive CE marking regime that is expected by DCTCP.

Test Plan

Verify that data packets sent when DCTCP congestion
control is active are sent using the IP ECT(1) marking instead
of the usual ECT(0) marking.

[rscheff]

This change will not go in for the time being, pending a conclusion of the discussion around the ECT1 codepoint in IETF.

[rgrimes]

If you have clients that need to do this type of thing I would recommend they are running behind DSCP and they should use 2 DSCP's to seperate there DCTCP like traffic from there TCP/reno like traffic. Using ECT(1) as a traffic classifier in advance of IETF clear decision may land them in a very hard to resolve possition in the future.

share/man/man4/cc_dctcp.4

98

Changing the default marking to ect(1) may break someone using DCTCP today, and given that ECT(1) is in a heavily contested state withint the IETF/tsvwg I do not think it would be wise to make this or any other ECT(1) related changes. The status from the chairs of tsvwg said "move forward with L4S", it did not say that consenses had been reached on usage of ECT(1).

sys/netinet/cc/cc_dctcp.c

71

By setting this to 1 here doesnt this change the default to be ect(1) marking

489

Isnt "Send DCTCP segments with IP ECT(1) *instead of* ECT(0)" the correct statement here?

[rscheff]

• rebase to main manually

[rscheff]

• add new flag at the bottom and next bit