Re: [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture based on armv8-a

Hi, Regards, Liron -Original Message- From: Ruifeng Wang (Arm Technology China) Sent: Friday, May 24, 2019 10:51 To: Liron Himi ; tho...@monjalon.net Cc: dev@dpdk.org; nd Subject: [EXT] RE: [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture based on armv8-a External Email --

[dpdk-dev] [RFC PATCH 2/2] Convert dpaa driver to tag internal-only symbols appropriately

make use of the new __rte_internal tag to specify symbols that should only be used by dpdk provided libraries (as specified by the BUILDING_RTE_SDK cflag Signed-off-by: Neil Horman CC: Jerin Jacob Kollanukkaran CC: Bruce Richardson CC: Thomas Monjalon --- ...rimental-syms.sh => check-special-

[dpdk-dev] [RFC PATCH 1/2] Add __rte_internal tag for functions and version target

This tag is meant to be used on function prototypes to identify functions that are only meant to be used by internal DPDK libraries (i.e. libraries that are built while building the SDK itself, as identified by the defining of the BUILDING_RTE_SDK macro). When that flag is not set, it will resolve

[dpdk-dev] [RFC PATCH 0/2] introduce __rte_internal tag

Hey- Based on our recent conversations regarding the use of symbols only meant for internal dpdk consumption (between dpdk libraries), this is an idea that I've come up with that I'd like to get some feedback on Summary: 1) We have symbols in the DPDK that are meant to be used between DPDK

Re: [dpdk-dev] [PATCH v2] net/i40e: Fail rte_flow MARK requests if RX func was vectorized

> -Original Message- > From: Ergin, Mesut A > Sent: Saturday, May 25, 2019 6:50 AM > To: Xing, Beilei ; Zhang, Qi Z > Cc: dev@dpdk.org; Ergin, Mesut A > Subject: [PATCH v2] net/i40e: Fail rte_flow MARK requests if RX func was > vectorized > > Runtime requests to install an rte_flow wi

Re: [dpdk-dev] [PATCH 3/3] net/i40e: fix inadvertent override of vector RX allowance

Hi Muset: > -Original Message- > From: Ergin, Mesut A > Sent: Saturday, May 25, 2019 2:09 AM > To: Zhang, Qi Z ; Xing, Beilei > Cc: dev@dpdk.org > Subject: RE: [PATCH 3/3] net/i40e: fix inadvertent override of vector RX > allowance > > Hi, > > > > > > i40e_rx_vec_dev_conf_condition_chec

[dpdk-dev] [PATCH] net/mlx5: fix event handler uninstall

When device is being closed and tries to unregister interrupt callback, there is a chance the handler is still active (called in context of eal_intr_thread_main thread). If so the rte_intr_callback_unregister returns -EAGAIN and keeps the handler registered, causing crash when underlaying resourse