From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] net/af_xdp: make the PMD compatible with libbpf >= v0.7.0
Date: Thu, 17 Feb 2022 14:26:39 +0000 [thread overview]
Message-ID: <PH0PR11MB479170CA11A2BDC41B7EC8628E369@PH0PR11MB4791.namprd11.prod.outlook.com> (raw)
In-Reply-To: <Yg5JoEjrBt8teL3m@bricha3-MOBL.ger.corp.intel.com>
> Subject: Re: [PATCH] net/af_xdp: make the PMD compatible with libbpf >=
> v0.7.0
>
> On Thu, Feb 17, 2022 at 12:14:30PM +0000, Ciara Loftus wrote:
> > libbpf v0.7.0 deprecates the bpf_prog_load function. Use meson to detect
> > if libbpf >= v0.7.0 is linked and if so, use the recommended replacement
> > functions bpf_object__open_file and bpf_oject__load.
> >
> > Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> > ---
> > drivers/net/af_xdp/compat.h | 39
> +++++++++++++++++++++++++++++
> > drivers/net/af_xdp/meson.build | 5 ++++
> > drivers/net/af_xdp/rte_eth_af_xdp.c | 9 +++----
> > 3 files changed, 48 insertions(+), 5 deletions(-)
> >
> <snip>
> > diff --git a/drivers/net/af_xdp/meson.build
> b/drivers/net/af_xdp/meson.build
> > index 93e895eab9..9fe4063b99 100644
> > --- a/drivers/net/af_xdp/meson.build
> > +++ b/drivers/net/af_xdp/meson.build
> > @@ -22,6 +22,11 @@ if cc.has_header('linux/if_xdp.h')
> > cflags += ['-DRTE_NET_AF_XDP_SHARED_UMEM']
> > ext_deps += xdp_dep
> > ext_deps += bpf_dep
> > + bpf_ver_dep = dependency('libbpf', version : '>=0.6.0',
>
> typo? Commit log refers to v0.7.
Indeed. Thanks for the catch! v2 on the way.
Ciara
prev parent reply other threads:[~2022-02-17 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 12:14 Ciara Loftus
2022-02-17 13:12 ` Bruce Richardson
2022-02-17 14:26 ` 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=PH0PR11MB479170CA11A2BDC41B7EC8628E369@PH0PR11MB4791.namprd11.prod.outlook.com \
--to=ciara.loftus@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).