[dpdk-dev] [PATCH v6 0/7] IPsec Sec GW new features

2021-11-01 Thread Radu Nicolau
Update the IPsec sample app with new features and updates: - telemetry support - add reset callback - stats screen configurable as a command line parameter - UDP encapsulation support for inline crypto - ESN with configurable start value Radu Nicolau (7): examples/ipsec-secgw: add stats interval

[dpdk-dev] [PATCH v6 0/7] Enhancements for PMD power management

2021-07-05 Thread Anatoly Burakov
This patchset introduces several changes related to PMD power management: - Changed monitoring intrinsics to use callbacks as a comparison function, based on previous patchset [1] but incorporating feedback [2] - this hopefully will make it possible to add support for .get_monitor_addr in virt

[dpdk-dev] [PATCH v6 0/7] vhost: Fix and improve NUMA reallocation

2021-06-18 Thread Maxime Coquelin
This patch series first fixes missing reallocations of some Virtqueue and device metadata. Then, it improves the numa_realloc function by using rte_realloc_socket API that takes care of the memcpy & freeing. The VQs NUMA IDs are also saved in the VQ metadata and used for every allocations so that

Re: [dpdk-dev] [PATCH v6 0/7] BBDEV test updates

2020-10-28 Thread Akhil Goyal
> Subject: [PATCH v6 0/7] BBDEV test updates > > v6: minor refactory suggested by Tom Rix, > v5: correcting typos again. Quite worrisome spelling disorder. > v4: rebased on main latest > v3: apologize again for typo and not double checking with check-git-log > v2: typos missed in commit messages >

[dpdk-dev] [PATCH v6 0/7] BBDEV test updates

2020-10-26 Thread Nicolas Chautru
v6: minor refactory suggested by Tom Rix, v5: correcting typos again. Quite worrisome spelling disorder. v4: rebased on main latest v3: apologize again for typo and not double checking with check-git-log v2: typos missed in commit messages Serie updating and extending the app running the bbdev-test

Re: [dpdk-dev] [PATCH v6 0/7] app/proc-info: enhancements

2020-10-19 Thread Thomas Monjalon
24/09/2020 07:34, Stephen Hemminger: > The current proc-info command is useful for diagnosing issues > with external DPDK applications, but the display is limited > and somewhat ugly. This patchset adds some enhancements which > show more info and suppress unnecessary stuff. > > Hemant Agrawal (1)

[dpdk-dev] [PATCH v6 0/7] app/proc-info: enhancements

2020-09-23 Thread Stephen Hemminger
The current proc-info command is useful for diagnosing issues with external DPDK applications, but the display is limited and somewhat ugly. This patchset adds some enhancements which show more info and suppress unnecessary stuff. A before/after example: # dpdk-proc-info -w 03:00.0 -- --show-por

Re: [dpdk-dev] [PATCH v6 0/7]

2020-09-23 Thread David Marchand
On Sun, Sep 20, 2020 at 1:49 PM Feifei Wang wrote: > > Several bugs in ring unit tests were identified and fixed. > > Added data validation on objects after enqueue/dequeue operations for > data integration check. > > Unit tests were enhanced by checking return value of enqueue/dequeue > operation

Re: [dpdk-dev] [PATCH v6 0/7]

2020-09-20 Thread Ananyev, Konstantin
> Several bugs in ring unit tests were identified and fixed. > > Added data validation on objects after enqueue/dequeue operations for > data integration check. > > Unit tests were enhanced by checking return value of enqueue/dequeue > operations and validating data integrity of objects. > > v

[dpdk-dev] [PATCH v6 0/7]

2020-09-20 Thread Feifei Wang
Several bugs in ring unit tests were identified and fixed. Added data validation on objects after enqueue/dequeue operations for data integration check. Unit tests were enhanced by checking return value of enqueue/dequeue operations and validating data integrity of objects. v2: 1. add check to v

Re: [dpdk-dev] [PATCH v6 0/7] add Intel DCF PMD support

2020-03-27 Thread Ye Xiaolong
On 03/27, Haiyue Wang wrote: >A DCF (Device Config Function) based approach is proposed where a device >bound to the device's VF0 can act as a sole controlling entity to exercise >advance functionality (such as switch, ACL) for rest of the VFs. > >The DCF works as a standalone PMD to support this f

[dpdk-dev] [PATCH v6 0/7] add Intel DCF PMD support

2020-03-26 Thread Haiyue Wang
A DCF (Device Config Function) based approach is proposed where a device bound to the device's VF0 can act as a sole controlling entity to exercise advance functionality (such as switch, ACL) for rest of the VFs. The DCF works as a standalone PMD to support this function, which shares the ice PMD

[dpdk-dev] [PATCH v6 0/7] ethdev: add new Rx offload flags

2019-10-01 Thread pbhagavatula
From: Pavan Nikhilesh Add new Rx offload flags `DEV_RX_OFFLOAD_RSS_HASH` and `DEV_RX_OFFLOAD_FLOW_MARK`. These flags can be used to enable/disable PMD writes to rte_mbuf fields `hash.rss` and `hash.fdir.hi` and also `ol_flags:PKT_RX_RSS` and `ol_flags:PKT_RX_FDIR`. Add new packet type set functi

Re: [dpdk-dev] [PATCH v6 0/7] use WFE for aarch64

2019-09-26 Thread Gavin Hu (Arm Technology China)
> > There is checkpatch failure. > ### eal: add the APIs to wait until equal > > WARNING:LONG_LINE_COMMENT: line over 80 characters > #123: FILE: lib/librte_eal/common/include/generic/rte_pause.h:29: > + * Wait for *addr to be updated with a 16-bit expected value, with a > relaxed memory > > Wit

Re: [dpdk-dev] [PATCH v6 0/7] use WFE for aarch64

2019-09-26 Thread Jerin Jacob
On Sat, Sep 14, 2019 at 8:30 PM Gavin Hu wrote: > > V6: > - squash the RTE_ARM_USE_WFE configuration entry patch into the new API patch > - move the new configuration to the end of EAL > - add doxygen comments to reflect the relaxed and acquire semantics > - correct the meson configuration > V5: >

[dpdk-dev] [PATCH v6 0/7] use WFE for aarch64

2019-09-14 Thread Gavin Hu
V6: - squash the RTE_ARM_USE_WFE configuration entry patch into the new API patch - move the new configuration to the end of EAL - add doxygen comments to reflect the relaxed and acquire semantics - correct the meson configuration V5: - add doxygen comments for the new APIs - spinlock early exit w

Re: [dpdk-dev] [PATCH v6 0/7] bbdev: adding support in BBDEV for 5GNR FEC

2019-07-05 Thread Akhil Goyal
> > 03/07/2019 20:31, Chautru, Nicolas: > > Thomas wrote: > > >> Nicolas Chautru (7): > > >> bbdev: renaming non-generic LTE specific structure > > >> bbdev: extension of BBDEV API for 5G FEC > > >> docs/guides: updating bbdev API for 5GNR operations > > >> baseband/turbo_sw: extension

Re: [dpdk-dev] [PATCH v6 0/7] bbdev: adding support in BBDEV for 5GNR FEC

2019-07-03 Thread Thomas Monjalon
03/07/2019 20:31, Chautru, Nicolas: > Thomas wrote: > >> Nicolas Chautru (7): > >> bbdev: renaming non-generic LTE specific structure > >> bbdev: extension of BBDEV API for 5G FEC > >> docs/guides: updating bbdev API for 5GNR operations > >> baseband/turbo_sw: extension of turbosw PMD for 5

Re: [dpdk-dev] [PATCH v6 0/7] bbdev: adding support in BBDEV for 5GNR FEC

2019-07-03 Thread Chautru, Nicolas
Thomas wrote: >> Nicolas Chautru (7): >> bbdev: renaming non-generic LTE specific structure >> bbdev: extension of BBDEV API for 5G FEC >> docs/guides: updating bbdev API for 5GNR operations >> baseband/turbo_sw: extension of turbosw PMD for 5G >> docs/guides: updating building steps for

Re: [dpdk-dev] [PATCH v6 0/7] bbdev: adding support in BBDEV for 5GNR FEC

2019-07-03 Thread Thomas Monjalon
Hi, > Nicolas Chautru (7): > bbdev: renaming non-generic LTE specific structure > bbdev: extension of BBDEV API for 5G FEC > docs/guides: updating bbdev API for 5GNR operations > baseband/turbo_sw: extension of turbosw PMD for 5G > docs/guides: updating building steps for BBDEV PMD > t

[dpdk-dev] [PATCH v6 0/7] bbdev: adding support in BBDEV for 5GNR FEC

2019-07-03 Thread Nicolas Chautru
v6 update: minor fix for compilation issue reported on CI v5 update: rebase and squashing release note update with related change. v4 update: cosmetic changes reported by ci/checkpatch This set enables specifically bbdev to support 5GNR operations (previously only LTE specific) and to add the re

Re: [dpdk-dev] [PATCH v6 0/7] replace attach/detach functions

2018-10-22 Thread Thomas Monjalon
22/10/2018 17:11, Iremonger, Bernard: > Hi Thomas, > > The following patch fails to apply to the latest master branch, a rebase may > be needed. > > v6-5-7-ethdev-remove-deprecated-attach-detach-functions.patch > > The remaining two patches of this patch set then fail to apply. I think it is b

Re: [dpdk-dev] [PATCH v6 0/7] replace attach/detach functions

2018-10-22 Thread Iremonger, Bernard
Hi Thomas, > -Original Message- > From: Thomas Monjalon [mailto:tho...@monjalon.net] > Sent: Monday, October 22, 2018 1:31 PM > To: dev@dpdk.org > Cc: gaetan.ri...@6wind.com; ophi...@mellanox.com; > wis...@mellanox.com; Yigit, Ferruh ; > arybche...@solarflare.com; Iremonger, Bernard > > S

[dpdk-dev] [PATCH v6 0/7] replace attach/detach functions

2018-10-22 Thread Thomas Monjalon
The functions for EAL attach/detach had already some replacements, so they are removed. The functions for ethdev attach/detach are removed and replaced thanks to a new ethdev iterator working with devargs. rte_eth_dev_attach(devargs, &port_id) is replaced by: rte_dev_probe(devargs); RT

[dpdk-dev] [PATCH v6 0/7] hotplug failure handle mechanism

2018-07-08 Thread Jeff Guo
As we know, hot plug is an importance feature, either use for the datacenter device’s fail-safe, or use for SRIOV Live Migration in SDN/NFV. It could bring the higher flexibility and continuality to the networking services in multiple use cases in industry. So let we see, dpdk as an importance netw

[dpdk-dev] [PATCH v6 0/7] hotplug failure handle mechanism

2018-07-08 Thread Jeff Guo
As we know, hot plug is an importance feature, either use for the datacenter device’s fail-safe, or use for SRIOV Live Migration in SDN/NFV. It could bring the higher flexibility and continuality to the networking services in multiple use cases in industry. So let we see, dpdk as an importance netw

[dpdk-dev] [PATCH v6 0/7] *** fix the cross compile errors ***

2018-06-14 Thread Gavin Hu
Pre-V5 version of this patch set(two patches) was aimed to fix the Makefile based cross compiling issue and add a guiding doc. This V6 patch set included the fixes for meson cross compiling. Gavin Hu (5): devtools: fix the Exec format error build: fix the meson build warning devtools: fix t

Re: [dpdk-dev] [PATCH v6 0/7] Introduce DPAA2 Command Interface raw driver

2018-05-08 Thread Thomas Monjalon
05/05/2018 20:44, Shreyansh Jain: > From: Nipun Gupta > > > > This patch set introduces DPAA2 based Command Interface > > device driver. > > > > This driver is provides communication between the GPP and > > AIOP Firmware. > > Series-Acked-by: Shreyansh Jain Applied, thanks

Re: [dpdk-dev] [PATCH v6 0/7] Introduce DPAA2 Command Interface raw driver

2018-05-05 Thread Shreyansh Jain
> -Original Message- > From: Nipun Gupta > Sent: Friday, May 4, 2018 3:41 PM > To: tho...@monjalon.net; Hemant Agrawal ; > Shreyansh Jain > Cc: dev@dpdk.org; Nipun Gupta > Subject: [PATCH v6 0/7] Introduce DPAA2 Command Interface raw driver > > This patch set introduces DPAA2 based Comma

[dpdk-dev] [PATCH v6 0/7] Introduce DPAA2 Command Interface raw driver

2018-05-04 Thread Nipun Gupta
This patch set introduces DPAA2 based Command Interface device driver. This driver is provides communication between the GPP and AIOP Firmware. This patchset is based on top of: https://dpdk.org/dev/patchwork/patch/39246/ Patches 1-3: Makes necessary changes and fixes in the DPAA2 bus and me

[dpdk-dev] [PATCH v6 0/7] switching device representation

2018-03-28 Thread Declan Doherty
This patchset follows on from the port rerpesentor patchsets and the community discussion that resulted. It outlines the model for representing and controlling switching capable devices in a new programmer's guide entry based upon the excellent summary by Adrien Mazarguil in (http://dpdk.org/ml/a

[dpdk-dev] [PATCH v6 0/7] Dynamic HW Mempool Detection Support

2018-01-22 Thread Hemant Agrawal
W.r.t the multiple discussions in the past about the ability to dynamically detect the HW mempool support. [1],[2] & [3] This patchset helps in removing the current static mempool selection model and provides a flexible model to select the pktmbuf mempool in more dynamic way. 1) This patchset upd

Re: [dpdk-dev] [PATCH v6 0/7] eventdev: cover letter: eth Rx adapter

2017-10-10 Thread Jerin Jacob
-Original Message- > Date: Wed, 11 Oct 2017 03:51:30 +0530 > From: Nikhil Rao > To: jerin.ja...@caviumnetworks.com, bruce.richard...@intel.com > CC: dev@dpdk.org > Subject: [PATCH v6 0/7] eventdev: cover letter: eth Rx adapter > X-Mailer: git-send-email 2.7.4 > > Eventdev-based networking

Re: [dpdk-dev] [PATCH v6 0/7] eventdev: cover letter: eth Rx adapter

2017-10-10 Thread Jerin Jacob
-Original Message- > Date: Wed, 11 Oct 2017 03:51:30 +0530 > From: Nikhil Rao > To: jerin.ja...@caviumnetworks.com, bruce.richard...@intel.com > CC: dev@dpdk.org > Subject: [PATCH v6 0/7] eventdev: cover letter: eth Rx adapter > X-Mailer: git-send-email 2.7.4 > > Eventdev-based networking

[dpdk-dev] [PATCH v6 0/7] eventdev: cover letter: eth Rx adapter

2017-10-10 Thread Nikhil Rao
Eventdev-based networking applications require a component to dequeue packets from NIC Rx queues and inject them into eventdev queues[1]. While some platforms (e.g. Cavium Octeontx) do this operation in hardware, other platforms use software. This patchset introduces an ethernet Rx event adapter t

Re: [dpdk-dev] [PATCH v6 0/7] Add Membership Library

2017-10-08 Thread Thomas Monjalon
> Yipeng Wang (7): > member: implement main API > member: implement HT mode > member: implement vBF mode > member: add AVX for HT mode > member: enable the library > test/member: add functional and perf tests > doc: add membership documentation It looks good. I have fixed some minor

[dpdk-dev] [PATCH v6 0/7] Add Membership Library

2017-10-03 Thread Yipeng Wang
DPDK Membership Library provides an API that can be used by many DPDK applications to conduct one or more set-membership tests (we mention some possible use cases below, but interested readers can refer to [1] for a wider survey of use cases). The basic functionalities of the Membership Library in

[dpdk-dev] [PATCH v6 0/7] virtio support for container

2016-06-02 Thread Jianfeng Tan
v6: - Move driver related code into from driver/net/virtio/virtio-user/ to driver/net/virtio/ directory, inside virtio_user_ethdev.c. - Rename vdev to virtio_user in comments and code. - Merge code, which lies in virtio_user_pci.c, into virtio_user_ethdev.c. - Add some comments at virtio-use

[dpdk-dev] [PATCH v6 0/7] support for netronome nfp-6xxx card

2015-11-06 Thread Alejandro Lucero
Yes. There was a bug in 1.8 affecting how BARs are used in the device, but this should be fixed in 2.2 On Thu, Nov 5, 2015 at 11:42 PM, Stephen Hemminger < stephen at networkplumber.org> wrote: > On Thu, 05 Nov 2015 11:59:59 +0100 > Vincent JARDIN wrote: > > > > > On 05/11/2015 11:43, Alejandro

[dpdk-dev] [PATCH v6 0/7] support for netronome nfp-6xxx card

2015-11-05 Thread Stephen Hemminger
On Thu, 05 Nov 2015 11:59:59 +0100 Vincent JARDIN wrote: > > On 05/11/2015 11:43, Alejandro.Lucero wrote: > > From: "Alejandro.Lucero" > > > > This patchset adds a new PMD for Netronome nfp-6xxx card. > > Just PCI Virtual Functions supported. > > Using this PMD requires previous Netronome BSP i

[dpdk-dev] [PATCH v6 0/7] support for netronome nfp-6xxx card

2015-11-05 Thread Vincent JARDIN
On 05/11/2015 11:43, Alejandro.Lucero wrote: > From: "Alejandro.Lucero" > > This patchset adds a new PMD for Netronome nfp-6xxx card. > Just PCI Virtual Functions supported. > Using this PMD requires previous Netronome BSP installation. > I understand that this PMD needs a kernel driver which is

[dpdk-dev] [PATCH v6 0/7] support for netronome nfp-6xxx card

2015-11-05 Thread Alejandro Lucero
Yes, this is true. There is a internal Netronome project for upstreaming the netdev kernel driver along with a BSP driver. PMD support will be in the BSP. There is a public github repo with current drivers: https://github.com/Netronome/nfp-drv-kmods On Thu, Nov 5, 2015 at 10:59 AM, Vincent JAR

[dpdk-dev] [PATCH v6 0/7] support for netronome nfp-6xxx card

2015-11-05 Thread Alejandro.Lucero
From: "Alejandro.Lucero" This patchset adds a new PMD for Netronome nfp-6xxx card. Just PCI Virtual Functions supported. Using this PMD requires previous Netronome BSP installation. v6: - Making each patch compilable v5: - Splitting up patches by functionality v4: - Getting rid of nfp_uio.

[dpdk-dev] [PATCH v6 0/7] i40e: PCI Port Hotplug Changes

2015-07-19 Thread Thomas Monjalon
> > Bernard Iremonger (7): > > i40e: changes to support PCI Port Hotplug > > i40e: release vmdq vsi's in dev_close > > i40e: increase ASQ_DELAY_MS to 100 and MAX_TRY_TIMES to 20 in > > i40evf_wait_cmd_done() > > i40e: call _clear_cmd() when error occurs > > i40e: clear queues in i40ev

[dpdk-dev] [PATCH v6 0/7] Cuckoo hash - part 3 of Cuckoo hash

2015-07-11 Thread Pablo de Lara
This patchset is to replace the existing hash library with a more efficient and functional approach, using the Cuckoo hash method to deal with collisions. This method is based on using two different hash functions to have two possible locations in the hash table where an entry can be. So, if a buck

[dpdk-dev] [PATCH v6 0/7] i40e: PCI Port Hotplug Changes

2015-07-10 Thread Zhang, Helin
> -Original Message- > From: Iremonger, Bernard > Sent: Friday, July 3, 2015 7:04 AM > To: dev at dpdk.org > Cc: Zhang, Helin; Qiu, Michael; Iremonger, Bernard > Subject: [PATCH v6 0/7] i40e: PCI Port Hotplug Changes > > Changes in V6: > Rebased to latest code. > Removed release of rx an

[dpdk-dev] [PATCH v6 0/7] i40e: PCI Port Hotplug Changes

2015-07-03 Thread Bernard Iremonger
Changes in V6: Rebased to latest code. Removed release of rx and tx queues from uninit() functions. added patch 7, add function i40e_dev_free_queues() and call from close() functions. Changes in V5: Increased timeout in i40evf_wait_cmd_done() Set nb_rx_queues and nb_tx_queues to 0 in uninit funct

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-24 Thread Bruce Richardson
On Tue, Feb 24, 2015 at 04:10:34AM +0100, Thomas Monjalon wrote: > 2015-02-24 09:00, Yerden Zhumabekov: > > > > 23.02.2015 23:36, Thomas Monjalon ?: > > > 2015-02-19 15:21, Bruce Richardson: > > >> Confirmed, this worked for me too. > > >> Looking at the patches, they look good. However, one t

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-24 Thread Yerden Zhumabekov
23.02.2015 23:36, Thomas Monjalon ?: > 2015-02-19 15:21, Bruce Richardson: >> Confirmed, this worked for me too. >> Looking at the patches, they look good. However, one thing I think we are >> missing >> is a unit test to verify that all our CRC implementations give the same >> result. >> Th

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-24 Thread Thomas Monjalon
2015-02-24 09:00, Yerden Zhumabekov: > > 23.02.2015 23:36, Thomas Monjalon ?: > > 2015-02-19 15:21, Bruce Richardson: > >> Confirmed, this worked for me too. > >> Looking at the patches, they look good. However, one thing I think we are > >> missing > >> is a unit test to verify that all our

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-23 Thread Thomas Monjalon
2015-02-19 15:21, Bruce Richardson: > Confirmed, this worked for me too. > Looking at the patches, they look good. However, one thing I think we are > missing > is a unit test to verify that all our CRC implementations give the same > result. > That would be useful as a sanity check of the softwa

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-19 Thread Bruce Richardson
On Mon, Feb 02, 2015 at 11:39:18AM +0600, Yerden Zhumabekov wrote: > > 02.02.2015 9:31, Neil Horman ?: > > On Mon, Feb 02, 2015 at 09:07:45AM +0600, Yerden Zhumabekov wrote: > > > >> I think so, I've just successfully built it against latest snapshot with > >> RTE_TARGET > >> equal to 'x86_64-

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-02 Thread Yerden Zhumabekov
02.02.2015 9:31, Neil Horman ?: > On Mon, Feb 02, 2015 at 09:07:45AM +0600, Yerden Zhumabekov wrote: > >> I think so, I've just successfully built it against latest snapshot with >> RTE_TARGET >> equal to 'x86_64-native-linuxapp-gcc'. >> > Please confirm that setting the machine type to defaul

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-02 Thread Yerden Zhumabekov
01.02.2015 20:13, Neil Horman ?: > On Thu, Jan 29, 2015 at 02:48:11PM +0600, Yerden Zhumabekov wrote: >> This is a rework of my previous patches improving performance of >> rte_hash_crc. >> >> Summary of changes: >> * software implementation of CRC32 introduced; >> * in the runtime, algorithm

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-01 Thread Neil Horman
On Mon, Feb 02, 2015 at 09:07:45AM +0600, Yerden Zhumabekov wrote: > > 01.02.2015 20:13, Neil Horman ?: > > On Thu, Jan 29, 2015 at 02:48:11PM +0600, Yerden Zhumabekov wrote: > >> This is a rework of my previous patches improving performance of > >> rte_hash_crc. > >> > >> Summary of changes:

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-02-01 Thread Neil Horman
On Thu, Jan 29, 2015 at 02:48:11PM +0600, Yerden Zhumabekov wrote: > This is a rework of my previous patches improving performance of rte_hash_crc. > > Summary of changes: > * software implementation of CRC32 introduced; > * in the runtime, algorithm can fall back to software version if CPU doesn'

[dpdk-dev] [PATCH v6 0/7] rte_hash_crc reworked to be platform-independent

2015-01-29 Thread Yerden Zhumabekov
This is a rework of my previous patches improving performance of rte_hash_crc. Summary of changes: * software implementation of CRC32 introduced; * in the runtime, algorithm can fall back to software version if CPU doesn't support SSE4.2; * best available algorithm is automatically detected upon