> -Original Message-
> From: Liang, Cunming
> Sent: Thursday, August 06, 2015 10:19 AM
> To: dev at dpdk.org
> Cc: Mcnamara, John; david.marchand at 6wind.com; Liang, Cunming
> Subject: [PATCH v1] doc: prog_guide update for RX interrupt event
>
> The patch updates the
Suggest you post this question to Openvswitch.org.
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of wenxu
> Sent: Tuesday, August 04, 2015 5:52 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] Vhost-User port not work and always show 'down'
>
> Hi all,
>
>
On your system, what is your iommu and intel_iommu kernel parameters?
Could you try to use uio_pci_generic for both PF on host and VF in guest after
configuring "iommu=pt" on your system?
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Andrew Theurer
>
Acked-by: Danny Zhou
> -Original Message-
> From: Liang, Cunming
> Sent: Friday, June 05, 2015 4:20 PM
> To: dev at dpdk.org
> Cc: shemming at brocade.com; david.marchand at 6wind.com; thomas.monjalon at
> 6wind.com; Zhou, Danny; Wang, Liang-min;
> Richardson, Bruc
; From: James (Fei) Liu-SSI [mailto:james.liu at ssi.samsung.com]
> Sent: Thursday, April 30, 2015 2:26 AM
> To: Zhou, Danny; dev at dpdk.org
> Cc: Liang, Cunming
> Subject: RE: [dpdk-dev] Issues of MSIx interrupt enable with user space driver
>
> Hi Danny,
>
> Thanks a lot
The V6 "Interrupt PMD" patch has been sent out to DPDK.org 2 months ago, and V7
is under development with changes
to include more generic APIs that could support all kinds of interrupts (e.g.
HW Rx interrupt and SW ring interrupt).
Stay tuned.
> -Original Message-
> From: dev
easier for any Linux distribution to package DPDK.
> -Original Message-
> From: Stephen Hemminger [mailto:stephen at networkplumber.org]
> Sent: Wednesday, April 15, 2015 9:06 AM
> To: Zhou, Danny; Richardson, Bruce; Doherty, Declan
> Cc: dev at dpdk.org
> Subject: UIO p
is expected.
> -Original Message-
> From: Olga Shern [mailto:olgas at mellanox.com]
> Sent: Monday, April 13, 2015 4:39 AM
> To: Raghav Sethi; Zhou, Danny; dev at dpdk.org
> Subject: RE: [dpdk-dev] Mellanox Flow Steering
>
> Hi Raghav,
>
> You are right with your
Currently, the DPDK PMD and NIC kernel driver cannot drive a same NIC device
simultaneously. When you
use ethtool to setup flow director filter, the rules are written to NIC via
ethtool support in kernel driver. But when
DPDK PMD is loaded to drive same device, the rules previously written by
e1000 driver supports many different NIC devices.
Do you know your NIC device type or device_id?
> -Original Message-
> From: Olivier Deme [mailto:odeme at druidsoftware.com]
> Sent: Sunday, April 05, 2015 1:03 AM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject:
Which NIC device are you using now?
KNI does not provide Ethtool support for all NICs supported by the Poll-Mode
Drivers.
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Olivier Deme
> Sent: Friday, April 03, 2015 10:03 PM
> To: dev at dpdk.org
> Subject:
Container itself is not considered as a secured solution that could provide
strict resource isolation which
VT could provide. Basically, we have 4 different configuration as below, you
could pick most appropriate one
depending on usage scenarios.
1) VT + VFIO: supposed to be the most secured
DPDK 2.0 support uio_pci_geneic this in_kernel module so you do not need to
insmod igb_uio, and rte_kni module can hardly been
upstreamed to net_dev, but it is not a must-to-have module to load if you do
not use KNI feaure.
> -Original Message-
> From: dev [mailto:dev-bounces at
From: David Marchand [mailto:david.march...@6wind.com]
Sent: Wednesday, February 25, 2015 6:22 PM
To: Zhou, Danny
Cc: dev at dpdk.org; Liang, Cunming
Subject: Re: [dpdk-dev] [PATCH v5 5/6] eal: add per rx queue interrupt handling
based on VFIO
Hello Danny,
On Wed, Feb 25, 2015 at 7:58 AM
Thanks for comments and please see my answers inline.
From: David Marchand [mailto:david.march...@6wind.com]
Sent: Tuesday, February 24, 2015 6:42 PM
To: Zhou, Danny
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] [PATCH v5 5/6] eal: add per rx queue interrupt handling
based on VFIO
Hello Danny
You can do it but it will not sync with DPDK. In current KNI implementation,
the devices'
I/O address spaces are mapped to both userspace DPDK and kenrelspace KNI, so one
can control the NIC device independently(using ethtool for KNI and ethdev APIs
for DPDK)
without synchronization.
In theory,
v5 changes
- Change invoked function name and parameter to accomodate EAL change
v3 changes
- Add spinlock to ensure thread safe when accessing interrupt mask
register
v2 changes
- Remove unused function which is for debug purpose
Demonstrate how to handle per rx queue interrupt in a
v5 changes
- Rebase the patchset onto the HEAD
- Isolate ethdev from EAL for new-added wait-for-rx interrupt function
- Export wait-for-rx interrupt function for shared libraries
v4 changes:
- Adjust position of new-added structure fields
v3 changes:
- Fix review comments
v2 changes:
- Fix
v5 changes
- Rebase the patchset onto the HEAD
v3 changes
- Remove unnecessary variables in e1000_mac_info
- Remove spinlok from PMD
v2 changes
- Consolidate review comments related to coding style
The patch does below for igb PF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register
v5 changes
- Rebase the patchset onto the HEAD
v3 changes
- Remove spinlok from PMD
v2 changes
- Consolidate review comments related to coding style
The patch does below things for ixgbe PF and VF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to
v5 changes:
- Create this new patch file for changed struct rte_intr_handle that
other patches depend on, to avoid breaking git bisect.
Signed-off-by: Danny Zhou
Tested-by: Yong Liu
---
lib/librte_eal/linuxapp/eal/include/exec-env/rte_interrupts.h | 4
1 file changed, 4 insertions(+)
v5 changes
- Rebase the patchset onto the HEAD
v4 changes
- Export interrupt enable/disable functions for shared libraries
- Put new functions at the end of eth_dev_ops to avoid breaking ABI
v3 changes
- Add return value for interrupt enable/disable functions
Add two dev_ops functions to enable
v5 changes
- Rebase the patchset onto the HEAD
- Isolate ethdev from EAL for new-added wait-for-rx interrupt function
- Export wait-for-rx interrupt function for shared libraries
- Split-off a new patch file for changed struct rte_intr_handle that
other patches depend on, to avoid breaking git
> -Original Message-
> From: Stephen Hemminger [mailto:stephen at networkplumber.org]
> Sent: Tuesday, February 24, 2015 12:59 AM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v5 1/6] ethdev: add rx interrupt
> enable/disable functions
>
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Monday, February 23, 2015 11:19 PM
> To: Zhou, Danny
> Cc: Gonzalez Monroy, Sergio; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4 4/5] eal: add per rx queue interrupt
> h
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Monday, February 23, 2015 9:20 PM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4 2/5] ixgbe: enable rx queue interrupts for
> both PF and VF
>
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Monday, February 23, 2015 9:28 PM
> To: Zhou, Danny
> Cc: Gonzalez Monroy, Sergio; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4 4/5] eal: add per rx queue interrupt
> h
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Saturday, February 21, 2015 6:44 AM
> To: Zhou, Danny; Gonzalez Monroy, Sergio
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4 4/5] eal: add per rx queue interrupt
> -Original Message-
> From: Jun Xiao [mailto:jun.xiao at cloudnetengine.com]
> Sent: Saturday, February 21, 2015 10:57 AM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4 4/5] eal: add per rx queue interrupt
> handling based on VFIO
>
njalon at 6wind.com]
> Sent: Monday, February 23, 2015 7:20 PM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4 2/5] ixgbe: enable rx queue interrupts for
> both PF and VF
>
> 2015-02-19 21:48, Zhou Danny:
> > + /* set max interrup
Add uio_pci_generic to the list of supported kernel drivers.
Signed-off-by: Danny Zhou
Tested-by: Qun Wan
---
tools/dpdk_nic_bind.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/dpdk_nic_bind.py b/tools/dpdk_nic_bind.py
index 812b6a1..2483056 100755
---
enable/disable interrupt by manipulating a control bit of command
register on NIC's PCIe configuration space.
Signed-off-by: Danny Zhou
Tested-by: Qun Wan
---
lib/librte_eal/linuxapp/eal/eal_interrupts.c | 68 +---
1 file changed, 52 insertions(+), 16 deletions(-)
diff
v2 changes:
- Change variable name of kernel driver with precise comment.
- Fix a union definition error in v1 patchset.
- Move redefined macro IORESOURCE_MEM to rte_pci.h with comment.
1) Unify procedure to retrieve BAR resource mapping information.
2) Setup bus master bit in NIC's PCIe
v2 changes:
- Change variable name of kernel driver with precise comment
- Fix a union definition error in v1 patchset
- Move redefined macro IORESOURCE_MEM to rte_pci.h with comment
Linux kernel provides UIO as well as VFIO mechanism to support writing user
space device driver. Comparing to UIO
v3 changes
- Add spinlock to ensure thread safe when accessing interrupt mask
register
v2 changes
- Remove unused function which is for debug purpose
Demonstrate how to handle per rx queue interrupt in a NAPI-like
implementation in usersapce. PDK polling thread mainly works in
polling mode and
v4 changes:
- Adjust position of new-added structure fields
v3 changes:
- Fix review comments
v2 changes:
- Fix compilation issue for a missed header file
- Bug fix: free unreleased resources on the exception path before return
- Consolidate coding style related review comments
This patch does
v3 changes
- Remove unnecessary variables in e1000_mac_info
- Remove spinlok from PMD
v2 changes
- Consolidate review comments related to coding style
The patch does below for igb PF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to vectors
- Implement
v3 changes
- Remove spinlok from PMD
v2 changes
- Consolidate review comments related to coding style
The patch does below things for ixgbe PF and VF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to vectors
- Implement interrupt enable/disable
v4 changes
- Export interrupt enable/disable functions for shared libraries
- Put new functions at the end of eth_dev_ops to avoid breaking ABI
v3 changes
- Add return value for interrupt enable/disable functions
Add two dev_ops functions to enable and disable rx queue interrupts
Signed-off-by:
v4 changes
- Export interrupt enable/disable functions for shared libraries
- Adjust position of new-added structure fields and functions to
avoid breaking ABI
v3 changes
- Add return value for interrupt enable/disable functions
- Move spinlok from PMD to L3fwd-power
- Remove unnecessary
Thomas, thanks for review and I added comments inline.
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Wednesday, February 18, 2015 9:40 PM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v
> -Original Message-
> From: Neil Horman [mailto:nhorman at tuxdriver.com]
> Sent: Thursday, February 19, 2015 9:10 PM
> To: Zhou, Danny
> Cc: Gonzalez Monroy, Sergio; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 1/5] ethdev: add rx interrupt
> ena
> -Original Message-
> From: Gonzalez Monroy, Sergio
> Sent: Thursday, February 19, 2015 4:22 PM
> To: Zhou, Danny; Neil Horman
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 1/5] ethdev: add rx interrupt
> enable/disable functions
>
> On 19/02/20
> -Original Message-
> From: Neil Horman [mailto:nhorman at tuxdriver.com]
> Sent: Tuesday, February 17, 2015 11:59 PM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 4/5] eal: add per rx queue interrupt
> handling based on VFIO
>
> -Original Message-
> From: Neil Horman [mailto:nhorman at tuxdriver.com]
> Sent: Tuesday, February 17, 2015 11:53 PM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 1/5] ethdev: add rx interrupt
> enable/disable functions
>
> On
> -Original Message-
> From: Neil Horman [mailto:nhorman at tuxdriver.com]
> Sent: Tuesday, February 17, 2015 11:55 PM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 1/5] ethdev: add rx interrupt
> enable/disable functions
>
> On
v3 changes
- Add spinlock to ensure thread safe when accessing interrupt mask
register
v2 changes
- Remove unused function which is for debug purpose
Demonstrate how to handle per rx queue interrupt in a NAPI-like
implementation in usersapce. PDK polling thread mainly works in
polling mode and
v3 changes:
- Fix review comments
v2 changes:
- Fix compilation issue for a missed header file
- Bug fix: free unreleased resources on the exception path before return
- Consolidate coding style related review comments
This patch does below:
- Create multiple VFIO eventfd for rx queues.
- Handle
v3 changes
- Remove unnecessary variables in e1000_mac_info
- Remove spinlok from PMD
v2 changes
- Consolidate review comments related to coding style
The patch does below for igb PF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to vectors
- Implement
v3 changes
- Remove spinlok from PMD
v2 changes
- Consolidate review comments related to coding style
The patch does below things for ixgbe PF and VF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to vectors
- Implement interrupt enable/disable
v3 changes
- Add return value for interrupt enable/disable functions
Add two dev_ops functions to enable and disable rx queue interrupts
Signed-off-by: Danny Zhou
Tested-by: Yong Liu
---
lib/librte_ether/rte_ethdev.c | 43
lib/librte_ether/rte_ethdev.h | 57
v3 changes
- Add return value for interrupt enable/disable functions
- Move spinlok from PMD to L3fwd-power
- Remove unnecessary variables in e1000_mac_info
- Fix miscelleous review comments
v2 changes
- Fix compilation issue in Makefile for missed header file.
- Consolidate internal and
> -Original Message-
> From: Liang, Cunming
> Sent: Friday, February 13, 2015 11:48 AM
> To: Zhou, Danny; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2 4/5] eal: add per rx queue interrupt
> handling based on VFIO
>
> Hi,
>
> > -Or
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Zhou, Danny
> Sent: Friday, February 13, 2015 10:48 AM
> To: Ananyev, Konstantin; Liang, Cunming; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 3/5] igb: enable rx queue in
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Thursday, February 12, 2015 6:29 PM
> To: Liang, Cunming; Zhou, Danny; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2 3/5] igb: enable rx queue interrupts for PF
>
>
>
> > -Origi
> -Original Message-
> From: Stephen Hemminger [mailto:stephen at networkplumber.org]
> Sent: Wednesday, February 04, 2015 7:43 AM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 1/5] ethdev: add rx interrupt
> enable/disable functions
>
> -Original Message-
> From: Stephen Hemminger [mailto:stephen at networkplumber.org]
> Sent: Wednesday, February 04, 2015 7:40 AM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 0/5] Interrupt mode for PMD
>
> On Tue, 3 Feb 2015 16:
v2 change
- Remove unused function which is for debug purpose
Demonstrate how to handle per rx queue interrupt in a NAPI-like
implementation in usersapce. PDK polling thread mainly works in
polling mode and switch to interrupt mode only if there is no
any packet received in recent polls.
v2 change:
- Fix compilation issue for a missed header file
- Bug fix: free unreleased resources on the exception path before return
- Consolidate coding style related review comments
This patch does below:
- Create multiple VFIO eventfd for rx queues.
- Handle per rx queue interrupt.
- Eliminate
v2 changes
- Consolidate review comments related to coding style
The patch does below for igb PF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to vectors
- Implement interrupt enable/disable functions
Signed-off-by: Danny Zhou
Tested-by: Yong Liu
---
v2 changes
- Consolidate review comments related to coding style
The patch does below things for ixgbe PF and VF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to vectors
- Implement interrupt enable/disable functions
Signed-off-by: Danny Zhou
> -Original Message-
> From: Qiu, Michael
> Sent: Thursday, January 29, 2015 11:40 AM
> To: Zhou, Danny; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v1 2/5] ixgbe: enable rx queue interrupts for
> both PF and VF
>
> On 1/28/2015 5:52 PM, Danny Zhou wrote:
> -Original Message-
> From: Qiu, Michael
> Sent: Thursday, January 29, 2015 1:07 PM
> To: Zhou, Danny; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v1 4/5] eal: add per rx queue interrupt
> handling based on VFIO
>
> On 1/28/2015 5:52 PM, Danny Zhou wrote:
> -Original Message-
> From: Liang, Cunming
> Sent: Thursday, January 29, 2015 2:34 AM
> To: Zhou, Danny; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v1 5/5] L3fwd-power: enable one-shot rx
> interrupt and polling/interrupt mode switch
>
>
>
Thanks for review Steve. Comments inline.
> -Original Message-
> From: Liang, Cunming
> Sent: Thursday, January 29, 2015 2:10 AM
> To: Zhou, Danny; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v1 4/5] eal: add per rx queue interrupt
> handling based on VFIO
>
&g
Thanks Ivan for your time spending on reviewing the patchset. Will fix those
issues
When submitting official patchset.
> -Original Message-
> From: Ivan Boule [mailto:ivan.boule at 6wind.com]
> Sent: Friday, January 23, 2015 5:22 PM
> To: Zhou, Danny; dev at dpdk.org
&
DPDK KNI(Kernel NIC interface) is your only option before bifurcated driver is
adopted.
Basically, DPDK rx/tx all packets and do flow classification (e.g. 5-tuple
based) in user
space then distribute control plane packets to KNI netdev in kernel space via
lockless queue based ring. The KNI
DPDK does not have PMD to support veth. I guess you might want to try to run
DPDK in container, right?
If that is the case, you have to assign a NIC's PF or VF to container to be
driven by DPDK PMD.
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Sachin
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Bruce Richardson
> Sent: Tuesday, November 25, 2014 11:03 PM
> To: Walukiewicz, Miroslaw
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [RFC PATCH 0/6] DPDK support to bifurcated driver
>
> On Tue, Nov 25,
Hope summary below could answer your questions.
From: lukego at gmail.com [mailto:luk...@gmail.com] On Behalf Of Luke Gorrie
Sent: Monday, November 24, 2014 7:58 PM
To: Thomas Monjalon
Cc: Zhou, Danny; dev at dpdk.org; Fastabend, John R
Subject: Re: [dpdk-dev] bifurcated driver
On 5 November
have plan to
support MP/MC in kernel part of KNI as well?
From: Robert Sanford [mailto:rsanfo...@gmail.com]
Sent: Thursday, November 20, 2014 4:49 AM
To: Zhou, Danny; dev at dpdk.org
Subject: Re: [dpdk-dev] Enhance KNI DPDK-app-side to be Multi-Producer/Consumer
Hi Danny,
On Fri, Nov 14, 2014
It will be always good if you can submit the RFC patch in terms of KNI
optimization.
On the other hand, do you have any perf. data to prove that your patchset could
improve
KNI performance which is the concern that most customers care about? We
introduced
multiple-threaded KNI kernel support
cated driver
solution depends on.
> -Original Message-
> From: Vincent JARDIN [mailto:vincent.jardin at 6wind.com]
> Sent: Thursday, November 06, 2014 9:31 AM
> To: Zhou, Danny
> Cc: Thomas Monjalon; dev at dpdk.org; Fastabend, John R; Or Gerlitz
> Subject: Re: [dpdk-dev] bif
lon [mailto:thomas.monjalon at 6wind.com]
> Sent: Wednesday, November 05, 2014 9:01 PM
> To: Zhou, Danny
> Cc: dev at dpdk.org; Fastabend, John R
> Subject: Re: [dpdk-dev] bifurcated driver
>
> Hi Danny,
>
> 2014-10-31 17:36, O'driscoll, Tim:
> > Bifurcated Driver (Danny.Zhou at
From: Alex Markuze [mailto:a...@weka.io]
Sent: Wednesday, November 05, 2014 11:19 PM
To: Thomas Monjalon
Cc: Zhou, Danny; dev at dpdk.org; Fastabend, John R
Subject: Re: [dpdk-dev] bifurcated driver
On Wed, Nov 5, 2014 at 5:14 PM, Alex Markuze mailto:alex at
weka.io>> wrote:
On Wed,
to IvyBridge/Haswell, there is NO
performance impact for 10G NIC.
-Danny
From: Shivapriya Hiremath [mailto:shivpr...@gmail.com]
Sent: Tuesday, October 28, 2014 1:28 AM
To: Zhou, Danny
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] Why do we need iommu=pt?
Hi Danny,
Your reply was very helpful
Shivapriya?
It is still ongoing as we need to run it on different Xeon server
platform like SandyBridge and IvyBridge, will post summary result
here once it is ready.
-Danny
From: Shivapriya Hiremath [mailto:shivpr...@gmail.com]
Sent: Tuesday, October 28, 2014 1:28 AM
To: Zhou, Danny
Cc: dev
performance impact to DPDK.
Please stay tuned.
Alex,
> -Original Message-
> From: Liang, Cunming
> Sent: Wednesday, October 22, 2014 4:53 PM
> To: alex; Zhou, Danny
> Cc: dev at dpdk.org
> Subject: RE: [dpdk-dev] Why do we need iommu=pt?
>
> I thinks it's a g
Thomas,
In terms of the bifurcated driver, it is actually the same thing. Specifically,
the bifurcated
driver PMD in DPDK depends on kernel code(af_packet and 10G/40G NIC) changes.
Once the
kernel patches are upstreamed, the corresponding DPDK PMDs patches will be
submitted to dpdk.org. John
IMHO, if memory protection with IOMMU is needed or not really depends on how
you use
and deploy your DPDK based applications. For Telco network middle boxes, which
adopts
a "close model" solution to achieve extremely high performance, the entire
system including
HW, software in kernel and
Yes, it is doable. The KNI establishes software based request/response queues
between
vNIC device in kernel and PMD in user space. So all ethtool commands will be
interpreted by
KNI driver and forwarded to PMD which really configure NIC registers.
Basically, it is the only option. Or you have
use DPDK to rx/tx packets in your box.
From: Jay Rolette [mailto:role...@infiniteio.com]
Sent: Wednesday, September 24, 2014 2:53 AM
To: Zhou, Danny
Cc: Marc Sune; ; dev-team at bisdn.de
Subject: Re: [dpdk-dev] KNI and memzones
I can't discuss product details openly yet, but I'm happy to have
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jay Rolette
> Sent: Tuesday, September 23, 2014 8:39 PM
> To: Marc Sune
> Cc: ; dev-team at bisdn.de
> Subject: Re: [dpdk-dev] KNI and memzones
>
> *> p.s. Lately someone involved with DPDK said KNI would be
> -Original Message-
> From: John W. Linville [mailto:linville at tuxdriver.com]
> Sent: Tuesday, September 16, 2014 1:48 AM
> To: Neil Horman
> Cc: Zhou, Danny; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] librte_pmd_packet: add PMD for
> AF_PACKET-
> -Original Message-
> From: Neil Horman [mailto:nhorman at tuxdriver.com]
> Sent: Monday, September 15, 2014 11:10 PM
> To: Zhou, Danny
> Cc: John W. Linville; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] librte_pmd_packet: add PMD for
> AF_PACKET-
> -Original Message-
> From: John W. Linville [mailto:linville at tuxdriver.com]
> Sent: Saturday, September 13, 2014 2:54 AM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] librte_pmd_packet: add PMD for
> AF_PACKET-based virtual device
I am concerned about its performance caused by too many memcpy(). Specifically,
on Rx side, kernel NIC driver needs to copy packets to skb, then af_packet
copies packets to AF_PACKET buffer which are mapped to user space, and then
those packets to be copied to DPDK mbuf. In addition, 3 copies
Have you insmod hwmon.ko on your system? Also, you may want to build the DPDK
on your system as KNI kernel module depends on local kernel source code.
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of rong wen
> Sent: Friday, September 05, 2014 7:35 PM
> To:
out.
> >
> > Thanks,
> > Rashmin
> >
> > On Aug 26, 2014 9:15 PM, Stephen Hemminger
> > wrote:
> > The way to handle switch between out of poll mode is to use IRQ coalescing
> > parameters.
> > You want to hold off IRQ until there are a
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Stephen Hemminger
> Sent: Wednesday, August 27, 2014 12:39 AM
> To: Michael Marchetti
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] overcommitting CPUs
>
> On Tue, 26 Aug 2014 16:27:14 +
> "Michael
I have a prototype that works on Niantic to enable NIC rx interrupt and allow
interrupt and polling mode switch according to real traffic load on the rx
queue. It is designed for DPDK power management, and can apply to CPU resource
sharing as well. It only works for non-virtualized environment
The .log below shows your two 10G ports link are up.
Which CPU are you using now and how many processor sockets do you have? If you
used a platform with two processor sockets, make sure to use correct core mask
to specify cores rx/tx packets from 10G NIC connecting to local socket. For you
> >KNI is mainly designed for exception path or control plane packets that
> >need to be pushed
> >to Linux TCP/IP packets in the kernel. You can push all the packets that
> >DPDK PMD received
> >in the user space via KNI to kernel, but majority of them will be dropped
> >for two reasons: 1) skb
>
KNI is mainly designed for exception path or control plane packets that need to
be pushed
to Linux TCP/IP packets in the kernel. You can push all the packets that DPDK
PMD received
in the user space via KNI to kernel, but majority of them will be dropped for
two reasons: 1) skb
allocation/free
packet are directly DMA to mbuf
which needs ixgbe driver to support.
> -Original Message-
> From: John W. Linville [mailto:linville at tuxdriver.com]
> Sent: Tuesday, July 15, 2014 2:25 AM
> To: dev at dpdk.org
> Cc: Thomas Monjalon; Richardson, Bruce; Zhou, Danny
>
20
#define PACKET_FANOUT_FLAG_ROLLOVER 0x1000
> -Original Message-
> From: John W. Linville [mailto:linville at tuxdriver.com]
> Sent: Saturday, July 12, 2014 2:47 AM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] librte_p
nville at tuxdriver.com]
> Sent: Saturday, July 12, 2014 3:32 AM
> To: Zhou, Danny
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] librte_pmd_packet: add PMD for
> AF_PACKET-based virtual devices
>
> I'm not sure that would make any sense -- the AF_PACKET sockets are mapp
Does it support specifying multiple NIC interfaces using command line option
like "--vdev=eth_packet0,iface=..."? Say "iface=eth0,eth1,eth2...", tried but
it doesn't work.
> -Original Message-----
> From: Zhou, Danny
> Sent: Saturday, July 12, 2014 2:01 AM
>
Tried on 3.12, both of them are undefined. Anyway, will comment them out and
see what performance it could achieve.
> -Original Message-
> From: John W. Linville [mailto:linville at tuxdriver.com]
> Sent: Saturday, July 12, 2014 1:41 AM
> To: Zhou, Danny
> Cc: dev at dpd
99 matches
Mail list logo
