[dpdk-dev] [PATCH v2 5/5] eal: remove compiler optimization workaround

The compiler optimization was disabled a long time ago without describing what was the exact issue. Maybe it does not apply anymore. As it looks unneeded, let's remove this strange pragma. Signed-off-by: Thomas Monjalon --- lib/librte_eal/common/eal_common_cpuflags.c | 13 - 1 file

[dpdk-dev] [PATCH v2 4/5] eal/ppc: adapt CPU flags check to the arch

The structure feature_entry does not need leaf/subleaf which were copied from x86 CPUID implementation. On x86, a valid flag is detected with the non-zero leaf value. This check is replaced by a check with a dummy "none" register. Signed-off-by: Thomas Monjalon ---

[dpdk-dev] [PATCH v2 3/5] eal/arm: adapt CPU flags check to the arch

The structure feature_entry does not need leaf/subleaf which were copied from x86 CPUID implementation. On x86, a valid flag is detected with the non-zero leaf value. This check is replaced by a check with a dummy "none" register. Signed-off-by: Thomas Monjalon ---

[dpdk-dev] [PATCH v2 2/5] eal: move CPU flag functions out of headers

The patch c344eab3ee has moved the hardware definition of CPU flags. Now the functions checking these hardware flags are also moved. The function rte_cpu_get_flag_enabled() is no more inline. The benefits are: - remove rte_cpu_feature_table from the ABI (recently added) - hide hardware details

[dpdk-dev] [PATCH v2 1/5] eal: get CPU flag name

The new function rte_cpu_get_flag_name() is added to the EAL API. It is implemented (duplicated) in each arch because the next patch will remove the public exposure of the feature tables. Signed-off-by: Thomas Monjalon --- lib/librte_eal/bsdapp/eal/rte_eal_version.map| 1 +

[dpdk-dev] [PATCH v2 0/5] clean-up cpuflags

Following the work of Ferruh, I suggest this cleanup to remove as much as possible of the code from the cpuflags headers. The goal is to un-inline these functions (not performance sensitive) and remove the CPU flags table from the ABI (just added recently). The bonus is to stop mimic x86 in ARM

[dpdk-dev] [PATCH] nfp: fix non-x86 build

The file sys/io.h was included but it can be unavailable in some non-x86 toolchains. As others system includes in the file nfp_net.c, it seems useless, so the easy fix is to remove them. Signed-off-by: Thomas Monjalon --- drivers/net/nfp/nfp_net.c | 11 --- 1 file changed, 11

[dpdk-dev] [PATCH v2] fm10k: handle err flags in vector RX func

From: "Chen Jing D(Mark)" Using SSE instructions to parse error flags in HW Rx descriptor, then set corresponding bits of mbuf. Signed-off-by: Chen Jing D(Mark) --- v2: - rebase to latest repo - fix a typo in the processing of HBO and IXE error flags

[dpdk-dev] [PATCH v2] doc: add Vector FM10K introductions

From: "Chen Jing D(Mark)" Add introductions on how to enable Vector FM10K Rx/Tx functions, the preconditions and assumptions on Rx/Tx configuration parameters. The new content also lists the limitations of vector, so app/customer can do better to select best Rx/Tx

[dpdk-dev] [PATCH v2 1/1] vhost: fix leak of fds and mmaps

Hey Rich, Sorry for the long delay; I barely forgot it :( On Tue, Jan 19, 2016 at 10:13:23AM -0800, Rich Lane wrote: > On Sun, Jan 17, 2016 at 11:58 PM, Yuanhan Liu > wrote: > > On Sun, Jan 17, 2016 at 11:57:18AM -0800, Rich Lane wrote: > > +/* > > + * Implementation-specific

[dpdk-dev] [PATCH v8 2/2] vhost: Add VHOST PMD

On Fri, Feb 05, 2016 at 08:28:13PM +0900, Tetsuya Mukawa wrote: > The patch introduces a new PMD. This PMD is implemented as thin wrapper > of librte_vhost. It means librte_vhost is also needed to compile the PMD. > The vhost messages will be handled only when a port is started. So start > a port

[dpdk-dev] [PATCH v8 1/2] ethdev: Add a new event type to notify a queue state changed event

On Fri, Feb 05, 2016 at 08:28:12PM +0900, Tetsuya Mukawa wrote: > This patch adds a below event type. > - RTE_ETH_EVENT_QUEUE_STATE_CHANGE > This event is used for notifying a queue state changed event. > > Signed-off-by: Tetsuya Mukawa > Acked-by: Ferruh Yigit > --- >

[dpdk-dev] DPDK i40evf problem in receving packet

Hi Qian -- Here's the data from Host: [root at oscompute3 ~]# ethtool -i p3p1 driver: i40e version: 1.0.11-k firmware-version: f4.40 a1.4 n04.53 e80001dc0 bus-info: :04:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes

[dpdk-dev] DPDK i40evf problem in receving packet

What's your current firmware info, can u run ethtool -i port_interface to check? Thanks Qian -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Saurabh Mishra Sent: Saturday, February 06, 2016 6:33 AM To: dev at dpdk.org; users at dpdk.org Subject: [dpdk-dev] DPDK