From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH] net/af_xdp: update docs with libxdp requirements and info
Date: Fri, 11 Feb 2022 17:39:20 +0000 [thread overview]
Message-ID: <ebd096cb-9b49-9393-3b9d-fadb4b891612@intel.com> (raw)
In-Reply-To: <20220211150305.27122-1-ciara.loftus@intel.com>
On 2/11/2022 3:03 PM, Ciara Loftus wrote:
> When libxdp is used, the LIBXDP_OBJECT_PATH environment variable must be
> set to the location of where libxdp placed its bpf object files. This is
> usually in /usr/local/lib/bpf or /usr/local/lib64/bpf. Failure to do so
> will result in the PMD not initialising correctly as the bpf program is
> not found. Document this requirement.
>
> Also, mention that the following logs which are generated on application
> launch can be ignored:
>
> libbpf: elf: skipping unrecognized data section(7) .xdp_run_config
> libbpf: elf: skipping unrecognized data section(8) xdp_metadata
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-02-11 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 15:03 Ciara Loftus
2022-02-11 17:39 ` 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=ebd096cb-9b49-9393-3b9d-fadb4b891612@intel.com \
--to=ferruh.yigit@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).