Hi,
-Original Message-
From: Xu, Rosen
Sent: Friday, May 24, 2019 11:07 AM
To: Wei, Dan ; dev@dpdk.org
Cc: Yigit, Ferruh ; Chen, Santos
; sta...@dpdk.org
Subject: RE: [DPDK] net/ipn3ke: modifications on AFU configurations
Hi,
> > -Original Message-
> > From: Wei, Dan
> > Sent:
Attendees: (present)
Cathal
Pallavi
Bruce
Thomas tho...@monjalon.net
Adham Masarwah
Eilon Greenstein
Yohad Tor
Tal Shnaiderman
Ranjit
Anan Saif ;
Rani Sharoni ;
Raslan rasl...@mellanox.com;
Harini harini.ramakrish...@microsoft.com;
Omar Cardona ;
Jeff jeffrey.tip...@microsoft.com;
Khoa k.
On DV/DR flow engine, MLX5 can match on ICMP/ICMP6's code and type field
via FLEX Parser, which can be enabled by config FW using FLEX Parser
profile 2:
mlxconfig -d -y set FLEX_PARSER_PROFILE_ENABLE=2
Signed-off-by: Xiaoyu Min
---
doc/guides/nics/mlx5.rst| 15
drivers/net/mlx5/m
Enabled IP-in-IP tunnel type support on DV/DR flow engine.
This includes the following combination:
- IPv4 over IPv4
- IPv4 over IPv6
- IPv6 over IPv4
- IPv6 over IPv6
MLX5 NIC supports IP-in-IP tunnel via FLEX Parser so
need to make sure fw using FLEX Paser profile 0.
mlxconfig -d -y set
Bruce Richardson writes:
> On Mon, May 27, 2019 at 04:13:53PM +0200, David Marchand wrote:
>>Hello,
>>On Wed, Apr 10, 2019 at 3:45 PM Bruce Richardson
>><[1]bruce.richard...@intel.com> wrote:
>>
>> Weak functions don't work well with static library builds as the
>> linker
>
Apologies for the confusion.
Regards,
Lance
On Mon, May 27, 2019 at 11:24 AM Ferruh Yigit wrote:
>
> On 5/27/2019 10:36 AM, Ferruh Yigit wrote:
> > On 5/24/2019 3:49 PM, Lance Richardson wrote:
> >> To allow sharing of tx_bds_in_hw() and bnxt_tx_avail() between
> >> vector-mode and non-vecto
Add optional ability to fragment packet bigger then mtu,
and reassemble fragmented packet.
To minimize possible performance effect, reassembly is
implemented as RX callback.
To support these features ipsec-secgw relies on librte_ipsec ability
to handle multi-segment packets.
Also when reassemble/fr
Enhance test scripts to support fragmentation/reassemble functionality.
Signed-off-by: Konstantin Ananyev
---
examples/ipsec-secgw/test/common_defs.sh | 18 +++---
examples/ipsec-secgw/test/data_rxtx.sh | 18 ++
examples/ipsec-secgw/test/linux_test4.sh | 17
for packets smaller then 64B some NICs reports pkt_len=64B.
As ipsec-secgw (and librte_ipsec) relies on pkt_len value to determine
payload length, that causes problems for small packets.
To fix the issue, check that pkt_len matches values in IPv4/IPv6 header
and re-adjust pkt_len if necessary.
Fix
Add into ipsec-secgw ability to fragment packet bigger then mtu,
and reassemble fragmented packet.
To support these features ipsec-secgw relies on librte_ipsec ability
to handle multi-segment packets.
Also when reassemble/fragmentation support is enabled, attached
crypto devices have to support 'In
Add support for packets that consist of multiple segments.
Take into account that trailer bytes (padding, ESP tail, ICV)
can spawn across multiple segments.
Signed-off-by: Konstantin Ananyev
---
lib/librte_ipsec/esp_inb.c | 148 -
lib/librte_ipsec/misc.h|
> -Original Message-
> From: Dybkowski, AdamX
> Sent: Tuesday, May 21, 2019 4:10 PM
> To: dev@dpdk.org; Trahe, Fiona ; Jozwiak, TomaszX
> ; sta...@dpdk.org
> Subject: [PATCH] compress/qat: fixed overflow status return from qat pmd
>
> This patch fixes fail status returned from compressi
The rte_eth_dev_close() function now handles freeing resources for
devices (e.g., mac_addrs). To conform with the new close() behaviour we
are asserting the RTE_ETH_DEV_CLOSE_REMOVE flag so that
rte_eth_dev_close() releases all device level dynamic memory.
Second level memory allocated to each in
https://bugs.dpdk.org/show_bug.cgi?id=285
Bug ID: 285
Summary: rte_table unit test crashes in ipv6
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: major
Prior
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ashijeet Acharya
> Sent: Friday, May 24, 2019 2:30 AM
> To: dev@dpdk.org
> Cc: Lu, Wenzhuo ; Ananyev, Konstantin
>
> Subject: [dpdk-dev] [PATCH] net/ixgbe/base: wait for link after copper MAC
> setup
>
> After
> -Original Message-
> From: Yigit, Ferruh
> Sent: Friday, May 24, 2019 6:53 AM
> To: Xing, Beilei ; Zhang, Qi Z
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: allow VF to configure pctype
> mapping
>
> On 5/23/2019 2:37 AM, Beilei Xing wrote:
> > This patch allows VF
On 5/20/2019 6:48 PM, Yong Wang wrote:
>
> -Original Message-
> From: Yogev Chaimovich
> Date: Thursday, May 16, 2019 at 12:10 AM
> To: Yong Wang
> Cc: "dev@dpdk.org" , Yogev Chaimovich
> , "sta...@dpdk.org"
> Subject: [PATCH] net/vmxnet3: uninitialized variable fix
>
> Coverity
On 5/15/2019 7:08 PM, Ajit Khaparde wrote:
> This patchset brings in few fixes and some changes tuning
> the Tx datapath performance in bnxt PMD.
> Please apply.
>
> Ajit Khaparde (4):
> net/bnxt: fix an issue seen with TSO
> net/bnxt: add support to update ipid
> net/bnxt: check for some er
Since we now always use _FILE_OFFSET_BITS=64 flag when building
DPDK, we can remove the Makefile and C-file #defines setting it
individually for parts of the build.
Signed-off-by: Bruce Richardson
---
examples/vhost_crypto/meson.build | 1 -
examples/vhost_scsi/meson.build | 1 -
l
By default on 32-bit systems, file offsets are given as 32-bit values
which prevents support for large files. While this is unlikely to be
a problem, enabling large file support globally makes "make" and
"meson" builds consistent, since meson always enables large file
support, and without this chan
>From comment in the build config for the make build-system:
"NFP PMD is not supported on 32-bit"
Therefore disable NFP for 32-bit meson builds as well as for 32-bit
make ones.
Signed-off-by: Bruce Richardson
---
drivers/net/nfp/meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-
This set fixes some issues seen on the automated CI system with building
on 32-bit Linux distro's using meson and ninja. The fixes are to disable
unsupported parts of the build, and switch the 32-bit builds to always
having large file support, so that make and meson are consistent in that
regard.
On 5/27/2019 2:46 PM, Allain Legacy wrote:
> The rte_eth_dev_close() function now handles freeing resources for
> devices (e.g., mac_addrs). There is no change in behaviour for AVP
> devices since they do not currently free their dynamic memory; which was
> a bug. To conform with the new close()
> -Original Message-
> From: Daly, Lee
> Sent: Tuesday, May 21, 2019 4:08 PM
> To: Stephen Hemminger
> Cc: dev@dpdk.org; Trahe, Fiona
> Subject: RE: [PATCH] compress/isal: fix use after free
>
> Hi Stephen,
> Thanks for the patch.
>
> > -Original Message-
> > From: Stephen He
On Mon, May 27, 2019 at 04:13:53PM +0200, David Marchand wrote:
>Hello,
>On Wed, Apr 10, 2019 at 3:45 PM Bruce Richardson
><[1]bruce.richard...@intel.com> wrote:
>
> Weak functions don't work well with static library builds as the
> linker
> always picks the first versio
On 5/27/2019 10:36 AM, Ferruh Yigit wrote:
> On 5/24/2019 3:49 PM, Lance Richardson wrote:
>> To allow sharing of tx_bds_in_hw() and bnxt_tx_avail() between
>> vector-mode and non-vector transmit functions, move these functions
>> into bnxt_txr.h.
>>
>> Signed-off-by: Lance Richardson
>> Reviewed-
On 4/11/2019 12:00 PM, Cian Ferriter wrote:
> It can be useful to use pcap files for some rudimental performance
> testing. This patch enables this functionality in the pcap driver.
>
> At a high level, this works by creaing a ring of sufficient size to
> store the packets in the pcap file passed
On Mon, 27 May 2019 10:31:22 +0200
Thomas Monjalon wrote:
> 25/05/2019 00:06, Stephen Hemminger:
> > On Fri, 24 May 2019 19:32:14 +0200
> > Thomas Monjalon wrote:
> > > 24/05/2019 19:11, Stephen Hemminger:
> > > > On Fri, 24 May 2019 19:05:20 +0200
> > > > Thomas Monjalon wrote:
> > > >
Hello,
On Wed, Apr 10, 2019 at 3:45 PM Bruce Richardson
wrote:
> Weak functions don't work well with static library builds as the linker
> always picks the first version of a function irrespective of whether it is
> weak or not. The solution to this is to use the "whole-archive" flag when
> link
On Mon, May 20, 2019 at 07:35:12PM +0300, lir...@marvell.com wrote:
> From: Liron Himi
>
> Alan is no longer involved in PMDs maintenance hence
> update the list.
> Also append new active maintainer to the list.
>
> Signed-off-by: Liron Himi
> ---
> MAINTAINERS | 4 +---
> 1 file changed, 1 inse
On Wed, May 22, 2019 at 11:44:46AM +0200, Thierry Herbelot wrote:
> Inverted letters.
>
> Fixes: 8a61c83af2fae ('crypto/mrvl: add mrvl crypto driver')
> Signed-off-by: Thierry Herbelot
> ---
> drivers/crypto/mvsam/rte_mrvl_pmd_ops.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
The rte_eth_dev_close() function now handles freeing resources for
devices (e.g., mac_addrs). There is no change in behaviour for AVP
devices since they do not currently free their dynamic memory; which was
a bug. To conform with the new close() behaviour we are asserting the
RTE_ETH_DEV_CLOSE_RE
Hello Dharmik,
On Wed, May 22, 2019 at 9:38 PM Dharmik Thakkar
wrote:
> > On May 22, 2019, at 12:17 PM, David Marchand
> wrote:
> > On Wed, May 22, 2019 at 6:27 PM Dharmik Thakkar
> wrote:
> > > @@ -738,10 +736,9 @@ struct {
> > > rte_eal_remote_launch(test_rwc_re
> -Original Message-
> From: Xing, Beilei
> Sent: Thursday, May 23, 2019 5:28 PM
> To: Zhang, Qi Z
> Cc: dev@dpdk.org
> Subject: [PATCH] net/ixgbe: enable new device
>
> This patch enables new device, the device id is 0x15B0.
>
> Signed-off-by: Beilei Xing
Acked-by: Qi Zhang
Appli
On Fri, May 24, 2019 at 09:04:04AM -0700, David Wilder wrote:
> Setting RTE_MAX_LCORE to reflect the largest available configuration.
> Adding defines for missing RTE_MACHINE_CPUFLAGs.
>
> Signed-off-by: David Wilder
> ---
> config/ppc_64/meson.build | 4 +++-
> 1 file changed, 3 insertions(+),
On 5/24/2019 3:49 PM, Lance Richardson wrote:
> To allow sharing of tx_bds_in_hw() and bnxt_tx_avail() between
> vector-mode and non-vector transmit functions, move these functions
> into bnxt_txr.h.
>
> Signed-off-by: Lance Richardson
> Reviewed-by: Ajit Khaparde
> Reviewed-by: Maxime Coquelin
> -Original Message-
> From: Aaron Conole
> Sent: Friday, May 24, 2019 7:03 PM
> To: Jerin Jacob Kollanukkaran
> Cc: dev@dpdk.org; tho...@monjalon.net; Pavan Nikhilesh Bhagavatula
> ; Olivier Matz ; Vamsi
> Krishna Attunuru
> Subject: Re: [dpdk-dev] [PATCH v1 25/27] mempool/octeontx2: ad
Hi Akhil,
> Subject: RE: [PATCH v4 1/2] examples/ipsec-secgw: fix 1st packet dropped for
> inline crypto
>
>
>
> > > > > > > > Subject: RE: [PATCH v4 1/2] examples/ipsec-secgw: fix 1st
> > > > > > > > packet
> > > > dropped
> > > > > > for
> > > > > > > > inline crypto
> > > > > > > >
> > > >
Configuring buffer size based following parameters:
- max-pkt-len
- max supported segments per MTU
Buffer size are configured as given below:
- If platform supports infinite segments per packet then default
buffer size is used.
- If platform supports nb_mtu_seg_max segments then buffer size
is
rte_eth_dev_info structure exposes, nb_seg_max & nb_mtu_seg_max to provide
maximum number of segments supported by the platform but API does not provide
any default value as well as no show case of above mentioned fields while
creating mbuf pool.
Also in absence of this, there may be a gap bewteen
rte_eth_dev_info structure exposes, nb_seg_max & nb_mtu_seg_max
to provide maximum number of supported segments for a given platform.
Defining UINT16_MAX as default value of above mentioned variables to
expose support of infinite/maximum segments.
Based on above values, application can decide bes
25/05/2019 00:06, Stephen Hemminger:
> On Fri, 24 May 2019 19:32:14 +0200
> Thomas Monjalon wrote:
> > 24/05/2019 19:11, Stephen Hemminger:
> > > On Fri, 24 May 2019 19:05:20 +0200
> > > Thomas Monjalon wrote:
> > >
> > > > > > > device drivers on Hyper-V/Azure. If the build system supported
42 matches
Mail list logo
