From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org, viktorin@rehivetech.com
Subject: Re: [PATCH v4 2/3] lpm: add support for NEON
Date: Tue, 01 Mar 2016 18:46:04 +0100 [thread overview]
Message-ID: <3982491.QlXm5U4YLd@xps13> (raw)
In-Reply-To: <1455280123-9311-3-git-send-email-jerin.jacob@caviumnetworks.com>
2016-02-12 17:58, Jerin Jacob:
> # fails to compile on ARM
> -CONFIG_RTE_LIBRTE_LPM=n
> -CONFIG_RTE_LIBRTE_TABLE=n
> -CONFIG_RTE_LIBRTE_PIPELINE=n
The associated examples cannot compile.
Maybe it's too early to enable them.
What about updating the comment to state that only examples fail?
> --- a/lib/librte_lpm/Makefile
> +++ b/lib/librte_lpm/Makefile
> +ifneq ($(filter y,$(CONFIG_RTE_ARCH_ARM) $(CONFIG_RTE_ARCH_ARM64)),)
> +SYMLINK-$(CONFIG_RTE_LIBRTE_LPM)-include += rte_lpm_neon.h
Simpler:
ifneq ($(CONFIG_RTE_ARCH_ARM)$(CONFIG_RTE_ARCH_ARM64),nn)
next prev parent reply other threads:[~2016-03-01 17:47 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 17:24 [PATCH 0/3] add lpm support for NEON Jerin Jacob
2015-11-30 17:24 ` [PATCH 1/3] eal: introduce rte_vect_* abstractions Jerin Jacob
2015-12-02 13:43 ` Jan Viktorin
2015-12-02 14:51 ` Jerin Jacob
2015-11-30 17:24 ` [PATCH 2/3] lpm: add support for NEON Jerin Jacob
2015-12-02 13:43 ` Jan Viktorin
2015-12-02 14:56 ` Jerin Jacob
2015-12-02 15:00 ` Jan Viktorin
2015-11-30 17:24 ` [PATCH 3/3] maintainers: claim responsibility for arm64 specific files of hash and lpm Jerin Jacob
2015-12-02 13:43 ` Jan Viktorin
2015-12-02 14:57 ` Jerin Jacob
2015-12-02 13:43 ` [PATCH 0/3] add lpm support for NEON Jan Viktorin
2015-12-02 14:41 ` Jerin Jacob
2015-12-04 15:14 ` [PATCH v2 " Jerin Jacob
2015-12-04 15:14 ` [PATCH v2 1/3] lpm: make rte_lpm_lookupx4 API definition architecture agnostic Jerin Jacob
2015-12-07 6:15 ` Jianbo Liu
2015-12-07 6:57 ` Jerin Jacob
2015-12-07 14:06 ` Ananyev, Konstantin
2015-12-04 15:14 ` [PATCH v2 2/3] lpm: add support for NEON Jerin Jacob
2015-12-04 15:14 ` [PATCH v2 3/3] maintainers: claim responsibility for arm64 specific files of hash and lpm Jerin Jacob
2016-01-29 4:10 ` [PATCH v3 0/3] add lpm support for NEON Jerin Jacob
2016-01-29 4:10 ` [PATCH v3 1/3] lpm: make rte_lpm_lookupx4 API definition architecture agnostic Jerin Jacob
2016-01-29 4:10 ` [PATCH v3 2/3] lpm: add support for NEON Jerin Jacob
2016-02-11 11:46 ` Thomas Monjalon
2016-02-12 6:47 ` Jerin Jacob
2016-02-12 8:42 ` Thomas Monjalon
2016-01-29 4:10 ` [PATCH v3 3/3] maintainers: claim responsibility for arm64 specific files of hash and lpm Jerin Jacob
2016-02-08 9:29 ` [PATCH v3 0/3] add lpm support for NEON Jerin Jacob
2016-02-12 12:28 ` [PATCH v4 " Jerin Jacob
2016-02-12 12:28 ` [PATCH v4 1/3] lpm: make rte_lpm_lookupx4 API definition architecture agnostic Jerin Jacob
2016-03-01 17:42 ` Thomas Monjalon
2016-03-02 6:28 ` Jerin Jacob
2016-02-12 12:28 ` [PATCH v4 2/3] lpm: add support for NEON Jerin Jacob
2016-03-01 17:46 ` Thomas Monjalon [this message]
2016-03-02 6:45 ` Jerin Jacob
2016-02-12 12:28 ` [PATCH v4 3/3] maintainers: claim responsibility for arm64 specific files of hash and lpm Jerin Jacob
2016-03-01 17:47 ` Thomas Monjalon
2016-03-02 6:46 ` Jerin Jacob
2016-02-16 13:27 ` [PATCH v4 0/3] add lpm support for NEON Kobylinski, MichalX
2016-02-16 16:44 ` Jerin Jacob
2016-02-18 10:26 ` Kobylinski, MichalX
2016-02-19 0:34 ` Jerin Jacob
2016-03-11 3:52 ` [PATCH v5 " Jerin Jacob
2016-03-11 3:52 ` [PATCH v5 1/3] lpm: make rte_lpm_lookupx4 API definition architecture agnostic Jerin Jacob
2016-03-11 3:52 ` [PATCH v5 2/3] lpm: add support for NEON Jerin Jacob
2016-03-11 3:52 ` [PATCH v5 3/3] Maintainers: claim responsibility for arm64 specific files of hash Jerin Jacob
2016-03-11 14:24 ` [PATCH v5 0/3] add lpm support for NEON Thomas Monjalon
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=3982491.QlXm5U4YLd@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=viktorin@rehivetech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.