DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>, <dev@dpdk.org>
Cc: <bruce.richardson@intel.com>
Subject: Re: [PATCH v3] net/af_xdp: use libxdp if available
Date: Tue, 1 Feb 2022 10:11:23 +0000	[thread overview]
Message-ID: <c373f498-eb0c-3cf9-f43f-1efa19fcc890@intel.com> (raw)
In-Reply-To: <20220128095029.4402-1-ciara.loftus@intel.com>

On 1/28/2022 9:50 AM, Ciara Loftus wrote:
> AF_XDP support is deprecated in libbpf since v0.7.0 [1]. The libxdp library
> now provides the functionality which once was in libbpf and which the
> AF_XDP PMD relies on. This commit updates the AF_XDP meson build to use the
> libxdp library if a version >= v1.2.2 is available. If it is not available,
> only versions of libbpf prior to v0.7.0 are allowed, as they still contain
> the required AF_XDP functionality.
> 
> libbpf still remains a dependency even if libxdp is present, as we use
> libbpf APIs for program loading.
> 
> The minimum required kernel version for libxdp for use with AF_XDP is v5.3.
> For the library to be fully-featured, a kernel v5.10 or newer is
> recommended. The full compatibility information can be found in the libxdp
> README.
> 
> v1.2.2 of libxdp includes an important fix required for linking with DPDK
> which is why this version or greater is required. Meson uses pkg-config to
> verify the version of libxdp on the system, so it is necessary that the
> library is discoverable using pkg-config in order for the PMD to use it. To
> verify this, you can run: pkg-config --modversion libxdp
> 
> [1]https://github.com/libbpf/libbpf/commit/277846bc6c15
> 
> Signed-off-by: Ciara Loftus<ciara.loftus@intel.com>


Applied to dpdk-next-net/main, thanks.

      parent reply	other threads:[~2022-02-01 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 10:58 [RFC PATCH] " Ciara Loftus
2022-01-12 13:07 ` [PATCH] " Ciara Loftus
2022-01-25  7:20   ` [PATCH v2] " Ciara Loftus
2022-01-25  9:27     ` Bruce Richardson
2022-01-27  8:42       ` Loftus, Ciara
2022-01-28  9:50     ` [PATCH v3] " Ciara Loftus
2022-01-31 17:59       ` Ferruh Yigit
2022-01-31 18:05         ` Bruce Richardson
2022-02-01 10:06           ` Ferruh Yigit
2022-02-01 10:11       ` Ferruh Yigit [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=c373f498-eb0c-3cf9-f43f-1efa19fcc890@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@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).