[dpdk-dev] [PATCH v3 0/2] examples/l3fwd: fix using packet type blindly
Ananyev, Konstantin
konstantin.ananyev at intel.com
Thu Mar 10 15:26:55 CET 2016
> From: Tan, Jianfeng
> Sent: Thursday, March 10, 2016 5:51 AM
> To: dev at dpdk.org
> Cc: Zhang, Helin; Ananyev, Konstantin; nelio.laranjeiro at 6wind.com; adrien.mazarguil at 6wind.com; rahul.lakkireddy at chelsio.com;
> pmatilai at redhat.com; Tan, Jianfeng
> Subject: [PATCH v3 0/2] examples/l3fwd: fix using packet type blindly
>
> This patch will work on below patch series.
> - [PATCH v7 00/11] Add API to get packet type info
>
> v3:
> - em ptype check: (l4_tcp || l4_udp) -> (l4_tcp && l4_udp).
> - avoid rte_be_to_cpu_16 for each packet by adding proper macros.
> - with --parse-ptype specified, use sw parser mandatorily.
> - enable i40e vector driver by default.
>
> v2:
> - Add patchset dependence in commit log.
> - Change hardcoded 0 to RTE_PTYPE_UNKNOWN.
> - More accurate em_parse_type.
> - Add restrictions in EM forwarding functions.
> - Define cb directly to avoid too many function calls when do analyze.
> - Some typo fixed.
> - Change the position to call rte_eth_dev_get_ptype_info
> after rte_eth_dev_start().
>
> Patch 1: add an option in l3fwd.
> Patch 2: enable vector pmd in i40e by default.
>
> Signed-off-by: Jianfeng Tan <jianfeng.tan at intel.com>
>
> Jianfeng Tan (2):
> examples/l3fwd: fix using packet type blindly
> config: enable i40e vector driver by default
>
> config/common_base | 2 +-
> doc/guides/rel_notes/release_16_04.rst | 14 ++++
> doc/guides/sample_app_ug/l3_forward.rst | 6 +-
> examples/l3fwd/l3fwd.h | 14 ++++
> examples/l3fwd/l3fwd_em.c | 112 ++++++++++++++++++++++++++++++++
> examples/l3fwd/l3fwd_em.h | 10 ++-
> examples/l3fwd/l3fwd_em_hlm_sse.h | 17 +++--
> examples/l3fwd/l3fwd_em_sse.h | 9 ++-
> examples/l3fwd/l3fwd_lpm.c | 65 ++++++++++++++++++
> examples/l3fwd/main.c | 55 ++++++++++++++++
> 10 files changed, 293 insertions(+), 11 deletions(-)
>
Acked-by: Konstantin Ananyev <konstantin.ananyev at intel.com>
> --
> 2.1.4
More information about the dev
mailing list