1DEVLINK(8) Linux DEVLINK(8)
2
3
4
6 devlink - Devlink tool
7
9 devlink [ OPTIONS ] { dev|port|monitor|sb|resource|region|health } {
10 COMMAND | help }
11
12
13 devlink [ -force ] -batch filename
14
15
16
18 -V, --Version
19 Print the version of the devlink utility and exit.
20
21
22 -b, -batch <FILENAME>
23 Read commands from provided file or standard input and invoke
24 them. First failure will cause termination of devlink.
25
26
27 -force Don't terminate devlink on errors in batch mode. If there were
28 any errors during execution of the commands, the application
29 return code will be non zero.
30
31
32 -n, --no-nice-names
33 Turn off printing out nice names, for example netdevice ifnames
34 instead of devlink port identification.
35
36
37 -j, --json
38 Generate JSON output.
39
40
41 -p, --pretty
42 When combined with -j generate a pretty JSON output.
43
44
45 -v, --verbose
46 Turn on verbose output.
47
48
49 OBJECT
50 dev - devlink device.
51
52
53 port - devlink port.
54
55
56 monitor
57 - watch for netlink messages.
58
59
60 sb - devlink shared buffer configuration.
61
62
63 resource
64 - devlink device resource configuration.
65
66
67 region - devlink address region access
68
69
70 health - devlink reporting and recovery
71
72
73 COMMAND
74 Specifies the action to perform on the object. The set of possible
75 actions depends on the object type. As a rule, it is possible to show
76 (or list ) objects, but some objects do not allow all of these opera‐
77 tions or have some additional commands. The help command is available
78 for all objects. It prints out a list of available commands and argu‐
79 ment syntax conventions.
80
81 If no command is given, some default command is assumed. Usually it is
82 list or, if the objects of this class cannot be listed, help.
83
84
86 Exit status is 0 if command was successful or a positive integer upon
87 failure.
88
89
91 devlink-dev(8), devlink-port(8), devlink-monitor(8), devlink-sb(8),
92 devlink-resource(8), devlink-region(8), devlink-health(8),
93
94
96 Report any bugs to the Network Developers mailing list <net‐
97 dev@vger.kernel.org> where the development and maintenance is primarily
98 done. You do not have to be subscribed to the list to send a message
99 there.
100
101
103 Jiri Pirko <jiri@mellanox.com>
104
105
106
107iproute2 14 Mar 2016 DEVLINK(8)