You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Issues when running low-latency applications on X1C9
How to reproduce consistently
Run watch -d -n 0.1 cat /proc/interrupts and find on what core periodic acpi interrupts happen
Pin a latency-sensitive application on that CPU core using taskset -c $CORE $APP where $CORE is the cpu number found in step 1. Observe that there are periodic interruptions in the real-time app (every ~0.5 seconds).
How to reproduce (seems random)
Run watch -d -n 0.1 cat /proc/interrupts and find on what core a lot of interrupts happen when holding your finger on the touchpad
Pin a latency-sensitive application on that CPU core using taskset -c $CORE $APP where $CORE is the cpu number found in step 1
Our goal is to route a packet from a particular interface or source address range to the desired interface, even if that interface is not our default interface.
Source based routing with ip rule
We have virtual machines bridged to the virbr1 interface and we want to route trafic of these VMs to a virtual network that is accessible via tun0.
Assuming default NAT routing has been set up for the VM instances, we can route the traffic as follows:
ip rule add dev virbr1 table 100
ip route add default dev tun0 table 100
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters