On Sat, 11 Jun 2022 09:55:00 +0800
fengchengwen wrote:
> On 2022/6/10 23:28, Stephen Hemminger wrote:
> > Need to warn users of DPDK spinlocks from non-pinned threads.
> > This is similar wording to Linux documentation in pthread_spin_init.
> >
> > Signed-off-by: Stephen Hemminger
> > ---
> >
On Sat, 11 Jun 2022 03:36:43 +0530
Rahul Lakkireddy wrote:
> Add comma after 1 in 1000 too, like 1,000. Also, since max uint64_t is
> a 20 digit number, increase space in temporary array to hold 20 digits.
> Fixes following warnings when using optimization=1 build flag with
> GCC 11.
>
> ../app/
On Fri, 10 Jun 2022 16:48:15 -0700
Tyler Retzlaff wrote:
> >
> > ++ locking
> > +
> > + If a pthread, that is not pinned to an lcore acquires a lock such as a
>
> nit: suggest not using term pthread but instead just say thread as not
> to imply a specific platform/implementation.
>
> > +
On Fri, Jun 10, 2022 at 08:28:19AM -0700, Stephen Hemminger wrote:
> Need to warn users of DPDK spinlocks from non-pinned threads.
> This is similar wording to Linux documentation in pthread_spin_init.
>
> Signed-off-by: Stephen Hemminger
> ---
> doc/guides/prog_guide/env_abstraction_layer.rst |
On Fri, Jun 10, 2022 at 08:28:19AM -0700, Stephen Hemminger wrote:
> Need to warn users of DPDK spinlocks from non-pinned threads.
> This is similar wording to Linux documentation in pthread_spin_init.
>
> Signed-off-by: Stephen Hemminger
Acked-by: Tyler Retzlaff
> ---
> doc/guides/prog_guide
On Fri, Jun 10, 2022 at 08:23:43AM -0700, Stephen Hemminger wrote:
> The DPDK is not designed to be used from a signal handler.
> Add a notice in the documentation describing this limitation,
> similar to Linux signal-safety manual page.
>
> Bugzilla ID: 1030
> Signed-off-by: Stephen Hemminger
A
On Fri, 10 Jun 2022 15:53:34 -0700
Tyler Retzlaff wrote:
> On Fri, Jun 10, 2022 at 08:23:43AM -0700, Stephen Hemminger wrote:
> > The DPDK is not designed to be used from a signal handler.
> > Add a notice in the documentation describing this limitation,
> > similar to Linux signal-safety manual
On Fri, Jun 10, 2022 at 08:23:43AM -0700, Stephen Hemminger wrote:
> The DPDK is not designed to be used from a signal handler.
> Add a notice in the documentation describing this limitation,
> similar to Linux signal-safety manual page.
>
> Bugzilla ID: 1030
> Signed-off-by: Stephen Hemminger
>
On Thu, Jun 09, 2022 at 11:24:12PM +0100, Konstantin Ananyev wrote:
> 09/06/2022 14:58, Tyler Retzlaff пишет:
> >Add rte_thread_equal() that tests if two rte_thread_id are equal.
> >
> >Signed-off-by: Narcisa Vasile
> >Signed-off-by: Tyler Retzlaff
> >---
> > lib/eal/common/rte_thread.c | 6 ++
Skip IPSec ESN and antireplay cases, if there are no packets. Fixes
following warning when using optimization=1 build flag with GCC 11.
../app/test/test_cryptodev.c: In function ‘test_ipsec_pkt_replay’:
../app/test/test_cryptodev.c:10074:15: warning: ‘td_outb’ may be used
uninitialized [-Wmaybe-u
Add comma after 1 in 1000 too, like 1,000. Also, since max uint64_t is
a 20 digit number, increase space in temporary array to hold 20 digits.
Fixes following warnings when using optimization=1 build flag with
GCC 11.
../app/test-flow-perf/main.c: In function ‘pretty_number’:
../app/test-flow-perf
This commit corrects the advertized capabilities reported by the DLB2 PMD.
Previously DLB2 reported supporting RTE_EVENT_DEV_CAP_QUEUE_QOS, but the
DLB2 hardware does not support such capability. This commit removes that
feature from the reported capabilities feature set.
Additionally, two capabi
Extend openssl crypto PMD to support CMAC operations.
Signed-off-by: Ashwin Sekhar T K
---
drivers/crypto/openssl/openssl_pmd_private.h | 9 ++
drivers/crypto/openssl/rte_openssl_pmd.c | 88
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 20 +
3 files changed, 117 i
On Xeon, 512b accesses are available, so movdir64 instruction is able to
perform 512b read and write to DLB producer port. In order for movdir64
to be able to pull its data from store buffers (store-buffer-forwarding)
(before actual write), data should be in single 512b write format.
This commit ad
Enable compilation for non x86 architectures by conditionally
compiling x86 specific code.
Signed-off-by: Ashwin Sekhar T K
---
drivers/crypto/ipsec_mb/ipsec_mb_private.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/crypto/ipsec_mb/ipsec_mb_private.c
b/drivers/crypto/ipsec_mb/i
On Fri, Jun 10, 2022 at 10:41:25AM -0500, Timothy McDaniel wrote:
> On Xeon, 512b accesses are available, so movdir64 instruction is able to
> perform 512b read and write to DLB producer port. In order for movdir64
> to be able to pull its data from store buffers (store-buffer-forwarding)
> (before
When counting the batch allocated pointers in cnxk mempool driver,
currently it always waits for in-flight batch operations to finish.
Add a provision to make this waiting optional.
Signed-off-by: Ashwin Sekhar T K
---
drivers/common/cnxk/roc_npa.h| 7 +--
drivers/mempool/cnxk/cn
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Friday, 10 June 2022 17.36
>
> Since use of KNI is no longer advised (due to known issues and the fact
> it's an out-of-tree module), virtio-user is recommended for new
> developments. To help encourage this, we improve the doc H
> -Original Message-
> From: Richardson, Bruce
> Sent: Friday, June 10, 2022 10:43 AM
> To: McDaniel, Timothy
> Cc: jer...@marvell.com; dev@dpdk.org; Wires, Kent
> Subject: Re: [PATCH v5] event/dlb2: add support for single 512B write of 4 QEs
>
> On Fri, Jun 10, 2022 at 03:41:00PM +0
On Fri, Jun 10, 2022 at 03:41:00PM +0100, McDaniel, Timothy wrote:
>
>
> > -Original Message-
> > From: Richardson, Bruce
> > Sent: Friday, June 10, 2022 8:12 AM
> > To: McDaniel, Timothy
> > Cc: jer...@marvell.com; dev@dpdk.org; Wires, Kent
> > Subject: Re: [PATCH v5] event/dlb2: add
On Xeon, 512b accesses are available, so movdir64 instruction is able to
perform 512b read and write to DLB producer port. In order for movdir64
to be able to pull its data from store buffers (store-buffer-forwarding)
(before actual write), data should be in single 512b write format.
This commit ad
To help encourage use of virtio-user in place of KNI, put a reference to
the relevant howto section at the top of the KNI doc.
Signed-off-by: Bruce Richardson
---
doc/guides/prog_guide/kernel_nic_interface.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/prog_guide/kernel
The HOWTO guide for using virtio-user as an exception path to the kernel
only provided an example of how testpmd may be used for that purpose.
However, a real application wanting to use virtio-user as exception path
would likely want to create such devices from code within the app
itself. Therefore
Since the section in the "howto" has been renamed from "exceptional
path" to "exception path", we can rename the relevant files to match
this new name too.
Signed-off-by: Bruce Richardson
---
...ptional_path.svg => virtio_user_as_exception_path.svg} | 0
doc/guides/howto/index.rst
This patch extensively reworks the howto guide on using virtio-user for
exception packets. Changes include:
* rename "exceptional path" to "exception path"
* remove references to uio and just reference vfio-pci
* simplify testpmd command-lines, giving a basic usage example first
before adding on
Since use of KNI is no longer advised (due to known issues and the fact
it's an out-of-tree module), virtio-user is recommended for new
developments. To help encourage this, we improve the doc HOWTO section
on using virtio-user and add a link to that document from the main KNI
section in the progra
Need to warn users of DPDK spinlocks from non-pinned threads.
This is similar wording to Linux documentation in pthread_spin_init.
Signed-off-by: Stephen Hemminger
---
doc/guides/prog_guide/env_abstraction_layer.rst | 10 ++
1 file changed, 10 insertions(+)
diff --git a/doc/guides/prog_
The DPDK is not designed to be used from a signal handler.
Add a notice in the documentation describing this limitation,
similar to Linux signal-safety manual page.
Bugzilla ID: 1030
Signed-off-by: Stephen Hemminger
---
doc/guides/prog_guide/env_abstraction_layer.rst | 13 +
1 file c
Hi Andrew,
Sorry for the late response, please see replies inline.
> -Original Message-
> From: Andrew Rybchenko
> Sent: Tuesday, June 7, 2022 6:49 PM
> To: Ding, Xuan ; Wu, WenxuanX
> ; tho...@monjalon.net; Li, Xiaoyun
> ; ferruh.yi...@xilinx.com; Singh, Aman Deep
> ; dev@dpdk.org; Zhan
> -Original Message-
> From: Richardson, Bruce
> Sent: Friday, June 10, 2022 8:12 AM
> To: McDaniel, Timothy
> Cc: jer...@marvell.com; dev@dpdk.org; Wires, Kent
> Subject: Re: [PATCH v5] event/dlb2: add support for single 512B write of 4 QEs
>
> On Fri, Jun 10, 2022 at 07:35:44AM -05
On Mon, May 30, 2022 at 06:33:14AM +0100, Xia, Chenbo wrote:
> Hi Bruce,
>
> > -Original Message-
> > From: Richardson, Bruce
> > Sent: Saturday, May 28, 2022 12:37 AM
> > To: dev@dpdk.org
> > Cc: Maxime Coquelin ; Xia, Chenbo
> > ; Richardson, Bruce
> > Subject: [PATCH v2 1/2] doc/howto
On Mon, May 30, 2022 at 06:44:27AM +0100, Xia, Chenbo wrote:
> > -Original Message-
> > From: Richardson, Bruce
> > Sent: Saturday, May 28, 2022 12:37 AM
> > To: dev@dpdk.org
> > Cc: Maxime Coquelin ; Xia, Chenbo
> > ; Richardson, Bruce
> > Subject: [PATCH v2 2/2] doc/howto: add code exam
I'm trying to understand if this change is at all related to an issue we
are experiencing with newer firmwares (
https://mails.dpdk.org/archives/dev/2022-April/238621.html) that happened
to start with 8.4 and affected qinq offload processing. I can say loading
this patch and running testpmd does n
When passing in test names to run via either the DPDK_TEST environment
variable or via extra argv parameters, the checks run on those commands
can miss valid commands that are registered with the cmdline library in
the initial context used to set it up. This is seen in the fact that the
"dump_*" se
The cmdline library cmdline_parse() function parses a command and
executes the action automatically too. The cmdline_valid_buffer function
also uses this function to validate commands, meaning that there is no
function to validate a command as ok without executing it.
To fix this omission, we extr
The dump* unit tests are uncallable from our test framework because the command
validation in the unit test binary is incorrect. Rather than trying to fix this
directly in the binary, a better approach is to add command validation to the
cmdline library - which already has 99% of what we need alrea
On Fri, Jun 10, 2022 at 03:08:49PM +0100, Bruce Richardson wrote:
> On Tue, Jun 07, 2022 at 10:08:30AM +0200, Olivier Matz wrote:
> > Hi Bruce,
> >
> > Just few minor comments below.
> >
> > On Fri, May 20, 2022 at 04:12:39PM +0100, Bruce Richardson wrote:
> > > The cmdline library cmdline_parse(
On Tue, Jun 07, 2022 at 10:08:30AM +0200, Olivier Matz wrote:
> Hi Bruce,
>
> Just few minor comments below.
>
> On Fri, May 20, 2022 at 04:12:39PM +0100, Bruce Richardson wrote:
> > The cmdline library cmdline_parse() function parses a command and
> > executes the action automatically too. The c
On Wed, May 18, 2022 at 11:11:00AM +0200, David Marchand wrote:
> clang 14 raises the following warning:
>
> ../drivers/net/mlx5/linux/mlx5_ethdev_os.c:1137:52: error: 'fscanf'
> may overflow; destination buffer in argument 3 has size 16, but the
> corresponding specifier may require size
On Mon, May 23, 2022 at 3:30 PM wrote:
>
> From: Pavan Nikhilesh
>
> Use mempool cache for vector mempool as vectors are freed by the Tx
> routine, also increase the minimum pool size to 512 to avoid resource
> contention on Rx.
>
> Signed-off-by: Pavan Nikhilesh
Acked-by: Jerin Jacob
> ---
On Mon, May 23, 2022 at 3:30 PM wrote:
>
> From: Pavan Nikhilesh
>
> Use mempool cache for vector mempool as vectors are freed by the Tx
> routine, also increase the minimum pool size to 512 to avoid resource
> contention on Rx.
>
> Signed-off-by: Pavan Nikhilesh
Acked-by: Jerin Jacob
> ---
On Fri, Jun 10, 2022 at 07:35:44AM -0500, Timothy McDaniel wrote:
> On Xeon, 512b accesses are available, so movdir64 instruction is able to
> perform 512b read and write to DLB producer port. In order for movdir64
> to be able to pull its data from store buffers (store-buffer-forwarding)
> (before
Hello maintainers,
On Wed, May 18, 2022 at 12:17 PM David Marchand
wrote:
>
> GCC 12 raises the following warning:
>
> In function ‘fill_sg_comp_from_iov’,
> inlined from ‘cpt_kasumi_enc_prep’ at
> ../drivers/common/cpt/cpt_ucode.h:2176:8,
> inlined from ‘cpt_fc_enc_hmac_prep’ at
On Wed, May 18, 2022 at 12:17 PM David Marchand
wrote:
>
> GCC 12 raises the following warning:
>
> ../drivers/net/enetfec/enet_ethdev.c: In function
> ‘enetfec_rx_queue_setup’:
> ../drivers/net/enetfec/enet_ethdev.c:473:9: error: array
> subscript 1 is
> above array bounds of
On Thu, Jun 2, 2022 at 11:50 AM Bruce Richardson
wrote:
>
> On Wed, May 18, 2022 at 12:16:48PM +0200, David Marchand wrote:
> > GCC 12 raises the following warning:
> >
> > In function ‘__rte_ring_enqueue_elems_64’,
> > inlined from ‘__rte_ring_enqueue_elems’ at
> > ../lib/ring/rte_rin
On Xeon, 512b accesses are available, so movdir64 instruction is able to
perform 512b read and write to DLB producer port. In order for movdir64
to be able to pull its data from store buffers (store-buffer-forwarding)
(before actual write), data should be in single 512b write format.
This commit ad
On Xeon, 512b accesses are available, so movdir64 instruction is able to
perform 512b read and write to DLB producer port. In order for movdir64
to be able to pull its data from store buffers (store-buffer-forwarding)
(before actual write), data should be in single 512b write format.
This commit ad
On 6/10/2022 11:39 AM, Morten Brørup wrote:
CAUTION: This message has originated from an External Source. Please use proper
judgment and caution when opening attachments, clicking links, or responding to
this email.
From: Ferruh Yigit [mailto:ferruh.yi...@xilinx.com]
Sent: Friday, 10 June 20
On Tue, Jun 07, 2022 at 12:48:54PM +0100, Herakliusz Lipiec wrote:
> Meson build system creates a vhost binary but Makefile
> and docs reference same as vhost-switch. Updating makefile
> to match meson.
>
> Signed-off-by: Herakliusz Lipiec
> ---
> examples/vhost/Makefile | 2 +-
> 1 file changed
Hi Kozlyuk,
Here is bugzilla ticket https://bugs.dpdk.org/show_bug.cgi?id=1028, its bad
commit id is this patch.
Could you please have a look? Thanks so much.
Best regards,
Yu Jiang
> -Original Message-
> From: Thomas Monjalon
> Sent: Wednesday, May 25, 2022 11:46 PM
> To: Dmitry Kozly
Add new packet type flags instead of overwriting.
Fixes: d04bb1c52647 ("examples/ipsec-secgw: use HW parsed packet type in poll
mode")
Signed-off-by: Radu Nicolau
---
examples/ipsec-secgw/ipsec-secgw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/examples/ipsec-secgw/ips
> From: Ferruh Yigit [mailto:ferruh.yi...@xilinx.com]
> Sent: Friday, 10 June 2022 12.13
>
> On 6/8/2022 11:49 PM, Stephen Hemminger wrote:
> > Gcc 12 adds more array bounds checking (good); but it is not smart
> > enough to realize that for small fixed sizes, the bigger move options
> > are not u
On 6/8/2022 11:49 PM, Stephen Hemminger wrote:
Gcc 12 adds more array bounds checking (good); but it is not smart
enough to realize that for small fixed sizes, the bigger move options
are not used.
An example is using rte_memcpy() on a RSS key of 40 bytes may trigger
rte_memcpy complaints from r
On Tue, May 31, 2022 at 5:50 PM Hanumanth Pothula wrote:
>
> Observing a crash when the user runs the second test case, with the
> first test case using all HWGRP and HWS, SSO resources. This happens
> as there are no HWGRP and HWS resources left for the second test case.
>
> Make sure to process
Response info may have valid sub_event_type. Pass this to the event
generated by CPT.
Signed-off-by: Anoob Joseph
Reviewed-by: Shijith Thotton
Reviewed-by: Jerin Jacob Kollanukkaran
---
drivers/crypto/cnxk/cn10k_cryptodev_ops.c | 7 ---
drivers/crypto/cnxk/cn9k_cryptodev_ops.c | 7 ---
Response info may have valid sub_event_type. Pass this to the event
generated by CPT.
Signed-off-by: Anoob Joseph
Reviewed-by: Shijith Thotton
Reviewed-by: Jerin Jacob Kollanukkaran
---
drivers/crypto/octeontx/otx_cryptodev_ops.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/cryp
From: Robin Zhang
Outer VLAN processing is supported after firmware v8.4, kernel driver
also change the default behavior to support this feature. To align with
kernel driver, add support for outer VLAN processing in DPDK.
But it is forbidden for firmware to change the Inner/Outer VLAN
configurat
Return with error on fail to initialize RoC Model.
Signed-off-by: Hanumanth Pothula
---
drivers/common/cnxk/roc_platform.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/common/cnxk/roc_platform.c
b/drivers/common/cnxk/roc_platform.c
index ebb6225f4d..443aa8d3
> -Original Message-
> From: Zhang, Qi Z
> Sent: 2022年6月10日 16:07
> To: Liu, KevinX ; dev@dpdk.org
> Cc: Zhang, Yuying ; Xing, Beilei
> ; Yang, SteveX ; Zhang,
> RobinX ; Liu, KevinX
> Subject: RE: [PATCH v6] net/i40e: add outer VLAN processing
>
>
>
> > -Original Message-
>
On 6/9/2022 12:49 PM, Dongdong Liu wrote:
From: Huisong Li
Currently, some eth devices are added to bond device, these devices are not
released when the quit command is executed in testpmd. This patch adds the
release operation for all active slaves under a bond device.
Fixes: 0e545d3047fe ("ap
> -Original Message-
> From: Kevin Liu
> Sent: Friday, June 10, 2022 11:52 PM
> To: dev@dpdk.org
> Cc: Zhang, Yuying ; Xing, Beilei
> ; Yang, SteveX ; Zhang,
> RobinX ; Liu, KevinX
> Subject: [PATCH v6] net/i40e: add outer VLAN processing
>
> From: Robin Zhang
>
> Outer VLAN process
From: Robin Zhang
Outer VLAN processing is supported after firmware v8.4, kernel driver
also change the default behavior to support this feature. To align with
kernel driver, add support for outer VLAN processing in DPDK.
But it is forbidden for firmware to change the Inner/Outer VLAN
configurat
Hi Maxime,
> -Original Message-
> From: Xia, Chenbo
> Sent: Friday, June 10, 2022 11:50 AM
> To: Maxime Coquelin ; dev@dpdk.org;
> jasow...@redhat.com; david.march...@redhat.com; Matz, Olivier
> ; Ma, WenwuX ; Zhang,
> Yuying ; Singh, Aman Deep
>
> Subject: RE: [PATCH v2 6/6] net/vhost:
> -Original Message-
> From: jer...@marvell.com
> Sent: Thursday, June 9, 2022 1:13 AM
> To: dev@dpdk.org; Jan Viktorin ; Ruifeng Wang
> ; Bruce Richardson
> ; David Christensen
> ; Stanislaw Kardach ;
> Konstantin Ananyev
> Cc: tho...@monjalon.net; david.march...@redhat.com;
> juraj.lin.
From: Robin Zhang
Outer VLAN processing is supported after firmware v8.4, kernel driver
also change the default behavior to support this feature. To align with
kernel driver, add support for outer VLAN processing in DPDK.
But it is forbidden for firmware to change the Inner/Outer VLAN
configurat
Hi Maxime,
> -Original Message-
> From: Xia, Chenbo
> Sent: Friday, June 10, 2022 11:49 AM
> To: Maxime Coquelin ; dev@dpdk.org;
> jasow...@redhat.com; david.march...@redhat.com; Matz, Olivier
> ; Ma, WenwuX ; Zhang,
> Yuying ; Singh, Aman Deep
> ; Jiang, Cheng1
> Subject: RE: [PATCH v2
66 matches
Mail list logo
