On Tue, 2016-09-13 at 10:13 -0700, Alexei Starovoitov wrote: > I'm afraid the point 'only for debugging' still didn't make it across. > xdp+e1k is for development (and debugging) of xdp-type of bpf > programs and _not_ for debugging of xdp itself, kernel or anything else. > The e1k provided interfaces and behavior needs to match exactly > what real hw nics (like mlx4, mlx5, igxbe, i40e) will do. > Doing special hacks are not acceptable. Therefore your > 'proposed fix' misses the mark, since: > 1. ignoring bql/qdisc is not a bug, but the requirement > 2. such 'fix' goes against the goal above since behaviors will be > different and xdp developer won't be able to build something like > xdp loadbalancer in the kvm. >
Is e1k the only way a VM can receive and send packets ? Instead of adding more cruft to a legacy driver, risking breaking real old machines, I am sure we can find modern alternative.