[dpdk-dev] [PATCH v2 01/16] Separate igb_uio mapping into a separate file

In order to make the code a bit more clean while using multiple drivers, IGB_UIO mapping has been separated into its own file. Signed-off-by: Anatoly Burakov Test-by: HuilongX Xu mailto:huilongx.xu at intel.com>> Compile pass >>Compile OS: FC20 x86_64 >>Kernel version: 3.13.6-200 >

[dpdk-dev] [PATCH v2 02/16] Distinguish between legitimate failures and non-fatal errors

Currently, EAL does not distinguish between actual failures and expected initialization errors. E.g. sometimes the driver fails to initialize because it was not supposed to be initialized in the first place, such as device not being managed by said driver. This patch makes EAL fail on actual initi

[dpdk-dev] [PATCH v2 03/16] Rename RTE_PCI_DRV_NEED_IGB_UIO to RTE_PCI_DRV_NEED_MAPPING

Rename the RTE_PCI_DRV_NEED_IGB_UIO to be more generic, retain old macro for backwards compatibility. Probably should be removed in one of the next releases. Signed-off-by: Anatoly Burakov Test-by: HuilongX Xu Compile pass >>Compile OS: FC20 x86_64 >>Kernel version: 3.13.6-200 >>G

[dpdk-dev] [PATCH v2 04/16] Make igb_uio compilation optional

Currently, igb_uio is always compiled. Some Linux distribution may not want to include igb_uio by default, so we need to make sure that igb_uio compilation can be optional. Signed-off-by: Anatoly Burakov mailto:anatoly.burakov at intel.com>> Test-by: HuilongX Xu mailto:huilongx.xu at intel.com>> C

[dpdk-dev] [PATCH v2 05/16] Moved interrupt type out of igb_uio

Moving interrupt type enum out of igb_uio and renaming it to be more generic. Such a strange header naming and separation is done mostly to make coming virtio patches easier to port to dpdk.org tree. Signed-off-by: Anatoly Burakov Test-by: HuilongX Xu Compile pass >>Compile OS: FC20 x86_64

[dpdk-dev] [PATCH v2 06/16] Add support for VFIO in Linuxapp targets

Make VFIO compilation optional for all configs. Signed-off-by: Anatoly Burakov http://dpdk.org/ml/listinfo/dev>> Test-by: HuilongX Xu Compile pass >>Compile OS: FC20 x86_64 >>Kernel version: 3.13.6-200 >>GCC version: 4.8.2 >>Server: Crownpass --- config/defconfig_i6

[dpdk-dev] [PATCH v2 06/16] Add support for VFIO in Linuxapp targets

Make VFIO compilation optional for all configs. Signed-off-by: Anatoly Burakov http://dpdk.org/ml/listinfo/dev>> Test-by: HuilongX Xu Compile pass >>Compile OS: FC20 x86_64 >>Kernel version: 3.13.6-200 >>GCC version: 4.8.2 >>Server: Crownpass --- config/defconfig_

[dpdk-dev] [PATCH v2 05/16] Moved interrupt type out of igb_uio

Moving interrupt type enum out of igb_uio and renaming it to be more generic. Such a strange header naming and separation is done mostly to make coming virtio patches easier to port to dpdk.org tree. Signed-off-by: Anatoly Burakov Test-by: HuilongX Xu Compile pass >>Compile OS: FC20 x86_64

[dpdk-dev] [PATCH v2 07/16] Add support for VFIO interrupts, add VFIO header

Creating code to handle VFIO interrupts in EAL interrupts, and also adding a header eal_vfio.h. This header checks two things: * checks if CONFIG_RTE_EAL_VFIO was enabled during build time * checks that kernel version is 3.6+ so that DPDK would still compile on older kernels despite VFIO compila

[dpdk-dev] [PATCH v2 08/16] Add support for mapping devices through VFIO.

VFIO is kernel 3.6+ only, and so is only compiled when DPDK config option CONFIG_RTE_EAL_VFIO is enabled, and kernel 3.6 or higher is detected, thus preventing compile failures on older kernels if VFIO is enabled in config (and it is, by default). Since VFIO cannot be used to map the same device t

[dpdk-dev] [PATCH v2 09/16] Enable VFIO device binding

Add support for binding VFIO devices if RTE_PCI_DRV_NEED_IGB_UIO is set for this driver. Try VFIO first, if not mapped then try IGB_UIO too. Signed-off-by: Anatoly Burakov Test-by: HuilongX Xu huilongx.xu at intel.com Compile pass >>Compile OS: FC20 x86_64 >>Kernel version: 3.

[dpdk-dev] [PATCH v2 10/16] Added support for selecting VFIO interrupt type from EAL command-line

Anatoly Burakov anatoly.burakov at intel.com Mon May 19 17:51:43 CEST 2014 Previous message: [dpdk-dev] [PATCH v2 09/16] Enable VFIO device binding Next message: [dpdk-dev] [PATCH v2 10/16] Added support for selecting VFIO interrupt type from EAL command-line Messages sorted by: [ date ] [ thread

[dpdk-dev] [PATCH v2 11/16] Make --no-huge use mmap instead of malloc

This makes it possible to run DPDK without hugepage memory when VFIO is used, as VFIO uses virtual addresses to set up DMA mappings. Signed-off-by: Anatoly Burakov http://dpdk.org/ml/listinfo/dev>> Test-by: HuilongX Xu huilongx.xu at intel.com Compile pass

[dpdk-dev] [PATCH v2 12/16] Adding unit tests for VFIO EAL command-line parameter

Adding unit tests for VFIO interrupt type command-line parameter. We don't know if VFIO is compiled (eal_vfio.h header is internal to Linuxapp EAL), so we check this flag regardless. Signed-off-by: Anatoly Burakov http://dpdk.org/ml/listinfo/dev>> Test-by: HuilongX Xu Compile pass >>Compi

[dpdk-dev] [PATCH v2 12/16] Adding unit tests for VFIO EAL command-line parameter

Adding unit tests for VFIO interrupt type command-line parameter. We don't know if VFIO is compiled (eal_vfio.h header is internal to Linuxapp EAL), so we check this flag regardless. Signed-off-by: Anatoly Burakov http://dpdk.org/ml/listinfo/dev>> Test-by: HuilongX Xu Compile pass >>Comp

[dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio

Note that since igb_uio no longer has a PCI ID list, it can now be bound to any device, not just those explicitly supported by DPDK. In other words, it now behaves similar to PCI stub, VFIO and other generic PCI drivers. Therefore to bind a new device to igb_uio, the user will now have to first wr

[dpdk-dev] [PATCH v2 14/16] Renamed igb_uio_bind to dpdk_nic_bind

Renaming the igb_uio_bind script to dpdk_nic_bind to have a generic name since we're now supporting two drivers. Signed-off-by: Anatoly Burakov http://dpdk.org/ml/listinfo/dev>> Test-by: HuilongX Xu Compile pass >>Compile OS: FC20 x86_64 >>Kernel version: 3.13.6-200 >>GCC

[dpdk-dev] [PATCH v2 15/16] Added support for VFIO drivers in dpdk_nic_bind.py

Since igb_uio no longer has a PCI ID list, the script will no longer distinguish between supported and unsupported NICs. There's a weird behaviour of sysfs when a new device ID is added to new_id. Subsequent writing to "bind" will result in IOError on closing the file. This error is harmless but i

[dpdk-dev] [PATCH v2 16/16] Adding support for VFIO to setup.sh

Support for loading/unloading VFIO drivers, binding/unbinding devices to/from VFIO, also setting up correct userspace permissions. Signed-off-by: Anatoly Burakov Test-by: HuilongX Xu huilongx.xu at intel.com Based-commit: 356cb732d5381140f42ef8b55492339579854986 Compile patch: pass Function test(

[dpdk-dev] [PATCH v2 4/5] i40e: set crc stripping in rx queue configuration

Tested-by: HuilongX xu This patch has been verified on FC20 with eagle fountain:4*10G fortville, spirit falls 1*40G fortville and 2*40G fortville. The VF is greater by SRIOV, and testpmd should be run on host to support VF work on VM. CRC stripping function works well in the testpmd app in VM

[dpdk-dev] [PATCH 00/15] i40e base driver update

Tested-by: HuilongX xu This patch has been verified on FC20 with Eagle Fountain: 4*10G , Spirit Falls: 1*40G fortvill and 2*40G fortvill. The i40e base driver update patch works well on FC20 with basic function and performance. The test environment detail information as the following: HOST env

[dpdk-dev] [PATCH] i40evf: fix of supporting jumbo frame

Tested-by:huilong xu - Tested Commit: 0095bb6dd77a6b4570af27320187e63bf37500c6 - OS: FC20 3.11.10-301.fc20.x86_64 - GCC: gcc version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC) - CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz - NIC: Ethernet controller [0200]: Intel Corporation Ethernet Controlle

[dpdk-dev] [PATCH v2] i40e: fix for ieee15888 with rte_next_abi

Tested-by:huilong xu Os: dpdk-fedora20 3.11.10-301.fc20.x86_64 Gcc: 4.8.3 20140911 (Red Hat 4.8.3-7) NIC: fortville_spirit_single Package:dpdk.org newest code(commit 921353134fe01606411d3508f3ca798f0a38da73) + patch Test case :ieee 1588 disable and ieee 1588 enable all passed. Test steps: 1. enab

[dpdk-dev] [PATCH v2 0/2] Increase number of next hops for LPM IPv4

Tested-by: huilong xu Run two unit case, are all passed. Test environment: OS: Linux ub12 3.13.0-32-generic #57~precise1-Ubuntu SMP Tue Jul 15 03:51:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Gcc: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) Package: dpdk.org next branch + patch NIC: 09:00.0

[dpdk-dev] [PATCH v3 0/6] new ntuple filter replaces 2tuple and 5tuple filters

package by port 0 queue 0 -Original Message- From: Wu, Jingjing Sent: Tuesday, February 10, 2015 12:48 PM To: dev at dpdk.org Cc: Wu, Jingjing; De Lara Guarch, Pablo; Cao, Min; Xu, HuilongX Subject: [PATCH v3 0/6] new ntuple filter replaces 2tuple and 5tuple filters v2 changes

[dpdk-dev] [PATCH] i40e: remove ALLOW_LB flag on SRIOV vsi

2015 3:32 PM To: dev at dpdk.org Cc: Wu, Jingjing; Xu, HuilongX; Zhang, Helin Subject: [PATCH] i40e: remove ALLOW_LB flag on SRIOV vsi Disable VEB switching by removing ALLOW_LB on SRIOV vsi. If the source mac address of packet sent from VF is not listed in the VEB's mac table, the VEB will s

[dpdk-dev] [PATCH v6 00/13] mbuf: enhancements of mbuf clones

Hi Olivier, Today I find a compile error, when I test ip fragment on dpdk.org. would you check this? thanks a lot. My dpdk.org commit: a6d71fa7146cc04320c2485d6dde44c1d888d652 The compile error as below: CC main.o /root/dpdk/examples/ip_fragmentation/main.c: In function 'init_mem': /root/dpdk/exa

[dpdk-dev] [PATCH 00/52] update i40e base driver

; To: dev at dpdk.org > Cc: Wu, Jingjing; Lu, Wenzhuo; Xu, HuilongX; Zhang, Helin > Subject: [PATCH 00/52] update i40e base driver > > Here is the update of i40e base driver. > Main update: > - support New X722 Device (FortPark) > - extend virtual channel interface > - suppo

[dpdk-dev] mutli process C/S model example init failed on xen dom0 with dpdk-16.07 rc2 package

Hi all, I run mutli procee C/S model example failed on xen dom0. Does anyone give me some suggest how to debug it? Thanks a lot test environment: OS&kernel: 3.17.4-301.fc21.x86_64 Gcc version: gcc version 4.9.2 20141101 (Red Hat 4.9.2-1) (GCC) Package :dpdk.16.07-rc1.tar.gz Target: x86_64-n

[dpdk-dev] about memzone name size issue

Hi , I will tester-by this patch, thanks a lot. > -Original Message- > From: Iremonger, Bernard > Sent: Tuesday, May 31, 2016 9:59 PM > To: Wiles, Keith; Xu, HuilongX; dev at dpdk.org > Subject: RE: [dpdk-dev] about memzone name size issue > > Hi Huilong, > &

[dpdk-dev] [PATCH] app/test: fix bond device name too long

Tester-by: huilong xu Test case: link_bonging_autotest Package:dpdk.org master branch newest commit + this patch Test cmdline: ./x86_64-native-linuxapp-gcc/app/test -c -n 1 Exec link_bonging_autotest cmdl Test environment: OS&kernel: dpdk-rhel72 3.10.0-327.el7.x86_64 Gcc: gcc ver

[dpdk-dev] [PATCH] app/test: fix bond device name too long

Test case: link_bonging_autotest Package:dpdk.org master branch newest commit + this patch Test cmdline: ./x86_64-native-linuxapp-gcc/app/test -c -n 1 Exec link_bonging_autotest cmdl Test environment: OS&kernel: dpdk-rhel72 3.10.0-327.el7.x86_64 Gcc: gcc version 4.8.5 20150623

[dpdk-dev] [PATCH] mk:fix second compile error

Hi Thomas, Could you give me some comments about this patch. Thanks a lot > -Original Message- > From: Xu, HuilongX > Sent: Tuesday, August 09, 2016 2:02 PM > To: dev at dpdk.org > Cc: Xu, HuilongX > Subject: [dpdk-dev][PATCH] mk:fix second compile error > > when c

[dpdk-dev] [PATCH] mk:fix second compile error

Hi Brue, Thanks a lot for your comments. I will send V2 patch. > -Original Message- > From: Richardson, Bruce > Sent: Tuesday, August 09, 2016 4:27 PM > To: Xu, HuilongX > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH] mk:fix second compile error > > On Tu

[dpdk-dev] [PATCH] ixgbe: fix x550 VF tx issue

Test-by: huilong xu Summary: Test four case, and all case passed. Test environment: Host: os: 4.2.3-300.fc23.x86_64 NIC: 03:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T [8086:15ad] NIC kernel driver: ixgbe 4.2.5 Guest:

[dpdk-dev] about memzone name size issue

Hi all, I find a issue on link_bonding unit test case. When I run model6 test case, will generate core dump error. I debug it, find the error code in function: rte_mempool_create_empty(const char *name, unsigned n, unsigned elt_size, unsigned cache_size, unsigned private_data_size,

[dpdk-dev] [PATCH 0/8] Dynamic RSS Configuration for Bonding

Tested-by: huilong xu - Tested Commit: 1a1109404e702d3ad1ccc1033df55c59bec1f89a + PATCH - OS: Linux dpdk-fedora20 3.11.10-301.fc20.x86_64 - GCC: gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC) - CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz - NIC: Intel Corporation 82599ES 10-Gigabit SFI/SFP+

[dpdk-dev] [PATCH v2 0/4] extend flow director to support L2_paylod type

Jingjing; Zhang, Helin; Xu, HuilongX > Subject: [PATCH v2 0/4] extend flow director to support L2_paylod type > > This patch set extends flow director to support L2_paylod type in i40e > driver. > > v2 change: > - remove the flow director VF filtering from this patch to avoid