[dpdk-dev] ipv4 fragmentation bug?

I am sorry for the late reply. I am not sure anymore about is it a bug I found or the author of rte_ipv4_fragment_packet() realy wanted to constraint the size of mtu writing lines: frag_size = (uint16_t)(mtu_size - sizeof(struct ipv4_hdr)); /* Fragment size should be a multiply of 8. */

[dpdk-dev] [PATCH] maintainers: claim responsability for crypto subtree

> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Thursday, September 15, 2016 8:17 AM > To: De Lara Guarch, Pablo > Cc: dev at dpdk.org > Subject: Re: [PATCH] maintainers: claim responsability for crypto subtree > > 2016-08-30 19:47, Pablo de

[dpdk-dev] [PATCH v2] maintainers: claim responsability for crypto subtree

>From 16.07, I will be the maintainer of the crypto subtree. This will include: - app/test/test_cryptodev* - doc/guides/cryptodevs/ - drivers/crypto/ - examples/l2fwd-crypto/ - examples/ipsec-secgw/ - lib/librte_cryptodev/ Signed-off-by: Pablo de Lara --- Changes in v2: - Included subtree path

[dpdk-dev] [PATCH v3] tools: add crypto device details

From: Eoin Breen Adding the support to bind/unbind crypto devices with dpdk-devbind.py script, as now it is not restricted to network devices anymore. Signed-off-by: Eoin Breen Signed-off-by: Pablo de Lara --- Changes since v2: * Removed network specific parameters from

[dpdk-dev] [PATCH v3 0/2] add aes-sha224-hmac support to Intel QAT driver

> -Original Message- > From: Jain, Deepak K > Sent: Thursday, September 15, 2016 9:27 AM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo; Jain, Deepak K > Subject: [PATCH v3 0/2] add aes-sha224-hmac support to Intel QAT driver > > This patchset adds support of aes-sha224-hmac in

[dpdk-dev] [PATCH v2 0/2] add aes-sha384-hmac support to Intel QAT driver

> -Original Message- > From: Jain, Deepak K > Sent: Monday, September 12, 2016 12:51 PM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo; Jain, Deepak K > Subject: [PATCH v2 0/2] add aes-sha384-hmac support to Intel QAT driver > > This patchset adds support of aes-sha384-hmac in

[dpdk-dev] [PATCH v3 1/2] crypto/qat: add NULL capability to Intel QAT driver

Hi Deepak, > -Original Message- > From: Jain, Deepak K > Sent: Tuesday, September 13, 2016 1:59 AM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo; Jain, Deepak K > Subject: [PATCH v3 1/2] crypto/qat: add NULL capability to Intel QAT driver > > From: Deepak Kumar JAIN > > enabled

[dpdk-dev] [PATCH v10 00/25] Introducing rte_driver/rte_device generalization

Based on master (58efd680d5e) Background: === It includes two different patch-sets floated on ML earlier: * Original patch series is from David Marchand [1], [2]. `- This focused mainly on PCI (PDEV) part `- v7 of this was posted by me [8] in August/2016 * Patch series [4] from Jan

[dpdk-dev] [PATCH v10 01/25] eal: define container macro

From: Jan Viktorin Signed-off-by: Jan Viktorin Signed-off-by: Shreyansh Jain --- lib/librte_eal/common/include/rte_common.h | 21 + 1 file changed, 21 insertions(+) diff --git a/lib/librte_eal/common/include/rte_common.h

[dpdk-dev] [PATCH v10 02/25] eal: remove duplicate function declaration

From: David Marchand rte_eal_dev_init is declared in both eal_private.h and rte_dev.h since its introduction. This function has been exported in ABI, so remove it from eal_private.h Fixes: e57f20e05177 ("eal: make vdev init path generic for both virtual and pci

[dpdk-dev] [PATCH v10 03/25] pci: no need for dynamic tailq init

From: David Marchand These lists can be initialized once and for all at build time. With this, those lists are only manipulated in a common place (and we could even make them private). A nice side effect is that pci drivers can now register in constructors.

[dpdk-dev] [PATCH v10 04/25] eal/pci: replace PCI devinit/devuninit with probe/remove

Probe and Remove are more appropriate names for PCI init and uninint operations. This is a cosmetic change. Only MLX* uses the PCI direct registeration, bypassing PMD_* macro. The calls backs for this too have been updated. VDEV are left out. For them, init/uninit are more appropriate.

[dpdk-dev] [PATCH v10 05/25] crypto: no need for a crypto pmd type

From: David Marchand This information is not used and just adds noise. Signed-off-by: David Marchand Signed-off-by: Shreyansh Jain --- lib/librte_cryptodev/rte_cryptodev.c | 8 +++- lib/librte_cryptodev/rte_cryptodev.h | 2 --

[dpdk-dev] [PATCH v10 06/25] drivers: align PCI driver definitions

From: David Marchand Pure coding style, but it might make it easier later if we want to move fields in rte_cryptodev_driver and eth_driver structures. Signed-off-by: David Marchand Signed-off-by: Shreyansh Jain --- drivers/crypto/qat/rte_qat_cryptodev.c | 2 +-

[dpdk-dev] [PATCH v10 07/25] eal: introduce PCI device init macros

From: David Marchand Introduce a RTE_INIT macro used to mark an init function as a constructor. Current eal macros have been converted to use this (no functional impact). DRIVER_REGISTER_PCI is added as a helper for pci drivers. Suggested-by: Jan Viktorin

[dpdk-dev] [PATCH v10 08/25] driver: init/uninit common wrappers for PCI drivers

From: David Marchand crypto and ethdev drivers aligned to PCI probe/remove. These wrappers are mapped directly to PCI resources. Existing handlers for init/uninit can be easily reused for this. Signed-off-by: David Marchand Signed-off-by: Shreyansh Jain ---

[dpdk-dev] [PATCH v10 09/25] drivers: convert all phy drivers as PCI drivers

From: David Marchand Simplify crypto and ethdev pci drivers init by using newly introduced init macros and helpers. Those drivers then don't need to register as "rte_driver"s anymore. Exceptions: - virtio and mlx* use RTE_INIT directly as they have custom

[dpdk-dev] [PATCH v10 10/25] drivers: remove driver register callbacks for crypto/net

From: David Marchand Now that all pdev are pci drivers, we don't need to register crypto and ethdev drivers through a dedicated channel. Signed-off-by: David Marchand Signed-off-by: Shreyansh Jain --- lib/librte_cryptodev/rte_cryptodev.c | 23

[dpdk-dev] [PATCH v10 11/25] eal/pci: helpers for device name parsing/update

From: David Marchand - Move rte_eth_dev_create_unique_device_name() from ether/rte_ethdev.c to common/include/rte_pci.h as rte_eal_pci_device_name(). Being a common method, can be used across crypto/net PCI PMDs. - Remove crypto specific routine and fallback to

[dpdk-dev] [PATCH v10 12/25] ethdev: do not scan all PCI devices on attach

From: David Marchand No need to scan all devices, we only need to update the device being attached. Signed-off-by: David Marchand Signed-off-by: Shreyansh Jain --- lib/librte_eal/common/eal_common_pci.c | 12 +--- lib/librte_ether/rte_ethdev.c | 3

[dpdk-dev] [PATCH v10 13/25] eal: add hotplug operations for PCI and VDEV

From: David Marchand Hotplug invocations, which deals with devices, should come from the layer that already handles them, i.e. EAL. For both attach and detach operations, 'name' is used to select the bus that will handle the request. Signed-off-by: David Marchand

[dpdk-dev] [PATCH v10 14/25] ethdev: convert to EAL hotplug

From: David Marchand Remove bus logic from ethdev hotplug by using eal for this. Current api is preserved: - the last port that has been created is tracked to return it to the application when attaching, - the internal device name is reused when detaching. We can

[dpdk-dev] [PATCH v10 15/25] ethdev: get rid of device type

From: David Marchand Now that hotplug has been moved to eal, there is no reason to keep the device type in this layer. Signed-off-by: David Marchand Signed-off-by: Shreyansh Jain --- app/test/virtual_pmd.c| 2 +-

[dpdk-dev] [PATCH v10 16/25] eal: extract vdev infra

From: Jan Viktorin Move all PMD_VDEV-specific code into a separate module and header file to not polute the generic code anymore. There is now a list of virtual devices available. The rte_vdev_driver integrates the original rte_driver inside (C inheritance). The

[dpdk-dev] [PATCH v10 17/25] eal: remove PDEV/VDEV unused code

From: Jan Viktorin - Remove checks for VDEV from rte_eal_vdev_(init/uninint) as all devices are inherently virtual here. - PDEVs perform PCI specific inits - rte_eal_dev_init() need not call rte_driver->init(); Signed-off-by: Jan Viktorin [Shreyansh: Reword commit

[dpdk-dev] [PATCH v10 18/25] drivers: convert VDRV to use RTE VDEV Driver

From: Jan Viktorin All PMD_VDEV drivers can now use rte_vdev_driver instead of the rte_driver (which is embedded in the rte_vdev_driver). Signed-off-by: Jan Viktorin Signed-off-by: Shreyansh Jain --- drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 10 ++

[dpdk-dev] [PATCH v10 19/25] eal: remove unused PMD types

From: Jan Viktorin - All devices register themselfs by calling a kind of DRIVER_REGISTER_XXX. The PMD_REGISTER_DRIVER is not used anymore. - PMD_VDEV type is also not being used - can be removed from all VDEVs. Note: PMD_REGISTER_DRIVER usage by PMDINFO tool and its

[dpdk-dev] [PATCH v10 20/25] eal: include dev headers in place of PCI headers

From: Jan Viktorin Further refactoring and generalization of PCI infrastructure will require access to the rte_dev.h contents. Signed-off-by: Jan Viktorin Signed-off-by: Shreyansh Jain --- lib/librte_eal/common/include/rte_pci.h | 1 + 1 file changed, 1 insertion(+)

[dpdk-dev] [PATCH v10 21/25] eal: rename and move RTE PCI Resources

From: Jan Viktorin There is no need to have a custom memory resource representation for each infrastructure (PCI, ...) as it would always have the same members. Signed-off-by: Jan Viktorin Signed-off-by: Shreyansh Jain --- drivers/net/szedata2/rte_eth_szedata2.c | 4

[dpdk-dev] [PATCH v10 22/25] eal/pci: inherit RTE driver in PCI driver

From: Jan Viktorin Remove the 'name' member from rte_pci_driver and move to generic rte_driver. Most of the PMD drivers were initially using DRIVER_REGISTER_PCI(..) as well as assigning a name to eth_driver.pci_drv.name member. In this patch, only the original

[dpdk-dev] [PATCH v10 23/25] eal: register EAL drivers explicitly

From: Jan Viktorin To register both vdev and pci drivers into the list of all rte_driver, we have to call rte_eal_driver_register explicitly. Signed-off-by: Jan Viktorin Signed-off-by: Shreyansh Jain --- lib/librte_eal/common/eal_common_pci.c | 2 ++

[dpdk-dev] [PATCH v10 24/25] eal: introduce generalized RTE device

From: Jan Viktorin Signed-off-by: Jan Viktorin Signed-off-by: Shreyansh Jain --- lib/librte_eal/common/eal_common_dev.c | 13 + lib/librte_eal/common/include/rte_dev.h | 31 +++ 2 files changed, 44 insertions(+) diff --git

[dpdk-dev] [PATCH v10 25/25] eal/pci: create RTE device list and fallback on its members

From: Jan Viktorin Now that rte_device is available, drivers can start using its members (numa, name) as well as link themselves into another rte_device list. As of now no one is using this list, but can be used for moving over all devices (pdev/vdev/Xdev) and perform

[dpdk-dev] [PATCH v9 22/25] eal/pci: inherit rte_driver by rte_pci_driver

On Thursday 08 September 2016 07:55 PM, Ferruh Yigit wrote: > On 9/7/2016 3:08 PM, Shreyansh Jain wrote: >> Remove the 'name' member from rte_pci_driver and move to generic rte_driver. >> >> Most of the PMD drivers were initially using DRIVER_REGISTER_PCI(..) >> as well as assigning a name to

[dpdk-dev] [PATCH v9 08/25] drivers: convert all pdev drivers as pci drivers

Hi David, On Monday 12 September 2016 12:46 PM, David Marchand wrote: > On Wed, Sep 7, 2016 at 4:08 PM, Shreyansh Jain > wrote: >> Simplify crypto and ethdev pci drivers init by using newly introduced >> init macros and helpers. >> Those drivers then don't need to register as "rte_driver"s

[dpdk-dev] [PATCH] Revert "bonding: use existing enslaved device queues"

Ping. Best regards, Ilya Maximets. On 07.09.2016 15:28, Ilya Maximets wrote: > This reverts commit 5b7bb2bda5519b7800f814df64d4e015282140e5. > > It is necessary to reconfigure all queues every time because configuration > can be changed. > > For example, if we're reconfiguring bonding device

[dpdk-dev] [PATCH v3 00/15] Introduce SoC device/driver framework for EAL

Hi David, > -Original Message- > From: Hunt, David [mailto:david.hunt at intel.com] > Sent: Thursday, September 15, 2016 6:26 PM > To: Shreyansh Jain ; dev at dpdk.org > Cc: viktorin at rehivetech.com; Hemant Agrawal > Subject: Re: [dpdk-dev] [PATCH v3 00/15] Introduce SoC device/driver

[dpdk-dev] [PATCH v3 01/15] eal/soc: introduce very essential SoC infra definitions

Hi David, > -Original Message- > From: Hunt, David [mailto:david.hunt at intel.com] > Sent: Thursday, September 15, 2016 6:29 PM > To: Shreyansh Jain ; dev at dpdk.org > Cc: viktorin at rehivetech.com; Hemant Agrawal > Subject: Re: [dpdk-dev] [PATCH v3 01/15] eal/soc: introduce very

[dpdk-dev] Possible bug in mlx5_tx_burst_mpw?

On Wed, Sep 14, 2016 at 09:33:18PM +0200, Luke Gorrie wrote: > Hi Adrien, > > On 14 September 2016 at 16:30, Adrien Mazarguil 6wind.com> > wrote: > > > Your interpretation is correct (this is intentional and not a bug). > > > > Thanks very much for clarifying. > > This is interesting to me

[dpdk-dev] [PATCH v3 12/15] ether: extract function eth_dev_get_intr_handle

On 09/15/2016 05:05 PM, Thomas Monjalon wrote: > 2016-09-15 14:02, Hunt, David: >> On 9/9/2016 9:43 AM, Shreyansh Jain wrote: >>> +static inline >>> +struct rte_intr_handle *eth_dev_get_intr_handle(struct rte_eth_dev *dev) >>> +{ >>> + if (dev->pci_dev) { >>> + return

[dpdk-dev] [PATCH v3 02/15] eal/soc: add rte_eal_soc_register/unregister logic

On 09/15/2016 05:09 PM, Thomas Monjalon wrote: > 2016-09-15 15:09, Jan Viktorin: >> On Thu, 15 Sep 2016 14:00:25 +0100 >> "Hunt, David" wrote: >> new file mode 100644 index 000..56135ed --- /dev/null +++ b/lib/librte_eal/common/eal_common_soc.c @@ -0,0 +1,56 @@

[dpdk-dev] [PATCH 3/3] drivers/net:build support for new tap device driver

On 09/15/2016 05:10 PM, Keith Wiles wrote: > Signed-off-by: Keith Wiles > --- > config/common_linuxapp | 3 +++ > drivers/net/Makefile | 1 + > mk/rte.app.mk | 1 + > 3 files changed, 5 insertions(+) > > diff --git a/config/common_linuxapp b/config/common_linuxapp > index

[dpdk-dev] [PATCH] log: do not drop debug logs at compile time

Today, all logs whose level is lower than INFO are dropped at compile-time. This prevents from enabling debug logs at runtime using --log-level=8. The rationale was to remove debug logs from the data path at compile-time, avoiding a test at run-time. This patch changes the behavior of RTE_LOG()

[dpdk-dev] [PATCH] nfp: using random mac address if not a configured mac

Thank you for the feedback. I'll send the fixed patched today. On Tue, Sep 13, 2016 at 8:30 PM, Thomas Monjalon wrote: > 2016-09-13 18:10, Ferruh Yigit: > > Hi Alejandro, > > > > On 8/16/2016 4:15 PM, Alejandro Lucero wrote: > > > Signed-off-by: Alejandro Lucero > > > --- > > > > There are

[dpdk-dev] Possible bug in mlx5_tx_burst_mpw?

Hi Adrien, Thanks for taking the time to write a detailed reply. This indeed sounds reasonable to me. Users will need to take these special-cases into account when predicting performance on their own anticipated workloads, which is a bit tricky, but then that is life when dealing with complex new

[dpdk-dev] [PATCH] remove unused ring includes

2016-08-31 10:34, Amine Kherbouche: > This patch removes all unused headers. > > Signed-off-by: Amine Kherbouche [...] > --- a/examples/performance-thread/common/lthread_int.h > +++ b/examples/performance-thread/common/lthread_int.h > @@ -72,7 +72,6 @@ > #include > #include > #include >

[dpdk-dev] [PATCH v2] maintainers: claim responsability for crypto subtree

2016-09-16 00:25, Pablo de Lara: > From 16.07, I will be the maintainer of the crypto subtree. > > This will include: > - app/test/test_cryptodev* > - doc/guides/cryptodevs/ > - drivers/crypto/ > - examples/l2fwd-crypto/ > - examples/ipsec-secgw/ > - lib/librte_cryptodev/ > > Signed-off-by:

[dpdk-dev] [PATCH v2 2/2] mempool:pktmbuf pool default fallback for mempool ops error

Hi Hemant, On 15/9/2016 6:13 PM, Hemant Agrawal wrote: > In the rte_pktmbuf_pool_create, if the default external mempool is > not available, the implementation can default to "ring_mp_mc", which > is an software implementation. > > Signed-off-by: Hemant Agrawal > --- >

[dpdk-dev] [PATCH v4 0/2] add NULL crypto support in Intel QAT driver

This patchset adds support of NULL crypto in Intel(R) QuickAssist Technology driver. This patchset depends on following patchset: "crypto/qat: add aes-sha384-hmac capability to Intel QAT driver" (http://dpdk.org/dev/patchwork/patch/15778/) Deepak Kumar JAIN (2): crypto/qat: add NULL

[dpdk-dev] [PATCH v4 1/2] crypto/qat: add NULL capability to Intel QAT driver

From: Deepak Kumar JAIN enabled NULL crypto for Intel(R) QuickAssist Technology Signed-off-by: Deepak Kumar Jain Acked-by: Fiona Trahe --- doc/guides/cryptodevs/qat.rst| 3 +- doc/guides/rel_notes/release_16_11.rst | 1 +

[dpdk-dev] [PATCH v4 2/2] app/test: add test cases for NULL for Intel QAT driver

From: Deepak Kumar JAIN Added NULL algorithm to test file for Intel(R) QuickAssist Technology Driver Signed-off-by: Deepak Kumar Jain Acked-by: Fiona Trahe --- app/test/test_cryptodev.c | 10 ++ 1 file changed, 10 insertions(+) diff --git

[dpdk-dev] [Snort-devel] 答复: A mutithreaded DPDK DAQ Module for Snort 3.0

Nacht: what about to submit the dpdk patch to DPDK.org? It is a good piece of work, it will make sense to avoid the extra patch whenever possible. We will review this patch by the mailing list. From: Nacht Z [mailto:nac...@outlook.com] Sent: Friday, September 16, 2016 10:56 AM To:

[dpdk-dev] [PATCH v2 1/2] eal/mempool: introduce check for external mempool availability

Hi Hemant, On 15/9/2016 6:13 PM, Hemant Agrawal wrote: > External offloaded mempool may not be available always. This check enables > run time verification of the presence of external mempool before the > mempool ops are installed. > > An application built with a specific external mempool may

[dpdk-dev] [PATCH v2 1/2] eal/mempool: introduce check for external mempool availability

HI David, > -Original Message- > From: Hunt, David [mailto:david.hunt at intel.com] > Sent: Friday, September 16, 2016 2:44 PM > To: Hemant Agrawal ; olivier.matz at 6wind.com > Cc: dev at dpdk.org; jerin.jacob at caviumnetworks.com > Subject: Re: [PATCH v2 1/2] eal/mempool: introduce

[dpdk-dev] [PATCH v2 2/2] mempool:pktmbuf pool default fallback for mempool ops error

Hi David, > -Original Message- > From: Hunt, David [mailto:david.hunt at intel.com] > Sent: Friday, September 16, 2016 2:00 PM > To: Hemant Agrawal ; olivier.matz at 6wind.com > Cc: dev at dpdk.org; jerin.jacob at caviumnetworks.com > Subject: Re: [PATCH v2 2/2] mempool:pktmbuf pool

[dpdk-dev] [PATCH] drivers: advertise kmod dependencies in pmdinfo

Hi Oliver, > -Original Message- > From: Olivier Matz [mailto:olivier.matz at 6wind.com] > Sent: Thursday, September 15, 2016 3:23 PM > To: dev at dpdk.org; nhorman at tuxdriver.com > Cc: thomas.monjalon at 6wind.com; vido at cesnet.cz; Trahe, Fiona > ; stephen at networkplumber.org >

[dpdk-dev] [PATCH] drivers: make driver names consistent

2016-08-24 22:37, Mcnamara, John: > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara > > > > ... > > > > -$RTE_TARGET/app/testpmd -c '0xf' -n 4 --vdev > > 'eth_pcap0,rx_pcap=/path/to/ file_rx.pcap,tx_pcap=/path/to/file_tx.pcap' -- > > --port-topology=chained > > +

[dpdk-dev] [PATCH] crypto/null: fix key size increment value

This patch fixes the values of increment in key size. Fixes: 94b0ad8e0a ("null_crypto_pmd: PMD to support null crypto operations") Signed-off-by: Deepak Kumar Jain --- drivers/crypto/null/null_crypto_pmd_ops.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[dpdk-dev] [PATCH v3 2/3] net/ixgbe: add functions for VF management

Add new functions to configure and manage VF's on an Intel 82559 NIC. add ixgbe_vf_ping function. add ixgbe_set_vf_vlan_anti_spoof function. add ixgbe_set_vf_mac_anti_spoof function. Signed-off-by: azelezniak add ixgbe_set_vf_vlan_insert function. add ixgbe_set_tx_loopback function. add

[dpdk-dev] [PATCH v3 1/3] librte_ether: add API's for VF management

Add new API functions to configure and manage VF's on a NIC. add rte_eth_dev_vf_ping function. add rte_eth_dev_set_vf_vlan_anti_spoof function. add rte_eth_dev_set_vf_mac_anti_spoof function. add rte_eth_dev_set_vf_vlan_strip function. Signed-off-by: azelezniak add

[dpdk-dev] [PATCH v3 3/3] app/test_pmd: add tests for new API's

add test for vf vlan anti spoof add test for vf mac anti spoof add test for vf ping add test for vf vlan strip add test for vf vlan insert add test for tx loopback add test for all queues drop enable bit add test for vf split drop enable bit add test for vf mac address add new API's to the testpmd

[dpdk-dev] [PATCH v3 0/3] add API's for VF management

This patchset contains new DPDK API's requested by AT for use with the Virtual Function Daemon (VFD). The need to configure and manage VF's on a NIC has grown to the point where AT have devloped a DPDK based tool, VFD, to do this. This patch set adds API extensions to DPDK VF configuration.

[dpdk-dev] [PATCH v2] nfp: using random MAC address if not configured

Signed-off-by: Alejandro Lucero --- drivers/net/nfp/nfp_net.c | 28 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/drivers/net/nfp/nfp_net.c b/drivers/net/nfp/nfp_net.c index 82e3e4e..1948a12 100644 --- a/drivers/net/nfp/nfp_net.c +++

[dpdk-dev] [PATCH v2] nfp: fixing bug when copying MAC address

Fixes: defb9a5dd156 ("nfp: introduce driver initialization") Signed-off-by: Alejandro Lucero --- drivers/net/nfp/nfp_net.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/nfp/nfp_net.c b/drivers/net/nfp/nfp_net.c index 1948a12..d79f0a1 100644 ---

[dpdk-dev] [PATCH v2] nfp: unregister interrupt callback when closing

With an app using hotplug feature, when a device is unplugged without unregistering makes the interrupt handling unstable. Fixes: 6c53f87b3497 ("nfp: add link status interrupt") Signed-off-by: Alejandro Lucero --- drivers/net/nfp/nfp_net.c | 5 + 1 file changed, 5 insertions(+) diff --git

[dpdk-dev] [PATCH v3 1/2] eal/mempool: check for external mempool support

External offloaded mempool may not be available always. This check enables run time verification of the presence of external mempool before the mempool ops are installed. An application built with a specific external mempool may work fine on host. But, may not work on VM, specificaly if non-hw

[dpdk-dev] [PATCH v3 2/2] mempool: pktmbuf pool default fallback for mempool ops error

In the rte_pktmbuf_pool_create, if the default external mempool is not available, the implementation can default to "ring_mp_mc", which is an software implementation. Signed-off-by: Hemant Agrawal --- Changes in V3: * adding warning message to say that falling back to default sw pool ---

[dpdk-dev] [PATCH v2] net/kni: add KNI PMD

Add KNI PMD which wraps librte_kni for ease of use. KNI PMD can be used as any regular PMD to send / receive packets to the Linux networking stack. Signed-off-by: Ferruh Yigit --- v2: * updated driver name eth_kni -> net_kni --- config/common_base | 1 +

[dpdk-dev] [PATCH v3 04/15] eal: introduce --no-soc option

Hello Shreyansh, there was an objection to reverse this option from negative to positive semantics: http://dpdk.org/ml/archives/dev/2016-May/038953.html As SoC infrastructure would to be experimental for some time, I think it is a good idea to disable it as default. Regards Jan On Fri, 9 Sep

[dpdk-dev] [PATCH v10 02/25] eal: remove duplicate function declaration

On Fri, 16 Sep 2016 09:59:37 +0530 Shreyansh Jain wrote: > From: David Marchand > > rte_eal_dev_init is declared in both eal_private.h and rte_dev.h since its > introduction. > This function has been exported in ABI, so remove it from eal_private.h > > Fixes: e57f20e05177 ("eal: make vdev

[dpdk-dev] [PATCH v10 05/25] crypto: no need for a crypto pmd type

On Fri, 16 Sep 2016 09:59:40 +0530 Shreyansh Jain wrote: > From: David Marchand > > This information is not used and just adds noise. > > Signed-off-by: David Marchand > Signed-off-by: Shreyansh Jain Reviewed-by: Jan Viktorin

[dpdk-dev] [PATCH v3 04/15] eal: introduce --no-soc option

Hello Jan, On Friday 16 September 2016 05:06 PM, Jan Viktorin wrote: > Hello Shreyansh, > > there was an objection to reverse this option from negative > to positive semantics: > > http://dpdk.org/ml/archives/dev/2016-May/038953.html Ok. I wasn't aware of this. Sounds reasonable as SoC is

[dpdk-dev] [PATCH] app/test: improve error message in crypto test code

From: Fiona Trahe Improve error message if crypto PMD build is not enabled in config file Signed-off-by: Fiona Trahe --- app/test/test_cryptodev.c | 37 + app/test/test_cryptodev_perf.c | 23 +++ 2 files

[dpdk-dev] [PATCH v3 06/15] eal/soc: implement probing of drivers

On Fri, 9 Sep 2016 14:13:50 +0530 Shreyansh Jain wrote: > Each SoC PMD registers a set of callback for scanning its own bus/infra and > matching devices to drivers when probe is called. > This patch introduces the infra for calls to SoC scan on rte_eal_soc_init() > and match on

[dpdk-dev] [PATCH 01/17] qede/base: update base driver

Hi Rasesh, On 8/27/2016 7:26 AM, Rasesh Mody wrote: > This patch updates the base driver and incorporates neccessary changes > required to bring in the new firmware 8.10.9.0. > > In addition, it would allow driver to add new functionalities that might > be needed in future. > > Signed-off-by:

[dpdk-dev] [PATCH] eal/linux: use more restrictive perms in hugedir

2016-08-10 16:52, Robin Jarry: > There is no need for the page files to be readable (and executable) by > other users. This can be exploited by non-privileged users to access the > working memory of a DPDK app. > > Open the files with 0600. > > Signed-off-by: Robin Jarry Applied, thanks I

[dpdk-dev] [PATCH v2 0/2] lpm6: speed improvement on delete rule

On 08/25/2016 00:59, Nikita Kozlov wrote: > This serie of pathes focus on improving the speed of deleting rules in lpm6. > > It also contains some other improvement like having a dynamic number of > rules in lpm6 and increasing the lpm6 nexthop size to 16bit for matching > the nexthop size in

[dpdk-dev] [PATCH] pci: fix one device probing

2016-08-04 14:50, Igor Ryzhov: > The rte_eal_pci_probe_one function could return false positive result if > no driver is found for the device. > > Signed-off-by: Igor Ryzhov [...] > --- a/lib/librte_eal/common/eal_common_pci.c > +++ b/lib/librte_eal/common/eal_common_pci.c > @@ -344,7 +344,7 @@

[dpdk-dev] [PATCH v3] eal: restrict cores detection

2016-09-01 01:31, Jianfeng Tan: > This patch uses pthread_getaffinity_np() to narrow down detected > cores before parsing coremask (-c), corelist (-l), and coremap > (--lcores). > > The purpose of this patch is to leave out these core related options > when DPDK applications are deployed under

[dpdk-dev] [PATCH v3] eal: restrict cores detection

2016-09-02 17:53, Bruce Richardson: > On Thu, Sep 01, 2016 at 01:31:47AM +, Jianfeng Tan wrote: It would help the discussion to have a problem statement here. > > This patch uses pthread_getaffinity_np() to narrow down detected > > cores before parsing coremask (-c), corelist (-l), and

[dpdk-dev] [PATCH v3 0/3] add API's for VF management

This patchset contains new DPDK API's requested by AT for use with the Virtual Function Daemon (VFD). The need to configure and manage VF's on a NIC has grown to the point where AT have devloped a DPDK based tool, VFD, to do this. This patch set adds API extensions to DPDK VF configuration.

[dpdk-dev] [PATCH v3 1/3] librte_ether: add API's for VF management

Add new API functions to configure and manage VF's on a NIC. add rte_eth_dev_vf_ping function. add rte_eth_dev_set_vf_vlan_anti_spoof function. add rte_eth_dev_set_vf_mac_anti_spoof function. add rte_eth_dev_set_vf_vlan_strip function. Signed-off-by: azelezniak add

[dpdk-dev] [PATCH v3 2/3] net/ixgbe: add functions for VF management

Add new functions to configure and manage VF's on an Intel 82559 NIC. add ixgbe_vf_ping function. add ixgbe_set_vf_vlan_anti_spoof function. add ixgbe_set_vf_mac_anti_spoof function. Signed-off-by: azelezniak add ixgbe_set_vf_vlan_insert function. add ixgbe_set_tx_loopback function. add

[dpdk-dev] [PATCH v3 3/3] app/test_pmd: add tests for new API's

add test for vf vlan anti spoof add test for vf mac anti spoof add test for vf ping add test for vf vlan strip add test for vf vlan insert add test for tx loopback add test for all queues drop enable bit add test for vf split drop enable bit add test for vf mac address add new API's to the testpmd

[dpdk-dev] [PATCH] mempool: fix corruption due to invalid handler

CC stable at dpdk.org 2016-09-08 10:29, Weiliang Luo: > When using rte_mempool_create(), the mempool handler is selected > depending on the flags given by the user: > - multi-consumer / multi-producer > - multi-consumer / single-producer > - single-consumer / multi-producer > -

[dpdk-dev] [PATCH] drivers: advertise kmod dependencies in pmdinfo

On Thu, Sep 15, 2016 at 4:22 PM, Olivier Matz wrote: > Add a new macro DRIVER_REGISTER_KMOD_DEP() that allows a driver to > declare the list of kernel modules required to run properly. > > Today, most PCI drivers require uio/vfio. > > Signed-off-by: Olivier Matz Thanks Olivier, this looks good

[dpdk-dev] [PATCH v10 00/25] Introducing rte_driver/rte_device generalization

Sorry dropped the ml. On Fri, Sep 16, 2016 at 4:21 PM, David Marchand wrote: > Commenting in the cover letter because these are details and it is > easier to track down what is missing before push for Thomas. > > >> driver: init/uninit common wrappers for PCI drivers > > In this patch

[dpdk-dev] [PATCH v3 0/2] Add 3DES support to Quickassist PMD

resend of v3 patchset as first send didn't get to patchwork, just to mailing list. Some preparatory cleanup done in QAT PMD for adding 3DES 3DES support added to QuickAssist PMD With CTR and CBC mode. Both cipher-only and chained with HMAC_SHAx 3DES test code is included in the libcrypto

[dpdk-dev] [PATCH v3 1/2] crypto/qat: code cleanup

Cleanup of unused code. Rename and simplify a badly named struct element, was aes, but used for all types of ciphers Print correct error msg (Unsupported rather than Undefined) for all ciphers not supported by qat PMD. Signed-off-by: Fiona Trahe --- drivers/crypto/qat/qat_adf/icp_qat_hw.h

[dpdk-dev] [PATCH v3 2/2] crypto/qat: adding support for 3DES cipher algorithm

3DES support added to QuickAssist PMD With CTR and CBC mode. Both cipher-only and chained with HMAC_SHAx This patch depends on following patch : crypto/qat: enable support of Kasumi F8 in QAT cryptodev http://dpdk.org/dev/patchwork/patch/15813/ Signed-off-by: Fiona Trahe ---

[dpdk-dev] [PATCH 3/3] drivers/net:build support for new tap device driver

Regards, Keith > On Sep 16, 2016, at 2:36 AM, Panu Matilainen wrote: > > On 09/15/2016 05:10 PM, Keith Wiles wrote: >> Signed-off-by: Keith Wiles >> --- >> config/common_linuxapp | 3 +++ >> drivers/net/Makefile | 1 + >> mk/rte.app.mk | 1 + >> 3 files changed, 5 insertions(+) >> >>

[dpdk-dev] [PATCH] app/test: improve error message in crypto test code

Resending patch as first send got to mailing list but didn't get to pachwork Improve error message if crypto PMD build is not enabled in config file Signed-off-by: Fiona Trahe --- app/test/test_cryptodev.c | 37 + app/test/test_cryptodev_perf.c | 23

[dpdk-dev] [PATCH v1]:rte_timer:timer lag issue correction

Thanks Reshma for the comments, the issue is a day one bug. I will correct the fixes line and submit v2 of the patch. -Original Message- From: Pattan, Reshma [mailto:reshma.pat...@intel.com] Sent: Thursday, September 15, 2016 5:28 AM To: Karmarkar Suyash Cc: dev at dpdk.org;

[dpdk-dev] [PATCH] app/test: improve error message in crypto test code

> -Original Message- > From: Trahe, Fiona > Sent: Friday, September 16, 2016 3:37 PM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo ; Trahe, Fiona > > Subject: [PATCH] app/test: improve error message in crypto test code > > Resending patch as first send got to mailing list but

[dpdk-dev] [PATCH] crypto/null: fix key size increment value

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Deepak Kumar Jain > Sent: Friday, September 16, 2016 11:50 AM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo ; Jain, Deepak K > > Subject: [dpdk-dev] [PATCH] crypto/null: fix key size increment value > >

[dpdk-dev] [PATCH v2]:rte_timer:timer lag issue correction

For Periodic timers ,if the lag gets introduced, the current code added additional delay when the next peridoc timer was initialized by not taking into account the delay added, with this fix the code would start the next occurrence of timer keeping in account the lag added.Corrected the

[dpdk-dev] [PATCH v2]:rte_timer:timer lag issue correction

For Periodic timers ,if the lag gets introduced, the current code added additional delay when the next peridoc timer was initialized by not taking into account the delay added, with this fix the code would start the next occurrence of timer keeping in account the lag added.Corrected the

[dpdk-dev] [PATCH] kni: fix build with kernel < v3.0

Compile error: CC [M] .../build/lib/librte_eal/linuxapp/kni/igb_main.o .../build/lib/librte_eal/linuxapp/kni/igb_main.c: In function ?igb_check_swap_media?: .../build/lib/librte_eal/linuxapp/kni/igb_main.c:1556:7: error: variable ?link? set but not used [-Werror=unused-but-set-variable] bool

[dpdk-dev] [PATCH v2] drivers/net:new PMD using tun/tap host interface

The rte_eth_tap.c PMD creates a device using TUN/TAP interfaces on the local host. The PMD allows for DPDK and the host to communicate using a raw device interface on the host and in the DPDK application. The device created is a Tap device with a L2 packet header. v2 - merge all of the patches

[dpdk-dev] [PATCH v2 00/19] KNI checkpatch cleanup

KNI checkpatch cleanup, mostly non-functional but cosmetic modifications. Only functional change is related logging, switched to kernel dynamic logging and compile time KNI debug options removed, some log message levels updated. v2: keep variable externs in .c file Ferruh Yigit (19): kni: move

  1   2   >