1============================= 2Netlink interface for ethtool 3============================= 4 5 6Basic information 7================= 8 9Netlink interface for ethtool uses generic netlink family ``ethtool`` 10(userspace application should use macros ``ETHTOOL_GENL_NAME`` and 11``ETHTOOL_GENL_VERSION`` defined in ``<linux/ethtool_netlink.h>`` uapi 12header). This family does not use a specific header, all information in 13requests and replies is passed using netlink attributes. 14 15The ethtool netlink interface uses extended ACK for error and warning 16reporting, userspace application developers are encouraged to make these 17messages available to user in a suitable way. 18 19Requests can be divided into three categories: "get" (retrieving information), 20"set" (setting parameters) and "action" (invoking an action). 21 22All "set" and "action" type requests require admin privileges 23(``CAP_NET_ADMIN`` in the namespace). Most "get" type requests are allowed for 24anyone but there are exceptions (where the response contains sensitive 25information). In some cases, the request as such is allowed for anyone but 26unprivileged users have attributes with sensitive information (e.g. 27wake-on-lan password) omitted. 28 29 30Conventions 31=========== 32 33Attributes which represent a boolean value usually use NLA_U8 type so that we 34can distinguish three states: "on", "off" and "not present" (meaning the 35information is not available in "get" requests or value is not to be changed 36in "set" requests). For these attributes, the "true" value should be passed as 37number 1 but any non-zero value should be understood as "true" by recipient. 38In the tables below, "bool" denotes NLA_U8 attributes interpreted in this way. 39 40In the message structure descriptions below, if an attribute name is suffixed 41with "+", parent nest can contain multiple attributes of the same type. This 42implements an array of entries. 43 44 45Request header 46============== 47 48Each request or reply message contains a nested attribute with common header. 49Structure of this header is 50 51 ============================== ====== ============================= 52 ``ETHTOOL_A_HEADER_DEV_INDEX`` u32 device ifindex 53 ``ETHTOOL_A_HEADER_DEV_NAME`` string device name 54 ``ETHTOOL_A_HEADER_FLAGS`` u32 flags common for all requests 55 ============================== ====== ============================= 56 57``ETHTOOL_A_HEADER_DEV_INDEX`` and ``ETHTOOL_A_HEADER_DEV_NAME`` identify the 58device message relates to. One of them is sufficient in requests, if both are 59used, they must identify the same device. Some requests, e.g. global string 60sets, do not require device identification. Most ``GET`` requests also allow 61dump requests without device identification to query the same information for 62all devices providing it (each device in a separate message). 63 64``ETHTOOL_A_HEADER_FLAGS`` is a bitmap of request flags common for all request 65types. The interpretation of these flags is the same for all request types but 66the flags may not apply to requests. Recognized flags are: 67 68 ================================= =================================== 69 ``ETHTOOL_FLAG_COMPACT_BITSETS`` use compact format bitsets in reply 70 ``ETHTOOL_FLAG_OMIT_REPLY`` omit optional reply (_SET and _ACT) 71 ================================= =================================== 72 73New request flags should follow the general idea that if the flag is not set, 74the behaviour is backward compatible, i.e. requests from old clients not aware 75of the flag should be interpreted the way the client expects. A client must 76not set flags it does not understand. 77 78 79Bit sets 80======== 81 82For short bitmaps of (reasonably) fixed length, standard ``NLA_BITFIELD32`` 83type is used. For arbitrary length bitmaps, ethtool netlink uses a nested 84attribute with contents of one of two forms: compact (two binary bitmaps 85representing bit values and mask of affected bits) and bit-by-bit (list of 86bits identified by either index or name). 87 88Verbose (bit-by-bit) bitsets allow sending symbolic names for bits together 89with their values which saves a round trip (when the bitset is passed in a 90request) or at least a second request (when the bitset is in a reply). This is 91useful for one shot applications like traditional ethtool command. On the 92other hand, long running applications like ethtool monitor (displaying 93notifications) or network management daemons may prefer fetching the names 94only once and using compact form to save message size. Notifications from 95ethtool netlink interface always use compact form for bitsets. 96 97A bitset can represent either a value/mask pair (``ETHTOOL_A_BITSET_NOMASK`` 98not set) or a single bitmap (``ETHTOOL_A_BITSET_NOMASK`` set). In requests 99modifying a bitmap, the former changes the bit set in mask to values set in 100value and preserves the rest; the latter sets the bits set in the bitmap and 101clears the rest. 102 103Compact form: nested (bitset) atrribute contents: 104 105 ============================ ====== ============================ 106 ``ETHTOOL_A_BITSET_NOMASK`` flag no mask, only a list 107 ``ETHTOOL_A_BITSET_SIZE`` u32 number of significant bits 108 ``ETHTOOL_A_BITSET_VALUE`` binary bitmap of bit values 109 ``ETHTOOL_A_BITSET_MASK`` binary bitmap of valid bits 110 ============================ ====== ============================ 111 112Value and mask must have length at least ``ETHTOOL_A_BITSET_SIZE`` bits 113rounded up to a multiple of 32 bits. They consist of 32-bit words in host byte 114order, words ordered from least significant to most significant (i.e. the same 115way as bitmaps are passed with ioctl interface). 116 117For compact form, ``ETHTOOL_A_BITSET_SIZE`` and ``ETHTOOL_A_BITSET_VALUE`` are 118mandatory. ``ETHTOOL_A_BITSET_MASK`` attribute is mandatory if 119``ETHTOOL_A_BITSET_NOMASK`` is not set (bitset represents a value/mask pair); 120if ``ETHTOOL_A_BITSET_NOMASK`` is not set, ``ETHTOOL_A_BITSET_MASK`` is not 121allowed (bitset represents a single bitmap. 122 123Kernel bit set length may differ from userspace length if older application is 124used on newer kernel or vice versa. If userspace bitmap is longer, an error is 125issued only if the request actually tries to set values of some bits not 126recognized by kernel. 127 128Bit-by-bit form: nested (bitset) attribute contents: 129 130 +------------------------------------+--------+-----------------------------+ 131 | ``ETHTOOL_A_BITSET_NOMASK`` | flag | no mask, only a list | 132 +------------------------------------+--------+-----------------------------+ 133 | ``ETHTOOL_A_BITSET_SIZE`` | u32 | number of significant bits | 134 +------------------------------------+--------+-----------------------------+ 135 | ``ETHTOOL_A_BITSET_BITS`` | nested | array of bits | 136 +-+----------------------------------+--------+-----------------------------+ 137 | | ``ETHTOOL_A_BITSET_BITS_BIT+`` | nested | one bit | 138 +-+-+--------------------------------+--------+-----------------------------+ 139 | | | ``ETHTOOL_A_BITSET_BIT_INDEX`` | u32 | bit index (0 for LSB) | 140 +-+-+--------------------------------+--------+-----------------------------+ 141 | | | ``ETHTOOL_A_BITSET_BIT_NAME`` | string | bit name | 142 +-+-+--------------------------------+--------+-----------------------------+ 143 | | | ``ETHTOOL_A_BITSET_BIT_VALUE`` | flag | present if bit is set | 144 +-+-+--------------------------------+--------+-----------------------------+ 145 146Bit size is optional for bit-by-bit form. ``ETHTOOL_A_BITSET_BITS`` nest can 147only contain ``ETHTOOL_A_BITSET_BITS_BIT`` attributes but there can be an 148arbitrary number of them. A bit may be identified by its index or by its 149name. When used in requests, listed bits are set to 0 or 1 according to 150``ETHTOOL_A_BITSET_BIT_VALUE``, the rest is preserved. A request fails if 151index exceeds kernel bit length or if name is not recognized. 152 153When ``ETHTOOL_A_BITSET_NOMASK`` flag is present, bitset is interpreted as 154a simple bitmap. ``ETHTOOL_A_BITSET_BIT_VALUE`` attributes are not used in 155such case. Such bitset represents a bitmap with listed bits set and the rest 156zero. 157 158In requests, application can use either form. Form used by kernel in reply is 159determined by ``ETHTOOL_FLAG_COMPACT_BITSETS`` flag in flags field of request 160header. Semantics of value and mask depends on the attribute. 161 162 163List of message types 164===================== 165 166All constants identifying message types use ``ETHTOOL_CMD_`` prefix and suffix 167according to message purpose: 168 169 ============== ====================================== 170 ``_GET`` userspace request to retrieve data 171 ``_SET`` userspace request to set data 172 ``_ACT`` userspace request to perform an action 173 ``_GET_REPLY`` kernel reply to a ``GET`` request 174 ``_SET_REPLY`` kernel reply to a ``SET`` request 175 ``_ACT_REPLY`` kernel reply to an ``ACT`` request 176 ``_NTF`` kernel notification 177 ============== ====================================== 178 179Userspace to kernel: 180 181 ===================================== ================================ 182 ``ETHTOOL_MSG_STRSET_GET`` get string set 183 ``ETHTOOL_MSG_LINKINFO_GET`` get link settings 184 ``ETHTOOL_MSG_LINKINFO_SET`` set link settings 185 ``ETHTOOL_MSG_LINKMODES_GET`` get link modes info 186 ``ETHTOOL_MSG_LINKMODES_SET`` set link modes info 187 ``ETHTOOL_MSG_LINKSTATE_GET`` get link state 188 ===================================== ================================ 189 190Kernel to userspace: 191 192 ===================================== ================================ 193 ``ETHTOOL_MSG_STRSET_GET_REPLY`` string set contents 194 ``ETHTOOL_MSG_LINKINFO_GET_REPLY`` link settings 195 ``ETHTOOL_MSG_LINKINFO_NTF`` link settings notification 196 ``ETHTOOL_MSG_LINKMODES_GET_REPLY`` link modes info 197 ``ETHTOOL_MSG_LINKMODES_NTF`` link modes notification 198 ``ETHTOOL_MSG_LINKSTATE_GET_REPLY`` link state info 199 ===================================== ================================ 200 201``GET`` requests are sent by userspace applications to retrieve device 202information. They usually do not contain any message specific attributes. 203Kernel replies with corresponding "GET_REPLY" message. For most types, ``GET`` 204request with ``NLM_F_DUMP`` and no device identification can be used to query 205the information for all devices supporting the request. 206 207If the data can be also modified, corresponding ``SET`` message with the same 208layout as corresponding ``GET_REPLY`` is used to request changes. Only 209attributes where a change is requested are included in such request (also, not 210all attributes may be changed). Replies to most ``SET`` request consist only 211of error code and extack; if kernel provides additional data, it is sent in 212the form of corresponding ``SET_REPLY`` message which can be suppressed by 213setting ``ETHTOOL_FLAG_OMIT_REPLY`` flag in request header. 214 215Data modification also triggers sending a ``NTF`` message with a notification. 216These usually bear only a subset of attributes which was affected by the 217change. The same notification is issued if the data is modified using other 218means (mostly ioctl ethtool interface). Unlike notifications from ethtool 219netlink code which are only sent if something actually changed, notifications 220triggered by ioctl interface may be sent even if the request did not actually 221change any data. 222 223``ACT`` messages request kernel (driver) to perform a specific action. If some 224information is reported by kernel (which can be suppressed by setting 225``ETHTOOL_FLAG_OMIT_REPLY`` flag in request header), the reply takes form of 226an ``ACT_REPLY`` message. Performing an action also triggers a notification 227(``NTF`` message). 228 229Later sections describe the format and semantics of these messages. 230 231 232STRSET_GET 233========== 234 235Requests contents of a string set as provided by ioctl commands 236``ETHTOOL_GSSET_INFO`` and ``ETHTOOL_GSTRINGS.`` String sets are not user 237writeable so that the corresponding ``STRSET_SET`` message is only used in 238kernel replies. There are two types of string sets: global (independent of 239a device, e.g. device feature names) and device specific (e.g. device private 240flags). 241 242Request contents: 243 244 +---------------------------------------+--------+------------------------+ 245 | ``ETHTOOL_A_STRSET_HEADER`` | nested | request header | 246 +---------------------------------------+--------+------------------------+ 247 | ``ETHTOOL_A_STRSET_STRINGSETS`` | nested | string set to request | 248 +-+-------------------------------------+--------+------------------------+ 249 | | ``ETHTOOL_A_STRINGSETS_STRINGSET+`` | nested | one string set | 250 +-+-+-----------------------------------+--------+------------------------+ 251 | | | ``ETHTOOL_A_STRINGSET_ID`` | u32 | set id | 252 +-+-+-----------------------------------+--------+------------------------+ 253 254Kernel response contents: 255 256 +---------------------------------------+--------+-----------------------+ 257 | ``ETHTOOL_A_STRSET_HEADER`` | nested | reply header | 258 +---------------------------------------+--------+-----------------------+ 259 | ``ETHTOOL_A_STRSET_STRINGSETS`` | nested | array of string sets | 260 +-+-------------------------------------+--------+-----------------------+ 261 | | ``ETHTOOL_A_STRINGSETS_STRINGSET+`` | nested | one string set | 262 +-+-+-----------------------------------+--------+-----------------------+ 263 | | | ``ETHTOOL_A_STRINGSET_ID`` | u32 | set id | 264 +-+-+-----------------------------------+--------+-----------------------+ 265 | | | ``ETHTOOL_A_STRINGSET_COUNT`` | u32 | number of strings | 266 +-+-+-----------------------------------+--------+-----------------------+ 267 | | | ``ETHTOOL_A_STRINGSET_STRINGS`` | nested | array of strings | 268 +-+-+-+---------------------------------+--------+-----------------------+ 269 | | | | ``ETHTOOL_A_STRINGS_STRING+`` | nested | one string | 270 +-+-+-+-+-------------------------------+--------+-----------------------+ 271 | | | | | ``ETHTOOL_A_STRING_INDEX`` | u32 | string index | 272 +-+-+-+-+-------------------------------+--------+-----------------------+ 273 | | | | | ``ETHTOOL_A_STRING_VALUE`` | string | string value | 274 +-+-+-+-+-------------------------------+--------+-----------------------+ 275 | ``ETHTOOL_A_STRSET_COUNTS_ONLY`` | flag | return only counts | 276 +---------------------------------------+--------+-----------------------+ 277 278Device identification in request header is optional. Depending on its presence 279a and ``NLM_F_DUMP`` flag, there are three type of ``STRSET_GET`` requests: 280 281 - no ``NLM_F_DUMP,`` no device: get "global" stringsets 282 - no ``NLM_F_DUMP``, with device: get string sets related to the device 283 - ``NLM_F_DUMP``, no device: get device related string sets for all devices 284 285If there is no ``ETHTOOL_A_STRSET_STRINGSETS`` array, all string sets of 286requested type are returned, otherwise only those specified in the request. 287Flag ``ETHTOOL_A_STRSET_COUNTS_ONLY`` tells kernel to only return string 288counts of the sets, not the actual strings. 289 290 291LINKINFO_GET 292============ 293 294Requests link settings as provided by ``ETHTOOL_GLINKSETTINGS`` except for 295link modes and autonegotiation related information. The request does not use 296any attributes. 297 298Request contents: 299 300 ==================================== ====== ========================== 301 ``ETHTOOL_A_LINKINFO_HEADER`` nested request header 302 ==================================== ====== ========================== 303 304Kernel response contents: 305 306 ==================================== ====== ========================== 307 ``ETHTOOL_A_LINKINFO_HEADER`` nested reply header 308 ``ETHTOOL_A_LINKINFO_PORT`` u8 physical port 309 ``ETHTOOL_A_LINKINFO_PHYADDR`` u8 phy MDIO address 310 ``ETHTOOL_A_LINKINFO_TP_MDIX`` u8 MDI(-X) status 311 ``ETHTOOL_A_LINKINFO_TP_MDIX_CTRL`` u8 MDI(-X) control 312 ``ETHTOOL_A_LINKINFO_TRANSCEIVER`` u8 transceiver 313 ==================================== ====== ========================== 314 315Attributes and their values have the same meaning as matching members of the 316corresponding ioctl structures. 317 318``LINKINFO_GET`` allows dump requests (kernel returns reply message for all 319devices supporting the request). 320 321 322LINKINFO_SET 323============ 324 325``LINKINFO_SET`` request allows setting some of the attributes reported by 326``LINKINFO_GET``. 327 328Request contents: 329 330 ==================================== ====== ========================== 331 ``ETHTOOL_A_LINKINFO_HEADER`` nested request header 332 ``ETHTOOL_A_LINKINFO_PORT`` u8 physical port 333 ``ETHTOOL_A_LINKINFO_PHYADDR`` u8 phy MDIO address 334 ``ETHTOOL_A_LINKINFO_TP_MDIX_CTRL`` u8 MDI(-X) control 335 ==================================== ====== ========================== 336 337MDI(-X) status and transceiver cannot be set, request with the corresponding 338attributes is rejected. 339 340 341LINKMODES_GET 342============= 343 344Requests link modes (supported, advertised and peer advertised) and related 345information (autonegotiation status, link speed and duplex) as provided by 346``ETHTOOL_GLINKSETTINGS``. The request does not use any attributes. 347 348Request contents: 349 350 ==================================== ====== ========================== 351 ``ETHTOOL_A_LINKMODES_HEADER`` nested request header 352 ==================================== ====== ========================== 353 354Kernel response contents: 355 356 ==================================== ====== ========================== 357 ``ETHTOOL_A_LINKMODES_HEADER`` nested reply header 358 ``ETHTOOL_A_LINKMODES_AUTONEG`` u8 autonegotiation status 359 ``ETHTOOL_A_LINKMODES_OURS`` bitset advertised link modes 360 ``ETHTOOL_A_LINKMODES_PEER`` bitset partner link modes 361 ``ETHTOOL_A_LINKMODES_SPEED`` u32 link speed (Mb/s) 362 ``ETHTOOL_A_LINKMODES_DUPLEX`` u8 duplex mode 363 ==================================== ====== ========================== 364 365For ``ETHTOOL_A_LINKMODES_OURS``, value represents advertised modes and mask 366represents supported modes. ``ETHTOOL_A_LINKMODES_PEER`` in the reply is a bit 367list. 368 369``LINKMODES_GET`` allows dump requests (kernel returns reply messages for all 370devices supporting the request). 371 372 373LINKMODES_SET 374============= 375 376Request contents: 377 378 ==================================== ====== ========================== 379 ``ETHTOOL_A_LINKMODES_HEADER`` nested request header 380 ``ETHTOOL_A_LINKMODES_AUTONEG`` u8 autonegotiation status 381 ``ETHTOOL_A_LINKMODES_OURS`` bitset advertised link modes 382 ``ETHTOOL_A_LINKMODES_PEER`` bitset partner link modes 383 ``ETHTOOL_A_LINKMODES_SPEED`` u32 link speed (Mb/s) 384 ``ETHTOOL_A_LINKMODES_DUPLEX`` u8 duplex mode 385 ==================================== ====== ========================== 386 387``ETHTOOL_A_LINKMODES_OURS`` bit set allows setting advertised link modes. If 388autonegotiation is on (either set now or kept from before), advertised modes 389are not changed (no ``ETHTOOL_A_LINKMODES_OURS`` attribute) and at least one 390of speed and duplex is specified, kernel adjusts advertised modes to all 391supported modes matching speed, duplex or both (whatever is specified). This 392autoselection is done on ethtool side with ioctl interface, netlink interface 393is supposed to allow requesting changes without knowing what exactly kernel 394supports. 395 396 397LINKSTATE_GET 398============= 399 400Requests link state information. At the moment, only link up/down flag (as 401provided by ``ETHTOOL_GLINK`` ioctl command) is provided but some future 402extensions are planned (e.g. link down reason). This request does not have any 403attributes. 404 405Request contents: 406 407 ==================================== ====== ========================== 408 ``ETHTOOL_A_LINKSTATE_HEADER`` nested request header 409 ==================================== ====== ========================== 410 411Kernel response contents: 412 413 ==================================== ====== ========================== 414 ``ETHTOOL_A_LINKSTATE_HEADER`` nested reply header 415 ``ETHTOOL_A_LINKSTATE_LINK`` bool link state (up/down) 416 ==================================== ====== ========================== 417 418For most NIC drivers, the value of ``ETHTOOL_A_LINKSTATE_LINK`` returns 419carrier flag provided by ``netif_carrier_ok()`` but there are drivers which 420define their own handler. 421 422``LINKSTATE_GET`` allows dump requests (kernel returns reply messages for all 423devices supporting the request). 424 425 426Request translation 427=================== 428 429The following table maps ioctl commands to netlink commands providing their 430functionality. Entries with "n/a" in right column are commands which do not 431have their netlink replacement yet. 432 433 =================================== ===================================== 434 ioctl command netlink command 435 =================================== ===================================== 436 ``ETHTOOL_GSET`` ``ETHTOOL_MSG_LINKINFO_GET`` 437 ``ETHTOOL_MSG_LINKMODES_GET`` 438 ``ETHTOOL_SSET`` ``ETHTOOL_MSG_LINKINFO_SET`` 439 ``ETHTOOL_MSG_LINKMODES_SET`` 440 ``ETHTOOL_GDRVINFO`` n/a 441 ``ETHTOOL_GREGS`` n/a 442 ``ETHTOOL_GWOL`` n/a 443 ``ETHTOOL_SWOL`` n/a 444 ``ETHTOOL_GMSGLVL`` n/a 445 ``ETHTOOL_SMSGLVL`` n/a 446 ``ETHTOOL_NWAY_RST`` n/a 447 ``ETHTOOL_GLINK`` ``ETHTOOL_MSG_LINKSTATE_GET`` 448 ``ETHTOOL_GEEPROM`` n/a 449 ``ETHTOOL_SEEPROM`` n/a 450 ``ETHTOOL_GCOALESCE`` n/a 451 ``ETHTOOL_SCOALESCE`` n/a 452 ``ETHTOOL_GRINGPARAM`` n/a 453 ``ETHTOOL_SRINGPARAM`` n/a 454 ``ETHTOOL_GPAUSEPARAM`` n/a 455 ``ETHTOOL_SPAUSEPARAM`` n/a 456 ``ETHTOOL_GRXCSUM`` n/a 457 ``ETHTOOL_SRXCSUM`` n/a 458 ``ETHTOOL_GTXCSUM`` n/a 459 ``ETHTOOL_STXCSUM`` n/a 460 ``ETHTOOL_GSG`` n/a 461 ``ETHTOOL_SSG`` n/a 462 ``ETHTOOL_TEST`` n/a 463 ``ETHTOOL_GSTRINGS`` ``ETHTOOL_MSG_STRSET_GET`` 464 ``ETHTOOL_PHYS_ID`` n/a 465 ``ETHTOOL_GSTATS`` n/a 466 ``ETHTOOL_GTSO`` n/a 467 ``ETHTOOL_STSO`` n/a 468 ``ETHTOOL_GPERMADDR`` rtnetlink ``RTM_GETLINK`` 469 ``ETHTOOL_GUFO`` n/a 470 ``ETHTOOL_SUFO`` n/a 471 ``ETHTOOL_GGSO`` n/a 472 ``ETHTOOL_SGSO`` n/a 473 ``ETHTOOL_GFLAGS`` n/a 474 ``ETHTOOL_SFLAGS`` n/a 475 ``ETHTOOL_GPFLAGS`` n/a 476 ``ETHTOOL_SPFLAGS`` n/a 477 ``ETHTOOL_GRXFH`` n/a 478 ``ETHTOOL_SRXFH`` n/a 479 ``ETHTOOL_GGRO`` n/a 480 ``ETHTOOL_SGRO`` n/a 481 ``ETHTOOL_GRXRINGS`` n/a 482 ``ETHTOOL_GRXCLSRLCNT`` n/a 483 ``ETHTOOL_GRXCLSRULE`` n/a 484 ``ETHTOOL_GRXCLSRLALL`` n/a 485 ``ETHTOOL_SRXCLSRLDEL`` n/a 486 ``ETHTOOL_SRXCLSRLINS`` n/a 487 ``ETHTOOL_FLASHDEV`` n/a 488 ``ETHTOOL_RESET`` n/a 489 ``ETHTOOL_SRXNTUPLE`` n/a 490 ``ETHTOOL_GRXNTUPLE`` n/a 491 ``ETHTOOL_GSSET_INFO`` ``ETHTOOL_MSG_STRSET_GET`` 492 ``ETHTOOL_GRXFHINDIR`` n/a 493 ``ETHTOOL_SRXFHINDIR`` n/a 494 ``ETHTOOL_GFEATURES`` n/a 495 ``ETHTOOL_SFEATURES`` n/a 496 ``ETHTOOL_GCHANNELS`` n/a 497 ``ETHTOOL_SCHANNELS`` n/a 498 ``ETHTOOL_SET_DUMP`` n/a 499 ``ETHTOOL_GET_DUMP_FLAG`` n/a 500 ``ETHTOOL_GET_DUMP_DATA`` n/a 501 ``ETHTOOL_GET_TS_INFO`` n/a 502 ``ETHTOOL_GMODULEINFO`` n/a 503 ``ETHTOOL_GMODULEEEPROM`` n/a 504 ``ETHTOOL_GEEE`` n/a 505 ``ETHTOOL_SEEE`` n/a 506 ``ETHTOOL_GRSSH`` n/a 507 ``ETHTOOL_SRSSH`` n/a 508 ``ETHTOOL_GTUNABLE`` n/a 509 ``ETHTOOL_STUNABLE`` n/a 510 ``ETHTOOL_GPHYSTATS`` n/a 511 ``ETHTOOL_PERQUEUE`` n/a 512 ``ETHTOOL_GLINKSETTINGS`` ``ETHTOOL_MSG_LINKINFO_GET`` 513 ``ETHTOOL_MSG_LINKMODES_GET`` 514 ``ETHTOOL_SLINKSETTINGS`` ``ETHTOOL_MSG_LINKINFO_SET`` 515 ``ETHTOOL_MSG_LINKMODES_SET`` 516 ``ETHTOOL_PHY_GTUNABLE`` n/a 517 ``ETHTOOL_PHY_STUNABLE`` n/a 518 ``ETHTOOL_GFECPARAM`` n/a 519 ``ETHTOOL_SFECPARAM`` n/a 520 =================================== ===================================== 521