> 'rte_eth_rx_burst' returns uint16_t. The same value need to be passed
> to 'process_packets' functions which performs further processing. Having
> this function use 'uint8_t' can result in issues when MAX_PKT_BURST is
> larger.
>
> The route functions (route4_pkts & route6_pkts) take uint8_t a
DMA library has a function to get DMA device based on device name but
there is no function to get DMA device using device id.
Added a function that lookup for the dma device using device id and
returns the pointer to the same.
Signed-off-by: Amit Prakash Shukla
Acked-by: Chengwen Feng
---
v2:
https://bugs.dpdk.org/show_bug.cgi?id=1336
Bug ID: 1336
Summary: Statistic counter rx_missed_errors always shows zero
no matter how large the traffic was generated on
Mellanox NICs
Product: DPDK
Version: 22.11
When building nic_uio module on FreeBSD 14, a build error is given in
the DRIVER_MODULE macro:
.../nic_uio.c:84:81: error: too many arguments provided to function-like macro
invocation
DRIVER_MODULE(nic_uio, pci, nic_uio_driver, nic_uio_devclass, nic_uio_modevent,
0);
> Currently the config option allows lcore IDs up to 255,
> irrespective of RTE_MAX_LCORES and needs to be fixed.
>
> The patch allows config options based on DPDK config.
>
> Fixes: d299106e8e31 ("examples/ipsec-secgw: add IPsec sample application")
> Cc: sergio.gonzalez.mon...@intel.com
> Cc:
> Currently the config option allows lcore IDs up to 255,
> irrespective of RTE_MAX_LCORES and needs to be fixed.
>
> The patch allows config options based on DPDK config.
>
> Fixes: af75078fece3 ("first public release")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Sivaprasad Tummala
> ---
> exa
>
> > Currently the config option allows lcore IDs up to 255,
> > irrespective of RTE_MAX_LCORES and needs to be fixed.
> >
> > The patch allows config options based on DPDK config.
> >
> > Fixes: af75078fece3 ("first public release")
> > Cc: sta...@dpdk.org
> >
> > Signed-off-by: Sivaprasad Tum
[AMD Official Use Only - General]
Hi Konstantin,
> -Original Message-
> From: Konstantin Ananyev
> Sent: Tuesday, December 19, 2023 6:00 PM
> To: Konstantin Ananyev ; Tummala, Sivaprasad
> ; david.h...@intel.com;
> anatoly.bura...@intel.com; jer...@marvell.com; radu.nico...@intel.com;
>
Hi Sivaprasad,
>
> Hi Konstantin,
>
> > -Original Message-
> > From: Konstantin Ananyev
> > Sent: Tuesday, December 19, 2023 6:00 PM
> > To: Konstantin Ananyev ; Tummala, Sivaprasad
> > ; david.h...@intel.com;
> > anatoly.bura...@intel.com; jer...@marvell.com; radu.nico...@intel.com;
Docs for IP Fragment said RTE_LIBRTE_IP_FRAG_MAX_FRAGS was 4 by default,
however this was changed to 8.
Documentation has been updated to account for this, including a
snippet of the code where RTE_LIBRTE_IP_FRAG_MAX_FRAGS is defined to
ensure the documentation stays up to date.
Signed-off-by: Eu
Removed LIBRTE from name as its an old prefix.
Signed-off-by: Euan Bourke
---
app/test/test_reassembly_perf.c | 2 +-
config/rte_config.h | 2 +-
doc/guides/prog_guide/ip_fragment_reassembly_lib.rst | 4 ++--
doc/guides/sample_app_ug/ip_reass
18/12/2023 15:38, David Marchand:
> +#ifdef RTE_TOOLCHAIN_GCC
> +#define RTE_LOG_CHECK_NO_NEWLINE(fmt) \
> + static_assert(!__builtin_strchr(fmt, '\n'), \
> + "This log format string contains a \\n")
> +#else
> +#define RTE_LOG_CHECK_NO_NEWLINE(...)
> +#endif
No support in clang?
This patchset adds support for a new gen3 QuickAssist device.
There are some changes for this device in comparison to the
existing gen3 implementation:
- DES and Kasumi removed from capabilities.
- ZUC256 added to capabiltiies.
- New device ID.
- New CMAC macros included.
- Some algorithms mo
Add new gen3 QAT device ID.
This device has a wireless slice, but other gen3 devices do not, so we
must set a flag to indicate this wireless enabled device.
Capabilities for the device are slightly different from base gen3
capabilities, some are removed from the list for this device.
Signed-off-b
The new gen3 device handles wireless algorithms on wireless slices,
based on the device wireless slice support, set the required flags for
these algorithms to move slice.
One of the algorithms supported for the wireless slices is ZUC 256,
support is added for this, along with modifying the capabil
The new QAT GEN3 device uses new macros for CMAC values, rather than
using XCBC_MAC ones.
The wireless slice handles CMAC in the new gen3 device, and no key
precomputes are required by SW.
Signed-off-by: Ciara Power
---
drivers/common/qat/qat_adf/icp_qat_hw.h | 4 +++-
drivers/crypto/qat/qat_s
Currently only symmetric crypto has been added for the new gen3 device,
adding a check to disable asym and comp PMDs for this device.
Signed-off-by: Ciara Power
---
drivers/compress/qat/qat_comp_pmd.c | 3 ++-
drivers/crypto/qat/qat_asym.c | 3 ++-
2 files changed, 4 insertions(+), 2 delet
Replace pktmbuf pool with mempool, this allows increase in MOPS
especially in lower buffer size. Using Mempool, allows to reduce
the extra CPU cycles.
Changes made are
1. pktmbuf pool create with mempool create.
2. create src & dst pointer array from the appropaite numa.
3. use get pool and put fo
Modify the user display data with total average latency per worker.
Signed-off-by: Vipin Varghese
---
app/test-dma-perf/benchmark.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/app/test-dma-perf/benchmark.c b/app/test-dma-perf/benchmark.c
index 9b1f58c78c..8b6886af62 100
The subject could be improved. That these methods are required is
kinda obvious. We should try to actually include some useful
information in the subject, such as "add basic methods to testpmd
shell", but even that is not saying much. Maybe "add startup
verification and forwarding to testpmd shell"
We should also update the subject and the body based on our previous
discussion. I don't think they properly describe the change, as we're
also updating the method's behavior of DPDK apps.
On Mon, Dec 18, 2023 at 7:13 PM wrote:
>
> From: Jeremy Spewock
>
> Modified interactive applications to al
Reviewed-by: Juraj Linkeš
On Mon, Dec 18, 2023 at 7:13 PM wrote:
>
> From: Jeremy Spewock
>
> Added the options to filter out LLDP and ARP packets when
> sniffing for packets with scapy. This was done using BPF filters to
> ensure that the noise these packets provide does not interfere with tes
Reviewed-by: Juraj Linkeš
On Mon, Dec 18, 2023 at 7:13 PM wrote:
>
> From: Jeremy Spewock
>
> Added allow list to the EAL parameters created in DTS to ensure that
> only the relevant PCI devices are considered when launching DPDK
> applications.
>
> Signed-off-by: Jeremy Spewock
> ---
> dts/f
On Mon, Dec 18, 2023 at 7:13 PM wrote:
>
> From: Jeremy Spewock
>
> Adds methods in both os_session and linux session to allow for setting
> MTU of port interfaces in an OS agnostic way.
>
The previous two commit messages had a little bit of an explanation,
but this one is missing one. Something
Reviewed-by: Juraj Linkeš
On Mon, Dec 18, 2023 at 7:13 PM wrote:
>
> From: Jeremy Spewock
>
> Allow for scatter to be specified in the configuration file.
>
> Signed-off-by: Jeremy Spewock
> ---
> dts/framework/config/conf_yaml_schema.json | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletio
On Tue, 19 Dec 2023 07:46:18 +
bugzi...@dpdk.org wrote:
> # git log -1
> commit e5dc404d33ac1c6cea5c62a88489746c5cb5e35e (HEAD, origin/main,
> origin/HEAD, main)
> Author: Stephen Hemminger
> Date: Mon Dec 11 12:17:32 2023 -0800
>
> cryptodev: use a dynamic logtype
>
> The cryptod
On Tue, 19 Dec 2023 10:59:23 +0530
Anoob Joseph wrote:
> Instead of freeing directly, use commonly used function which also
> updates stats.
>
> Signed-off-by: Anoob Joseph
> ---
> examples/ipsec-secgw/ipsec_process.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ex
The design of the macros requires a type to be provided to the macro.
By expanding the type parameter inside of typeof it also inadvertently
allows an expression to be used which appears not to have been intended
after evaluating the parameter name and existing macro use.
Technically this is an A
Adjust the use of per lcore macro to provide type as the first argument
as to not require __typeof__ during expansion.
Signed-off-by: Tyler Retzlaff
---
lib/eal/common/eal_common_errno.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/eal/common/eal_common_errno.c
b/lib/
The design of the macros requires a type to be provided to the macro.
By expanding the type parameter inside of typeof it also inadvertently
allows an expression to be used which appears not to have been intended
after evaluating the parameter name and existing macro use.
Technically this is an A
Should we use the full name (pmd_buffer_scatter) in the subject? I
lean towards the full name.
On Mon, Dec 18, 2023 at 7:13 PM wrote:
>
> From: Jeremy Spewock
>
> This test suite provides testing the support of scattered packets by
> Poll Mode Drivers using testpmd. It incorporates 5 different t
From: Jerin Jacob
Introduce a new API to retrieve the number of available free descriptors
in a Tx queue. Applications can leverage this API in the fast path to
inspect the Tx queue occupancy and take appropriate actions based on the
available free descriptors.
A notable use case could be implem
On Tue, Dec 19, 2023 at 09:27:42AM -0800, Tyler Retzlaff wrote:
> The design of the macros requires a type to be provided to the macro.
>
> By expanding the type parameter inside of typeof it also inadvertently
> allows an expression to be used which appears not to have been intended
> after evalu
Introducing port representor support to CNXK drivers by adding virtual ethernet
ports providing a logical representation in DPDK for physical function(PF) or
SR-IOV virtual function (VF) devices for control and monitoring.
These port representor ethdev instances can be spawned on an as needed basi
- Mailbox for registering base device behind all representors
- Registering debug log type for representors
Signed-off-by: Harman Kalra
---
drivers/common/cnxk/roc_constants.h | 1 +
drivers/common/cnxk/roc_mbox.h | 8
drivers/common/cnxk/roc_nix.c | 31
Eswitch device is a parent or base device behind all the representors,
acting as transport layer between representors and representees
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_eswitch.c | 465
drivers/net/cnxk/cnxk_eswitch.h | 103 +++
drivers/ne
Configuring the hardware resources used by the eswitch device.
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_eswitch.c | 206
1 file changed, 206 insertions(+)
diff --git a/drivers/net/cnxk/cnxk_eswitch.c b/drivers/net/cnxk/cnxk_eswitch.c
index 51110a762
Implementing the devargs parsing logic via which the representors
pattern is provided. These patterns define for which representies
representors shall be created.
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_eswitch.c | 88 +
drivers/net/cnxk/cnxk_eswitch.h | 5
Basic skeleton for probing representor devices. If PF device is
passed with "representor" devargs, representor ports gets probed
as a separate ethdev device.
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_eswitch.c | 12 ++
drivers/net/cnxk/cnxk_eswitch.h | 8 +-
drivers/net/cnxk/cnxk_
- adding support for installing flow using npc_install_flow mbox
- rss action configuration for eswitch
- new mcam helper apis
Signed-off-by: Harman Kalra
---
drivers/common/cnxk/meson.build| 1 +
drivers/common/cnxk/roc_api.h | 3 +
drivers/common/cnxk/roc_eswitch.c | 285
Introducing eswitch variant of set vlan tpid api which can be
using for PF and VF
Signed-off-by: Harman Kalra
---
drivers/common/cnxk/roc_eswitch.c | 15 +++
drivers/common/cnxk/roc_eswitch.h | 4
drivers/common/cnxk/roc_nix_priv.h | 4 ++--
drivers/common/cnxk/roc_nix_vlan.
- Adding flow rules for eswitch PF and VF
- Interfaces to delete shift flow rules
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_eswitch.c | 43 ++-
drivers/net/cnxk/cnxk_eswitch.h | 25 +-
drivers/net/cnxk/cnxk_eswitch_devargs.c | 1 +
drivers/net/cnxk/cnxk_eswitch_fl
Implementing fastpath RX and TX fast path routines which can be
invoked from respective representors rx burst and tx burst
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_eswitch.h | 5 +
drivers/net/cnxk/cnxk_eswitch_rxtx.c | 212 +++
drivers/net/cnxk/meson.
Implementing the control path for representor ports, where represented
ports can be configured using TLV messaging.
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_eswitch.c | 67 ++-
drivers/net/cnxk/cnxk_eswitch.h | 8 +
drivers/net/cnxk/cnxk_rep.c | 52 ++
drivers/net/cnxk/cnxk_
Setting up a callback which gets invoked every time a representee
comes up or goes down. Later this callback gets handled by network
conterpart.
Signed-off-by: Harman Kalra
---
drivers/common/cnxk/roc_dev.c | 24
drivers/common/cnxk/roc_dev_priv.h | 3 +++
drivers/
In case of any representee coming up or going down, kernel sends a
mbox up call which signals a thread to process these messages and
enable/disable HW resources accordingly.
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_eswitch.c | 8 +
drivers/net/cnxk/cnxk_eswitch.h | 20 +++
driver
Implementing ethernet device operation callbacks for
port representors PMD
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_rep.c | 28 +-
drivers/net/cnxk/cnxk_rep.h | 35 +++
drivers/net/cnxk/cnxk_rep_msg.h | 8 +
drivers/net/cnxk/cnxk_rep_ops.c | 495 +
Implementing an mbox interface to fetch the representees's ethernet
stats from the kernel.
Signed-off-by: Harman Kalra
---
drivers/common/cnxk/roc_eswitch.c | 45 +++
drivers/common/cnxk/roc_eswitch.h | 2 ++
drivers/common/cnxk/roc_mbox.h| 30 +++
Adding representor ethernet statistics support which can fetch stats
for representees which are operating independently or part of
companian app.
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_rep_msg.h | 7 ++
drivers/net/cnxk/cnxk_rep_ops.c | 140 +++-
2 fi
- ROC layer changes for supporting eswitch VF
- NIX lbk changes for esw
Signed-off-by: Harman Kalra
---
drivers/common/cnxk/roc_constants.h | 1 +
drivers/common/cnxk/roc_dev.c | 1 +
drivers/common/cnxk/roc_nix.c | 15 +--
drivers/common/cnxk/roc_nix.h | 1 +
dr
Adding support for eswitch VF to probe as normal cnxk ethernet device
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cn10k_ethdev.c| 1 +
drivers/net/cnxk/cnxk_ethdev.c | 39 ++
drivers/net/cnxk/cnxk_ethdev.h | 3 +++
drivers/net/cnxk/cnxk_ethdev_ops.c
Implementing the common infrastructural changes for supporting port
representors and represented ports used as action and pattern in net
layer.
Signed-off-by: Kiran Kumar K
Signed-off-by: Satheesh Paul
Signed-off-by: Harman Kalra
---
drivers/common/cnxk/roc_npc.c | 63 +++
Adding support for represented_port item matching and action.
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_flow.c | 107 +++
1 file changed, 57 insertions(+), 50 deletions(-)
diff --git a/drivers/net/cnxk/cnxk_flow.c b/drivers/net/cnxk/cnxk_flow.c
index
Adding support for port_representor as item matching and action.
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_flow.c | 224 +++
drivers/net/cnxk/cnxk_rep.h | 14 +++
2 files changed, 212 insertions(+), 26 deletions(-)
diff --git a/drivers/net/cnxk/cnxk
Flow operations can be performed on cnxk ports as well as representor
ports. Since representor ports are not cnxk ports but have eswitch as
base device underneath, special handling is required to align with base
infra. Introducing a flag to generic flow APIs to discriminate if the
operation request
- Implementing base infra for handling flow operations performed on
representor ports, where these representor ports may be representing
native representees or part of companian apps.
- Handling flow create operation
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_flow.h | 9 +-
driv
Implementing other flow operations - validate, destroy, query,
flush, dump for representor ports
Signed-off-by: Harman Kalra
---
drivers/net/cnxk/cnxk_rep_flow.c | 414 +++
drivers/net/cnxk/cnxk_rep_msg.h | 32 +++
2 files changed, 446 insertions(+)
diff --git a/dr
Updating the CNXK PMD documentation with the added support
for port representors.
Signed-off-by: Harman Kalra
---
MAINTAINERS | 1 +
doc/guides/nics/cnxk.rst | 58
doc/guides/nics/features/cnxk.ini| 3 ++
doc/guides/nics/fea
rte_os.h includes sched.h so install sched.h to allow DPDK installed to
DESTDIR to be usable.
Signed-off-by: Tyler Retzlaff
---
lib/eal/windows/include/meson.build | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/eal/windows/include/meson.build
b/lib/eal/windows/include/meson.build
index
[AMD Official Use Only - General]
Hi Konstantin,
> -Original Message-
> From: Konstantin Ananyev
> Sent: Tuesday, December 19, 2023 8:40 PM
> To: Tummala, Sivaprasad ;
> david.h...@intel.com; anatoly.bura...@intel.com; jer...@marvell.com;
> radu.nico...@intel.com; gak...@marvell.com; cri
> -Original Message-
> From: Rushil Gupta
> Sent: Tuesday, December 19, 2023 10:17
> To: Guo, Junfeng ; jeroe...@google.com;
> joshw...@google.com; ferruh.yi...@amd.com
> Cc: dev@dpdk.org; Rushil Gupta
> Subject: [PATCH] net/gve: Enable stats reporting for GQ format
>
> Read from share
Hi Chuanyu,
> -Original Message-
> From: Chuanyu Xue
> Sent: Monday, December 18, 2023 4:21 AM
> To: Lu, Wenzhuo ; Zhang, Qi Z
> ; Xing, Beilei
> Cc: dev@dpdk.org; Chuanyu Xue
> Subject: [PATCH] net/e1000: support launchtime feature
>
> Enable the time-based scheduled Tx of packets bas
With modern CPUs, it is possible to have higher
CPU count thus we can have higher RTE_MAX_LCORES.
In DPDK sample applications, the current config
lcore options are hard limited to 255.
The patchset fixes these constraints by allowing
all lcore IDs up to RTE_MAX_LCORES.
Sivaprasad Tummala (6):
e
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch allows config options based on DPDK config.
Fixes: af75078fece3 ("first public release")
Cc: sta...@dpdk.org
Signed-off-by: Sivaprasad Tummala
Acked-by: Konstantin Ananyev
--
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch allows config options based on DPDK config.
Fixes: f88e7c175a68 ("examples/l3fwd-power: add high/regular perf cores
options")
Cc: radu.nico...@intel.com
Cc: sta...@dpdk.org
Si
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch allows config options based on DPDK config.
Fixes: 08bd1a174461 ("examples/l3fwd-graph: add graph-based l3fwd skeleton")
Cc: ndabilpu...@marvell.com
Cc: sta...@dpdk.org
Signed-
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch allows config options based on DPDK config.
Fixes: d299106e8e31 ("examples/ipsec-secgw: add IPsec sample application")
Cc: sergio.gonzalez.mon...@intel.com
Cc: sta...@dpdk.org
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch allows config options based on DPDK config.
Fixes: de3cfa2c9823 ("sched: initial import")
Cc: sta...@dpdk.org
Signed-off-by: Sivaprasad Tummala
---
examples/qos_sched/args.c
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch allows config options based on DPDK config.
Fixes: 0e8f47491f09 ("examples/vm_power: add command to query CPU frequency")
Cc: marcinx.hajkow...@intel.com
Cc: sta...@dpdk.org
Si
With modern CPUs, it is possible to have higher
CPU count thus we can have higher RTE_MAX_LCORES.
In DPDK sample applications, the current config
lcore options are hard limited to 255.
The patchset fixes these constraints by allowing
all lcore IDs up to RTE_MAX_LCORES.
Sivaprasad Tummala (6):
e
On x86 platforms, max lcores are limited to 128 by default.
On AMD EPYC processors, this limit was adjusted for native
builds in the previous patch.
https://patches.dpdk.org/project/dpdk/patch/
20230925151027.558546-1-sivaprasad.tumm...@amd.com/
As agreed earlier in mailing list, this patch adjus
Hi all,
Here is a list of patches targeted for stable release 22.11.4.
The planned date for the final release is 5th January.
Please help with testing and validation of your use cases and report
any issues/results with reply-all to this mail. For the final release
the fixes and reported validati
> From: Sivaprasad Tummala [mailto:sivaprasad.tumm...@amd.com]
> Sent: Wednesday, 20 December 2023 08.11
>
> On x86 platforms, max lcores are limited to 128 by default.
>
> On AMD EPYC processors, this limit was adjusted for native
> builds in the previous patch.
> https://patches.dpdk.org/projec
73 matches
Mail list logo
