From: xiangxia.m@gmail.com
> From: Tonghao Zhang
>
> When setting the CONFIG_RTE_BUILD_SHARED_LIB to y, and build the mlx5
> pmd, there is a building error.
> To fix it, add RTE_IBVERBS_LINK_DLOPEN to include relative codes.
>
> mlx5_common.o: In function `mlx5_glue_init':
> drive
On 03/08, Haiyue Wang wrote:
>Use the 32bit typedef for structure 4B alignment marking.
>
>Fixes: 2b393160a480 ("eal: introduce structure markers")
>Cc: sta...@dpdk.org
>
>Signed-off-by: Haiyue Wang
>---
> lib/librte_eal/common/include/rte_common.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deleti
Use the 32bit typedef for structure 4B alignment marking.
Fixes: 2b393160a480 ("eal: introduce structure markers")
Cc: sta...@dpdk.org
Signed-off-by: Haiyue Wang
---
lib/librte_eal/common/include/rte_common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_eal/com
On 03/06, Ye Xiaolong wrote:
>Hi, Qi
>
>Thanks for the cleanup.
>
>On 03/04, Qi Zhang wrote:
>>Remove CONFIG_RTE_LIBRTE_ICE_RX_ALLOW_BULK_ALLOC with below
>>consideration:
>>
>>1. a default Rx path can always be selected by setting a proper
>> rx_free_thresh value at runtime, see
>> ice_check_r
Declaring zero-length arrays in other contexts, including as interior
members of structure objects or as non-member objects, is discouraged.
Accessing elements of zero-length arrays declared in such contexts is
undefined and may be diagnosed.[1]
Fix by using unnamed union and struct.
https://bugs
Hi Jerin,
> -Original Message-
> From: Jerin Jacob
> Sent: Friday, March 6, 2020 3:45 PM
> To: Gavin Hu
> Cc: dpdk-dev ; nd ; David Marchand
> ; tho...@monjalon.net;
> jer...@marvell.com; Ye, Xiaolong ; Honnappa
> Nagarahalli ; Ruifeng Wang
> ; Phil Yang ; Joyce Kong
> ; Steve Capper
>
Hi Kevin,
> -Original Message-
> From: Kevin Traynor
> Sent: Wednesday, March 4, 2020 8:33 PM
> To: Gavin Hu ; dev@dpdk.org
> Cc: nd ; tho...@monjalon.net;
> david.march...@redhat.com; jer...@marvell.com; Honnappa Nagarahalli
> ; Ruifeng Wang
> ; Phil Yang ;
> sta...@dpdk.org
> Subject: R
> -Original Message-
> From: Aaron Conole
> Sent: Friday, March 6, 2020 23:57
> To: Ruifeng Wang
> Cc: maicolgabr...@hotmail.com; bruce.richard...@intel.com; dev@dpdk.org;
> david.march...@redhat.com; Gavin Hu ; Honnappa
> Nagarahalli ; juraj.lin...@pantheon.tech;
> nd
> Subject: Re: [
VHOST_FEATURES has been removed in previous refactor.
Fixes: 0917f9d1f059 ("vhost: use new APIs to handle features")
Cc: sta...@dpdk.org
Signed-off-by: Xiaolong Ye
---
lib/librte_vhost/vhost.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/librte_vhost/vhost.h b/lib/librte_vhost/vhost.h
Fix the comment that's incorrect as the code evolves.
Fixes: 9470427c88e1 ("net/virtio: do not store PCI device pointer at shared
memory")
Cc: sta...@dpdk.org
Signed-off-by: Xiaolong Ye
---
drivers/net/virtio/virtio_ethdev.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --g
This series contains small fixes for virtio and vhost.
Xiaolong Ye (2):
net/virtio: fix for out of date comment
vhost: remove unused variable
drivers/net/virtio/virtio_ethdev.c | 6 +++---
lib/librte_vhost/vhost.h | 1 -
2 files changed, 3 insertions(+), 4 deletions(-)
--
2.17.1
On 3/7/20 3:51 PM, Andrew Rybchenko wrote:
On 3/6/20 4:37 PM, Jerin Jacob wrote:
On Fri, Mar 6, 2020 at 7:06 PM wrote:
From: Tonghao Zhang
The order of mempool initiation affects mempool index in the
rte_mempool_ops_table. For example, when building APPs with:
$ gcc -lrte_mempool_bucket -lr
On 3/6/20 4:37 PM, Jerin Jacob wrote:
On Fri, Mar 6, 2020 at 7:06 PM wrote:
From: Tonghao Zhang
The order of mempool initiation affects mempool index in the
rte_mempool_ops_table. For example, when building APPs with:
$ gcc -lrte_mempool_bucket -lrte_mempool_ring ...
The "bucket" mempool wi
From: Kiran Kumar K
Octeontx2 HW has support for detecting the bad L2/L3/L4 UDP lengths.
Since DPDK does not have specific error flag for this, exposing it
as bad checksum failure in mbuff:ol_flags to leverage this feature.
These errors will be propagated to the ol_flags as follows.
L2 length e
From: Hongbo Zheng
This patch adds TCP segment offload support for hns3 PMD driver.
Signed-off-by: Hongbo Zheng
Signed-off-by: Wei Hu (Xavier)
---
doc/guides/nics/features/hns3.ini| 1 +
doc/guides/nics/features/hns3_vf.ini | 1 +
doc/guides/nics/hns3.rst | 1 +
drivers/
This series are updates and fixes for hns3 PMD driver.
Chengchang Tang (3):
net/hns3: remove unnecessary restriction on setting VF's MTU
net/hns3: support promiscuous and allmulticast mode for VF
net/hns3: fix promiscuous mode for PF
Hongbo Zheng (1):
net/hns3: support TCP segment offload
From: "Wei Hu (Xavier)"
Currently, when receiving and transmitting packets based on hns3 network
engine there are probably unexpected and redundant Tx interrupts if Rx
interrupt is enabled.
The root cause as below:
Tx and Rx queues with the same number share the interrupt vector in hns3
network
From: Chengchang Tang
Currently, we only support VF device is bound to vfio_pci or igb_uio and
then driven by DPDK driver when PF is driven by kernel mode hns3 ethdev
driver, VF is not supported when PF is driven by hns3 DPDK driver.
This patch adds promiscuous and allmulticast mode support for
From: Chengchang Tang
The hns3 PF/VF devices on the same port share the hardware MTU
configuration. Currently, we send mailbox to inform hns3 PF kernel
ethdev driver to finish hardware MTU configuration in hns3 VF PMD
driver, there is no need to stop the port for hns3 VF device, and
the MTU value
From: Chengchang Tang
Currently, when promiscuous mode is enabled, it is just allowed to accept
all the unicast and broadcast packets in hns3 PF PMD driver. It should
also be able to receive multicast packets.
Fixes: 19a3ca4c99cf ("net/hns3: add start/stop and configure operations")
Cc: sta...@d
20 matches
Mail list logo
