How to make TX/RX ring config change survive a reboot?

SUSE Product Topics SLES Configure-Administer
1

Hi,

How can i make the following change survive a reboot?

Change : ethtool -G eth0 rx 4096 tx 4096

ethtool -g eth0

Ring parameters for eth0:
Pre-set maximums:
RX: 4096
RX Mini: 0
RX Jumbo: 0
TX: 4096
Current hardware settings:
RX: 4096
RX Mini: 0
RX Jumbo: 0
TX: 4096

Rgds

2

[QUOTE=ronanb78;53958]Hi,

How can i make the following change survive a reboot?

Change : ethtool -G eth0 rx 4096 tx 4096

ethtool -g eth0

Ring parameters for eth0:
Pre-set maximums:
RX: 4096
RX Mini: 0
RX Jumbo: 0
TX: 4096
Current hardware settings:
RX: 4096
RX Mini: 0
RX Jumbo: 0
TX: 4096

Rgds[/QUOTE]
Hi
Create a systemd service :wink: file down in /etc/systemd/service called say ring_buffer.service with the following content;

#/etc/systemd/system/ring_buffer.service

[Unit]
Desctiption=Configure memory to store network packets received/transmitted
After=network.target

[Service]
Type=oneshot

ExecStart=/usr/sbin/ethtool -G eth0 rx 4096 tx 4096

[Install]
WantedBy=multi-user.target

Then test and enable;

systemctl start ring_buffer
systemctl status ring_buffer
systemctl enable ring_buffer

On the next reboot it will run after the network starts up.

3

Hi Malcolm,

This works only when i manually start the ring_buffer service after a reboot?
Does the “systemctl start ring_buffer” command need to be included in the ring_buffer.service file?

Thanks

4

I got this to work. Because I am using cluster manager software, i had to manually create the softlink that the “systemctl enable ring_buffer” command does.
Thanks for your help, again!