From: Andy Gospodarek <andy@xxxxxxxxxxxxx> Date: Mon, 10 Apr 2017 14:39:35 -0400 > I also noted that... > > xdp1 not parsing the protocol correctly. All traffic was showing up as > protocol '0' instead of '17' in the output. > > xdp2 was not actually sending the frames back out when using this patch. > > I'll take a look in a bit and see if I can track these two issues down. Read Alexei's earlier posting, he spotted the bugs you are seeing here. Basically, the MAC header is pulled already so we have to push it back before we run XDP over it. We also have to be similarly careful with the MAC header for XDP_TX cases.
|