1DCB(8) Linux DCB(8)
2
6 dcb - show / manipulate DCB (Data Center Bridging) settings
7
9 dcb [ OPTIONS ] { app | buffer | ets | maxrate | pfc } { COMMAND | help
10 }
11 dcb [ -force ] -batch filename
14 dcb [ OPTIONS ] help
17
21 -n, --netns <NETNS>
22 switches dcb to the specified network namespace NETNS.
23 -V, --Version
26 Print the version of the dcb utility and exit.
27 -b, --batch <FILENAME>
30 Read commands from provided file or standard input and invoke
31 them. First failure will cause termination of dcb.
32 -f, --force
35 Don't terminate dcb on errors in batch mode. If there were any
36 errors during execution of the commands, the application return
37 code will be non zero.
38 -i, --iec
41 When showing rates, use ISO/IEC 1024-based prefixes (Ki, Mi, Bi)
42 instead of the 1000-based ones (K, M, B).
43 -j, --json
46 Generate JSON output.
47 -N, --Numeric
50 If the subtool in question translates numbers to symbolic names
51 in some way, suppress this translation.
52 -p, --pretty
55 When combined with -j generate a pretty JSON output.
56 -s, --statistics
59 If the object in question contains any statistical counters,
60 shown them as part of the "show" output.
61
64 app - Configuration of application priority table
65 buffer - Configuration of port buffers
68 ets - Configuration of ETS (Enhanced Transmission Selection)
71 maxrate
74 - Configuration of per-TC maximum transmit rate
75 pfc - Configuration of PFC (Priority-based Flow Control)
78
81 A COMMAND specifies the action to perform on the object. The set of
82 possible actions depends on the object type. As a rule, it is possible
83 to show objects and to invoke topical help, which prints a list of
84 available commands and argument syntax conventions.
85
88 Like commands, specification of parameters is in the domain of individ‐
89 ual objects (and their commands) as well. However, much of the DCB in‐
90 terface revolves around arrays of fixed size that specify one value per
91 some key, such as per traffic class or per priority. There is therefore
92 a single syntax for adjusting elements of these arrays. It consists of
93 a series of KEY:VALUE pairs, where the meaning of the individual keys
94 and values depends on the parameter.
95 The elements are evaluated in order from left to right, and the latter
97 ones override the earlier ones. The elements that are not specified on
98 the command line are queried from the kernel and their current value is
99 retained.
100 As an example, take a made-up parameter tc-juju, which can be set to
102 charm traffic in a given TC with either good luck or bad luck. KEY can
103 therefore be 0..7 (as is usual for TC numbers in DCB), and VALUE either
104 of none, good, and bad. An example of changing a juju value of TCs 0
105 and 7, while leaving all other intact, would then be:
106 # dcb foo set dev eth0 tc-juju 0:good 7:bad
109 A special key, all, is recognized which sets the same value to all ar‐
111 ray elements. This can be combined with the usual single-element syn‐
112 tax. E.g. in the following, the juju of all keys is set to none, except
113 0 and 7, which have other values:
114 # dcb foo set dev eth0 tc-juju all:none 0:good 7:bad
117
120 Exit status is 0 if command was successful or a positive integer upon
121 failure.
122
125 dcb-app(8), dcb-buffer(8), dcb-ets(8), dcb-maxrate(8), dcb-pfc(8)
126
129 Report any bugs to the Network Developers mailing list <net‐
130 dev@vger.kernel.org> where the development and maintenance is primarily
131 done. You do not have to be subscribed to the list to send a message
132 there.
133
136 Petr Machata <me@pmachata.org>
137iproute2 19 October 2020 DCB(8)