The following warning is observed with GCC12 compilation
with release 20.11:
In function ‘__rte_ring_enqueue_elems_64’,
inlined from ‘__rte_ring_enqueue_elems’ at
../lib/librte_ring/rte_ring_elem.h:225:3,
inlined from ‘__rte_ring_do_enqueue_elem’ at
../lib/librte_ri
> -Original Message-
> From: Akhil Goyal
> Sent: Tuesday 21 March 2023 13:05
> To: dev@dpdk.org
> Cc: tho...@monjalon.net; david.march...@redhat.com;
> hemant.agra...@nxp.com; ano...@marvell.com; De Lara Guarch, Pablo
> ; Trahe, Fiona ;
> Doherty, Declan ; ma...@nvidia.com;
> g.si...@nx
Acked-by: Hemant Agrawal
It has been observed that mbufs of some received VLAN packets had the
VLAN tag correctly set in vlan_tci, but ol_flags were missing the
VLAN-indicating flags.
_mm256_shuffle_epi8 operates as two independent 128-bit operations,
not as a single 256-bit operation. To have the RTE_MBUF_F_RX_VLAN* flag
Hi,
> -Original Message-
> From: Harold Huang
> Sent: Sunday, March 12, 2023 4:00 AM
> To: dev@dpdk.org
> Cc: Harold Huang ; Wisam Monther
>
> Subject: [PATCH] app/flow-perf: replace RTE_BE32/16 with
> rte_cpu_to_be_32/16 for variables
>
> In DPDK, the macros RTE_BE32 or RTE_BE16 are us
Replace the deprecated VF action with the represented_port action.
Fixes: 776c119736e7 ("net/ice: remove deprecated VF flow action")
Cc: sta...@dpdk.org
Signed-off-by: Qi Zhang
---
doc/guides/nics/ice.rst | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/guides/nic
> -Original Message-
> From: Peng, Yuan
> Sent: Friday, March 24, 2023 3:55 PM
> To: Chen, LingliX ; Zhang, Qi Z
> ; dev@dpdk.org
> Subject: RE: [PATCH V1] doc: add tested Intel platforms with Intel NICs
>
>
>
> > -Original Message-
> > From: Chen, LingliX
> > Sent: Wednesda
Hi Bruce,
I think one of the loops in rte_memcpy_aligned() takes one too many rounds in
the case where the catch-up could replace the last round.
Consider e.g. n = 128:
The 64 bytes block copy will take two rounds, and the catch-up will copy the
last 64 bytes once again.
I think that the 64 b
HI,
I see all the other RTE_BE32 and RTE_BE16 are used for constant
values. I think it is not necessary to fix them:
In app/test-flow-perf/items_gen.c:
.hdr.vlan_tci = RTE_BE16(VLAN_VALUE),
.hdr.vlan_tci = RTE_BE16(0x),
ipv4_masks[ti].hdr.src_addr = RTE_BE32(0x);
.protocol = RTE_BE16
On 3/27/2023 6:31 AM, Deng, KaiwenX wrote:
>
>
>> -Original Message-
>> From: Ferruh Yigit
>> Sent: Thursday, March 23, 2023 11:39 PM
>> To: Deng, KaiwenX ; dev@dpdk.org
>> Cc: sta...@dpdk.org; Yang, Qiming ; Zhou, YidingX
>> ; Chas Williams ; Min Hu (Connor)
>> ; Wu, Jingjing ; Xing, Be
On 3/27/2023 1:31 PM, Ferruh Yigit wrote:
> On 3/27/2023 6:31 AM, Deng, KaiwenX wrote:
>>
>>
>>> -Original Message-
>>> From: Ferruh Yigit
>>> Sent: Thursday, March 23, 2023 11:39 PM
>>> To: Deng, KaiwenX ; dev@dpdk.org
>>> Cc: sta...@dpdk.org; Yang, Qiming ; Zhou, YidingX
>>> ; Chas Willi
This patch adds an operation callback which gets called every time the
library wants to call eventfd_write(). This eventfd_write() call could
result in a system call, which could potentially block the PMD thread.
The callback function can decide whether it's ok to handle the
eventfd_write() now or
Hi Eelco,
On 3/27/23 14:51, Eelco Chaudron wrote:
This patch adds an operation callback which gets called every time the
library wants to call eventfd_write(). This eventfd_write() call could
result in a system call, which could potentially block the PMD thread.
The callback function can decide
On 27 Mar 2023, at 15:21, Maxime Coquelin wrote:
> Hi Eelco,
>
> On 3/27/23 14:51, Eelco Chaudron wrote:
>> This patch adds an operation callback which gets called every time the
>> library wants to call eventfd_write(). This eventfd_write() call could
>> result in a system call, which could po
> -Original Message-
> From: Joyce Kong
> Signed-off-by: Joyce Kong
> Reviewed-by: Ruifeng Wang
Acked-by: Reshma Pattan
Replace the use of __sync__and_fetch and __sync_fetch_and_ atomics
with GCC C11 memory model __atomic builtins.
This series contributes to converging on standard atomics in 23.11 but is
kept separate as there may be sensitivity to converting from __sync to the
C11 memory model builtins.
Tyler Ret
Replace use of __sync_fetch_and_or and __sync_fetch_and_and with
__atomic_fetch_or and __atomic_fetch_and.
Signed-off-by: Tyler Retzlaff
---
drivers/crypto/ccp/ccp_dev.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/ccp/ccp_dev.c b/drivers/crypto/ccp/cc
Replace use of __sync_or_and_fetch with __atomic_fetch_or.
Signed-off-by: Tyler Retzlaff
---
drivers/bus/vmbus/vmbus_channel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/bus/vmbus/vmbus_channel.c
b/drivers/bus/vmbus/vmbus_channel.c
index 5549fd0..4d74df3 100644
Replace use of __sync_fetch_and_add and __sync_fetch_and_sub with
__atomic_fetch_add and __atomic_fetch_sub.
Signed-off-by: Tyler Retzlaff
---
lib/eal/include/generic/rte_atomic.h | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/lib/eal/inclu
On Mon, Mar 27, 2023 at 07:07:12AM +, Joyce Kong wrote:
> The following warning is observed with GCC12 compilation
> with release 20.11:
>
> In function ‘__rte_ring_enqueue_elems_64’,
> inlined from ‘__rte_ring_enqueue_elems’ at
> ../lib/librte_ring/rte_ring_elem.h:225:3,
>
The names in a patch were possibly checked with checkpatches.sh
before applying the patch, so before .mailmap file was updated.
The check is moved and translated in check-git-log.sh,
which is run only on a repository, not a detached patch file.
Fixes: e83d41f0694d ("mailmap: add list of contribut
From: Bing Zhao
> With some OFED or upstream kernel of mlx5, the port name fetched from
> "/sys/class/net/[DEV]/phys_port_name" may have a tailing "\n" as the EOL.
> The sscanf() will return the scanned items number with this EOL.
>
> In such case, the "equal to" condition is considered as fals
From: Alexander Kozyrev
> The regular CQE size can be 64 bytes or 128 bytes depending on the cache
> line size. The error CQE is always 64 bytes long.
> Only 64 bytes are dumped to the log file in case of Tx queue recovery form
> the error. Use the CQE size, not the error CQE size.
>
> Fixes: 95
Hi Eelco,
> +void
> +rte_vhost_notify_guest(int vid, uint16_t queue_id) {
> + struct virtio_net *dev = get_device(vid);
> + struct vhost_virtqueue *vq;
> +
> + if (!dev || queue_id >= VHOST_MAX_VRING)
> + return;
> +
> + vq = dev->virtqueue[queue_id];
> + if (!vq)
> From: Tyler Retzlaff [mailto:roret...@linux.microsoft.com]
> Sent: Monday, 27 March 2023 16.30
>
> Replace the use of __sync__and_fetch and __sync_fetch_and_ atomics
> with GCC C11 memory model __atomic builtins.
>
> This series contributes to converging on standard atomics in 23.11 but is
> ke
On 27 Mar 2023, at 17:16, Gowrishankar Muthukrishnan wrote:
> Hi Eelco,
>
>> +void
>> +rte_vhost_notify_guest(int vid, uint16_t queue_id) {
>> +struct virtio_net *dev = get_device(vid);
>> +struct vhost_virtqueue *vq;
>> +
>> +if (!dev || queue_id >= VHOST_MAX_VRING)
>> +
On 3/27/23 18:04, Eelco Chaudron wrote:
On 27 Mar 2023, at 17:16, Gowrishankar Muthukrishnan wrote:
Hi Eelco,
+void
+rte_vhost_notify_guest(int vid, uint16_t queue_id) {
+ struct virtio_net *dev = get_device(vid);
+ struct vhost_virtqueue *vq;
+
+ if (!dev || queue_id
Hi folks,
I don't think we discussed it specifically but what is the expectation
in relation to converting to standard atomics and compatibility of the
legacy rte_atomic APIs?
We can't really convert the inline function implementations of the
rte_atomic APIs because doing so would break compatibi
> From: Tyler Retzlaff [mailto:roret...@linux.microsoft.com]
> Sent: Monday, 27 March 2023 21.39
>
> Hi folks,
>
> I don't think we discussed it specifically but what is the expectation
> in relation to converting to standard atomics and compatibility of the
> legacy rte_atomic APIs?
>
> We can'
https://bugs.dpdk.org/show_bug.cgi?id=1200
smiller (7532ya...@gmail.com) changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
This patch set contains:
1. switch copyright from MIT to BSD-3 for GVE base code.
2. remove MIT license exception
3. add maintainers
4. update copyright holders for GVE
Junfeng Guo (2):
net/gve: switch copyright from MIT to BSD-3
net/gve: update copyright holders
.mailmap
Switch copyright from MIT to BSD-3 for GVE base code.
In the meantime, remove MIT license exception for GVE driver.
Also update the maintainers for GVE driver.
Signed-off-by: Rushil Gupta
Signed-off-by: Joshua Washington
Signed-off-by: Junfeng Guo
Signed-off-by: Jeroen de Borst
---
.mailmap
Add Google LLC as one of the copyright holders for GVE.
Signed-off-by: Rushil Gupta
Signed-off-by: Joshua Washington
Signed-off-by: Junfeng Guo
Signed-off-by: Jeroen de Borst
---
drivers/net/gve/gve_ethdev.c | 32 ++--
drivers/net/gve/gve_ethdev.h | 32
> -Original Message-
> From: Boleslav Stankevich
> Sent: Wednesday, March 22, 2023 6:23 PM
> To: dev@dpdk.org
> Cc: Boleslav Stankevich ;
> sta...@dpdk.org; Andrew Rybchenko ; Maxime
> Coquelin ; Xia, Chenbo ;
> David Marchand ; Hyong Youb Kim
> ; Harman Kalra
> Subject: [PATCH 1/2] net/v
> -Original Message-
> From: Tyler Retzlaff
> Sent: Monday, March 27, 2023 10:35 PM
> To: Joyce Kong
> Cc: reshma.pat...@intel.com; step...@networkplumber.org;
> konstantin.v.anan...@yandex.ru; dev@dpdk.org; nd ;
> sta...@dpdk.org; Ruifeng Wang
> Subject: Re: [PATCH] pdump: fix build iss
> Hi Saoirse,
>
> > Subject: [PATCH] test/crypto: fix errors for test stats testcase
> >
> > The test stats testcase was printing the same error message for multiple
> > errors
> > in the test stats testcase. This is now replaced with descriptive error
> > messages,
> > which match the cause of
> Acked-by: Hemant Agrawal
Applied to dpdk-next-crypto
Thanks.
> Hi Gowrishankar,
> > Subject: [PATCH] examples/fips_validation: fix digest in non JSON SHA MCT
> >
> > Non JSON SHA MCT tests produce incorrect digest due to a regression while
> > handling MD blocks in common for all kind of SHA, SHA2, SHA3 and SHAKE
> > algorithms. Fixing this along with some c
38 matches
Mail list logo
