Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
udev-rule: rationale for applying the rule on virtual interfaces
We should apply the rule on the virtual interfaces of the host, because of the RPS mask that would be consulted, is the one on the RX side of the veth in the host. Consider the following diagram: Pod A <veth1 - veth2> host <veth3 - veth4> Pod B veth2's RPS affinity is the one determining the CPUs that are handling the packet processing when sending data from Pod A to pod B. Additional common scenarios: 1. Pod A = sender, host = receiver The RPS affinity of the host side should be consulted (because it’s the receiver) and it should be set to cpus not sensitive to preemption (reserved pool). 2. Pod A = receiver, host = sender In case of no RPS mask on the receiver side, the sender needs to pay the price and do all the processing on its cores. Signed-off-by: Talor Itzhak <titzhak@redhat.com>
- Loading branch information