From: Stephen Hemminger <stephen@networkplumber.org>
To: Qi Zhang <qi.z.zhang@intel.com>
Cc: dev@dpdk.org, magnus.karlsson@intel.com, bjorn.topel@intel.com
Subject: Re: [dpdk-dev] [RFC 6/7] net/af_xdp: load BPF file
Date: Wed, 28 Feb 2018 13:10:08 -0800 [thread overview]
Message-ID: <20180228131008.296f54bd@xeon-e3> (raw)
In-Reply-To: <20180227093554.23951-7-qi.z.zhang@intel.com>
On Tue, 27 Feb 2018 17:35:53 +0800
Qi Zhang <qi.z.zhang@intel.com> wrote:
> diff --git a/drivers/net/af_xdp/Makefile b/drivers/net/af_xdp/Makefile
> index ac38e20bf..a642786de 100644
> --- a/drivers/net/af_xdp/Makefile
> +++ b/drivers/net/af_xdp/Makefile
> @@ -42,7 +42,10 @@ EXPORT_MAP := rte_pmd_af_xdp_version.map
>
> LIBABIVER := 1
>
> -CFLAGS += -O3 -I/opt/af_xdp/linux_headers/include
> +LINUX_HEADER_DIR := /opt/af_xdp/linux_headers/include
> +TOOLS_DIR := /root/af_xdp/npg_dna-dna-linux/tools
Hardcoding paths is not a good idea.
next prev parent reply other threads:[~2018-02-28 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 9:35 [dpdk-dev] [RFC 0/7] PMD driver for AF_XDP Qi Zhang
2018-02-27 9:35 ` [dpdk-dev] [RFC 1/7] net/af_xdp: new PMD driver Qi Zhang
2018-02-27 9:35 ` [dpdk-dev] [RFC 2/7] lib/mbuf: enable parse flags when create mempool Qi Zhang
2018-02-27 9:35 ` [dpdk-dev] [RFC 3/7] lib/mempool: allow page size aligned mempool Qi Zhang
2018-02-27 9:35 ` [dpdk-dev] [RFC 4/7] net/af_xdp: use mbuf mempool for buffer management Qi Zhang
2018-02-27 9:35 ` [dpdk-dev] [RFC 5/7] net/af_xdp: enable share mempool Qi Zhang
2018-02-27 9:35 ` [dpdk-dev] [RFC 6/7] net/af_xdp: load BPF file Qi Zhang
2018-02-28 21:10 ` Stephen Hemminger [this message]
2018-02-28 21:12 ` Stephen Hemminger
2018-02-27 9:35 ` [dpdk-dev] [RFC 7/7] app/testpmd: enable parameter for mempool flags Qi Zhang
-- strict thread matches above, loose matches on Subject: below --
2018-02-27 9:32 [dpdk-dev] [RFC 0/7] PMD driver for AF_XDP Qi Zhang
2018-02-27 9:33 ` [dpdk-dev] [RFC 6/7] net/af_xdp: load BPF file Qi Zhang
2018-03-01 2:10 ` Stephen Hemminger
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=20180228131008.296f54bd@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bjorn.topel@intel.com \
--cc=dev@dpdk.org \
--cc=magnus.karlsson@intel.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).