From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@xilinx.com>
Cc: Ciara Loftus <ciara.loftus@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
dev@dpdk.org, david.marchand@redhat.com, ferruh.yigit@amd.com,
andrew.rybchenko@oktetlabs.ru
Subject: Re: af_xdp + libbpf 0.8
Date: Fri, 24 Jun 2022 03:26:31 +0200 [thread overview]
Message-ID: <4227833.0vhOF50zNu@thomas> (raw)
In-Reply-To: <4c546c6c-b51c-37c2-4a4e-5e471e5b2a37@xilinx.com>
24/06/2022 00:18, Ferruh Yigit:
> On 6/23/2022 10:58 PM, Thomas Monjalon wrote:
> > Hi,
> >
> > It seems DPDK is not compatible with libbpf 0.8:
> >
> > drivers/net/af_xdp/rte_eth_af_xdp.c:871:6: error: 'bpf_get_link_xdp_id' is deprecated: libbpf v0.8+: use bpf_xdp_query_id() instead
> > /usr/include/bpf/libbpf.h:1168:1: note: 'bpf_get_link_xdp_id' has been explicitly marked deprecated here
> > LIBBPF_DEPRECATED_SINCE(0, 8, "use bpf_xdp_query_id() instead")
> >
> > drivers/net/af_xdp/rte_eth_af_xdp.c:876:2: error: 'bpf_set_link_xdp_fd' is deprecated: libbpf v0.8+: use bpf_xdp_attach() instead
> > /usr/include/bpf/libbpf.h:1163:1: note: 'bpf_set_link_xdp_fd' has been explicitly marked deprecated here
> > LIBBPF_DEPRECATED_SINCE(0, 8, "use bpf_xdp_attach() instead")
> >
> > dpdk/drivers/net/af_xdp/rte_eth_af_xdp.c:1198:8: error: 'bpf_set_link_xdp_fd' is deprecated: libbpf v0.8+: use bpf_xdp_attach() instead
> > /usr/include/bpf/libbpf.h:1163:1: note: 'bpf_set_link_xdp_fd' has been explicitly marked deprecated here
> > LIBBPF_DEPRECATED_SINCE(0, 8, "use bpf_xdp_attach() instead")
>
> From af_xdp documentation (doc.dpdk.org/guides/nics/af_xdp.html):
>
> 5.2. Prerequisites
> This is a Linux-specific PMD, thus the following prerequisites apply:
>
> Both libxdp >=v1.2.2 and libbpf libraries installed, or, libbpf <=v0.6.0
I am in the first case: libxdp-1.2.3 and libbpf-0.8
According to the documentation, it should work.
next prev parent reply other threads:[~2022-06-24 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 21:58 Thomas Monjalon
2022-06-23 22:18 ` Ferruh Yigit
2022-06-24 1:26 ` Thomas Monjalon [this message]
2022-06-24 6:12 ` Loftus, Ciara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4227833.0vhOF50zNu@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ciara.loftus@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=ferruh.yigit@xilinx.com \
--cc=qi.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).