On 20 Nov 2019, at 21:17, William Tu wrote:
On Tue, Nov 19, 2019 at 10:51:01AM -0800, William Tu wrote:
Hi Eelco,
Thanks for your testing.
On Tue, Nov 12, 2019 at 11:25:55AM +0100, Eelco Chaudron wrote:
See one remark below, however when I did a quick test with a program
that
would not
On Tue, Nov 19, 2019 at 10:51:01AM -0800, William Tu wrote:
> Hi Eelco,
>
> Thanks for your testing.
>
> On Tue, Nov 12, 2019 at 11:25:55AM +0100, Eelco Chaudron wrote:
> > See one remark below, however when I did a quick test with a program that
> > would not load it goes into some re-try loop:
Hi Eelco,
Thanks for your testing.
On Tue, Nov 12, 2019 at 11:25:55AM +0100, Eelco Chaudron wrote:
> See one remark below, however when I did a quick test with a program that
> would not load it goes into some re-try loop:
>
> 2019-11-12T10:13:21.658Z|01609|netdev_afxdp|INFO|eno1: Removing xdp
See one remark below, however when I did a quick test with a program
that would not load it goes into some re-try loop:
2019-11-12T10:13:21.658Z|01609|netdev_afxdp|INFO|eno1: Removing xdp
program.
2019-11-12T10:13:21.658Z|01610|netdev_afxdp|INFO|Removed program ID: 0,
fd: 0
Now netdev-afxdp always forwards all packets to userspace because
it is using libbpf's default XDP program, see 'xsk_load_xdp_prog'.
There are some cases when users want to keep packets in kernel instead
of sending to userspace, for example, management traffic such as SSH
should be processed in
