What does the meaning of "[fixed]" string in output of ethtool command

networking nic
leivli picture leivli · Dec 15, 2014 · Viewed 12.3k times · Source

I run ethtool to query the offload features of a NIC using "ethtool -k" command, and the output is something as follows:

ethtool -k eth0

scatter-gather: on
tx-scatter-gather: on
tx-scatter-gather-fraglist: off **[fixed]**

I am wondering what the meaning of "[fixed]" is.

Answer

user2360915 picture user2360915 · Dec 15, 2014

Those are the parameters that cant be changed, they are "fixed".

Here is an example. Let's take this output of ethtool :

large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on

If I want to change rx-vlan-offload I would do :

$ sudo ethtool -K eth0 rxvlan off
Actual changes:
tcp-segmentation-offload: on
    tx-tcp-segmentation: on
    tx-tcp6-segmentation: on
rx-vlan-offload: off

The result will be :

$ sudo ethtool -k eth0 | grep rx-vlan
rx-vlan-offload: **off**
rx-vlan-filter: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]

Now, let's try to modify a "fixed" parameter like "large-receive-offload" :

$ sudo ethtool -K eth0 lro on
Cannot change large-receive-offload
Could not change any device features

Hope this helps.

Related questions

How can I get the IP address from NIC in Python?

When an error occurs in a Python script on Unix , an email is sent. I have been asked to add {Testing Environment} to the subject line of the email if the IP address is 192.168.100.37 which is the testing server. This …

Read More
ixgbe: setting the number of RX/TX queues

I want to set the number of RX/TX queues used by an Intel 10G NIC. Let me explain why: I am using an Intel 10G NIC of type X520, on a Dell R720 system. I am using ixgbe version 3.6.7…

Read More
docker-compose: specify which interface will connect to each network (when having multiple networks)

Inside the docker-compose.yaml I define 4 different networks: networks: vpp-nw: vpp-client: vpp-server: vpp-db: which use the following network addresses respectively: 172.20.0.x 172.21.0.x 172.22.0.x 172.23.0.x One of the containers I use, connects to all 4 networks (with the same order): # part of …

Read More