DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
	"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: af_xdp + libbpf 0.8
Date: Fri, 24 Jun 2022 06:12:47 +0000	[thread overview]
Message-ID: <MW4PR11MB5872657BDCE56E215C8B88CA8EB49@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4227833.0vhOF50zNu@thomas>

> 
> 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.
> 

I submitted a fix to prevent linking with >=v0.8.0.
It can be used until the more robust solution is ready which requires a bit more validation.

Thanks,
Ciara

      reply	other threads:[~2022-06-24  6:12 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
2022-06-24  6:12     ` Loftus, Ciara [this message]

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=MW4PR11MB5872657BDCE56E215C8B88CA8EB49@MW4PR11MB5872.namprd11.prod.outlook.com \
    --to=ciara.loftus@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --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 \
    --cc=thomas@monjalon.net \
    /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).