On 6 Sep 2023, at 8:20, David Marchand wrote:
> When using net/af_xdp DPDK driver along OVS native AF_XDP support,
> confusing logs are reported, like:
>
> netdev_dpdk|INFO|Device 'net_af_xdpp0,iface=ovs-p0' attached to DPDK
> dpif_netdev|INFO|PMD thread on numa_id: 0, core id: 11 created.
> dpif_netdev|INFO|There are 1 pmd threads on numa node 0
> dpdk|INFO|Device with port_id=0 already stopped
> dpdk(pmd-c11/id:22)|INFO|PMD thread uses DPDK lcore 1.
> netdev_dpdk|WARN|Rx checksum offload is not supported on port 0
> netdev_afxdp|INFO|libbpf: elf: skipping unrecognized data section(6)
> .xdp_run_config
> netdev_afxdp|INFO|libbpf: elf: skipping unrecognized data section(7)
> xdp_metadata
> netdev_afxdp|INFO|libbpf: elf: skipping unrecognized data section(7)
> xdp_metadata
> netdev_afxdp|INFO|libbpf: elf: skipping unrecognized data section(7)
> xdp_metadata
>
> This comes from the fact that netdev-afxdp unconditionnally registers a
> helper for logging libbpf messages.
> Making both net/af_xdp and netdev-afxdp work at the same time seems
> difficult, so at least, ensure that netdev-afxdp won't register this
> helper unless a netdev is actually allocated.
>
> Signed-off-by: David Marchand <[email protected]>
These changes look good to me!
Acked-by: Eelco Chaudron <[email protected]>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
