[dpdk-dev] [PATCH 5/5] vmxnet3: Some perf improvement on the rx path

Signed-off-by: Yong Wang --- lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c | 242 -- 1 file changed, 116 insertions(+), 126 deletions(-) diff --git a/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c b/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c index e2fb8a8..4799f4d 100644 --- a/lib/lib

[dpdk-dev] [PATCH 4/5] vmxnet3: Add rx pkt check offloads

Only supports IPv4 so far. Signed-off-by: Yong Wang --- lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c b/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c index 2017d4b..e2fb8a8 100644 --

[dpdk-dev] [PATCH 3/5] vmxnet3: Fix dev stop/restart bug

This change makes vmxnet3 consistent with other pmds in terms of dev_stop behavior: rather than releasing tx/rx rings, it only resets the ring structure and release the pending mbufs. Verified with various tests (test-pmd and pktgen) over vmxnet3 that dev stop/restart works fine. Signed-off-by: Y

[dpdk-dev] [PATCH 2/5] vmxnet3: Add VLAN Tx offload

Signed-off-by: Yong Wang --- lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c b/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c index 986e5e5..0b6363f 100644 --- a/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c +++ b/lib/librte_pm

[dpdk-dev] [PATCH 1/5] vmxnet3: Fix VLAN Rx stripping

Shouldn't reset vlan_tci to 0 if a valid VLAN tag is stripped. Signed-off-by: Yong Wang --- lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c b/lib/librte_pmd_vmxnet3/vmxnet3_rxtx.c index

[dpdk-dev] [PATCH 0/5] vmxnet3 pmd fixes/improvement

This patch series include various fixes and improvement to the vmxnet3 pmd driver. Yong Wang (5): vmxnet3: Fix VLAN Rx stripping vmxnet3: Add VLAN Tx offload vmxnet3: Fix dev stop/restart bug vmxnet3: Add rx pkt check offloads vmxnet3: Some perf improvement on the rx path lib/librte_pm

[dpdk-dev] [PATCH v4 10/10] VM Power Management Unit Tests

Updated the unit tests to cover both librte_power implementations as well as the external API. Signed-off-by: Alan Carew --- app/test/Makefile | 3 +- app/test/autotest_data.py | 26 ++ app/test/test_power.c | 445 +++--- app/test

[dpdk-dev] [PATCH v4 09/10] Build system integration for VM Power Management(Guest and Host)

librte_power now contains both rte_power_acpi_cpufreq and rte_power_kvm_vm implementations. Signed-off-by: Alan Carew --- lib/librte_power/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/librte_power/Makefile b/lib/librte_power/Makefile index 6185812..d672a5a 1

[dpdk-dev] [PATCH v4 08/10] Packet format for VM Power Management(Host and Guest).

Provides a command packet format for host and guest. Signed-off-by: Alan Carew --- lib/librte_power/channel_commands.h | 77 + 1 file changed, 77 insertions(+) create mode 100644 lib/librte_power/channel_commands.h diff --git a/lib/librte_power/channel_comma

[dpdk-dev] [PATCH v4 07/10] librte_power common interface for Guest and Host

Moved the current librte_power implementation to rte_power_acpi_cpufreq, with renaming of functions only. Added rte_power_kvm_vm implmentation to support Power Management from a VM. librte_power now hides the implementation based on the environment used. A new call rte_power_set_env() can explicid

[dpdk-dev] [PATCH v4 06/10] VM communication channels for VM Power Management(Guest).

Allows for the opening of Virtio-Serial devices on a VM, where a DPDK application can send packets to the host based monitor. The packet formatted is specified in channel_commands.h Each device appears as a serial device in path /dev/virtio-ports/virtio.serial.port.. where each lcore in a DPDK appl

[dpdk-dev] [PATCH v4 05/10] VM Power Management CLI(Guest).

Provides a small sample application(guest_vm_power_mgr) to run on a VM. The application is run by providing a core mask(-c) and number of memory channels(-n). The core mask corresponds to the number of lcore channels to attempt to open. A maximum of 64 channels per VM is allowed. The channels must

[dpdk-dev] [PATCH v4 04/10] VM Power Management application and Makefile.

For launching CLI thread and Monitor thread and initialising resources. Requires a minimum of two lcores to run, additional cores specified by eal core mask are not used. Signed-off-by: Alan Carew --- examples/vm_power_manager/Makefile | 57 ++ examples/vm_power_manager/main.c

[dpdk-dev] [PATCH v4 03/10] CPU Frequency Power Management(Host).

A wrapper around librte_power(using ACPI cpufreq), providing locking around the non-threadsafe library, allowing for frequency changes based on core masks and core numbers from both the CLI thread and epoll monitor thread. Signed-off-by: Alan Carew --- examples/vm_power_manager/power_manager.c |

[dpdk-dev] [PATCH v4 02/10] VM Power Management CLI(Host).

The CLI is used for administrating the channel monitor and manager and manually setting the CPU frequency on the host. Supports the following commands: add_vm [Mul-choice STRING]: add_vm|rm_vm , add a VM for subsequent operations with the CLI or remove a previously added VM from the VM Power

[dpdk-dev] [PATCH v4 01/10] Channel Manager and Monitor for VM Power Management(Host).

The manager is responsible for adding communications channels to the Monitor thread, tracking and reporting VM state and employs the libvirt API for synchronization with the KVM Hypervisor. The manager interacts with the Hypervisor to discover the mapping of virtual CPUS(vCPUs) to the host physical

[dpdk-dev] [PATCH v4 00/10] VM Power Management

Virtual Machine Power Management. The following patches add two DPDK sample applications and an alternate implementation of librte_power for use in virtualized environments. The idea is to provide librte_power functionality from within a VM to address the lack of MSRs to facilitate frequency chang

[dpdk-dev] [PATCH 0/7] Patches to split architecture specific operations from DPDK

David, I agree that your idea may be better for the splitting. However, as Bruce said, I think people would like to see the multi-architecture support feature of DPDK first. We can improve it gradually. Do you have some comments? Best Regards! -- Chao Zhu From:

[dpdk-dev] [PATCH 0/7] Patches to split architecture specific operations from DPDK

Cyril, Thanks for your comments! You are right. SSE needs to be splited. The current split is not a completed one. I'll continue to contribute. Best Regards! -- Chao Zhu (??) Research Staff Member Cloud Infrastructure and Technology Group IBM China Research Lab Buildi

[dpdk-dev] DPDK - VIRTIO performance problems

Hi I am checking performance DPDK VIRTIO mode running on KVM (Linux ubuntu 3.11.0-15-generic). The maximum throughput I reached was 4Gbps and then I saw an interesting phenomena. Every ~2min traffic stopped completely and then immediately came back. This happened in a periodic fashion. I have

[dpdk-dev] [PATCH v2 1/4] app/test: unit test for rx and tx cycles/packet

Hi Neil, Very appreciate your comments. I add inline reply, will send v3 asap when we get alignment. BRs, Liang Cunming > -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Saturday, October 11, 2014 1:52 AM > To: Liang, Cunming > Cc: dev at dpdk.org > Subje

[dpdk-dev] Newbie question about distributor library

Hi , Distributor was running as part of Rx core. Thanks, Reshma > -Original Message- > From: Wang, Shawn [mailto:xingbow at amazon.com] > Sent: Friday, October 10, 2014 10:06 PM > To: Pattan, Reshma; dev at dpdk.org > Subject: RE: Newbie question about distributor library > > 15.5 mpps

[dpdk-dev] DPDK - VIRTIO performance problems

On Sun, Oct 12, 2014 at 12:37:37PM +, Yan Freedland wrote: > Every ~2min traffic stopped completely and then immediately came back. This > happened in a periodic fashion. To me it sounds like it could be similar to what I've seen when I ran out of mbuf's or ran out of RX / TX descriptor entr