Hi Jun,
> -Original Message-
> From: Jun Qiu
> Sent: Wednesday, July 27, 2022 4:01 PM
> To: dev@dpdk.org
> Cc: Hu, Jiayu ; sta...@dpdk.org
> Subject: [PATCH] gro: fix gro with ethernet tail padding bytes
>
> Exclude CRC fields, the minimum Ethernet packet length is 60 bytes. When
> the a
Update the example CLI scripts with the commands for code generation
and shared object library build.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/examples/ethdev.io | 27 +
examples/pipeline/examples/fib.cli| 44 +++---
Remove the tap CLI command, as the file descriptor I/O ports of the
pipeline are now configured trough the I/O specification file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 37 -
examples/pipeline/obj.c | 89 -
Rework the link CLI command for better alignment with the naming
conventions used in the pipeline I/O specification file. Use the
library linked list of devices and remove the application list.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 81 ++
Convert the CLI commands to use the pipeline name query API and remove
the linked list of pipeline objects previously maintained by the
application.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c| 268 -
exam
The pipeline I/O ports configuration is now done through the I/O
specification file, hence these CLI commands are no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 465
1 file changed, 465 d
Add CLI command for the shared object library build operation.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 157 +++-
1 file changed, 153 insertions(+), 4 deletions(-)
diff --git a/examples/pipeline/cli.c b/
The pipeline mirroring configuration is done through the I/O
specification file, so this CLI command is no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 76 -
1 file changed, 76 deletions(-)
The pipeline configuration is now done through the I/O specification
file, hence this CLI command is no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 47 -
1 file changed, 47 deletions(-)
d
Add CLI command for the pipeline code generation operation.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 61 +
1 file changed, 61 insertions(+)
diff --git a/examples/pipeline/cli.c b/examples/pipeline/cl
Previously, the pipeline build operation was done based on the
specification file (typically produced by the P4 compiler), then the C
code with optimized functions for the pipeline actions and
instructions was generated, built into a shared object library, loaded
and installed into the pipeline in
Previously, the C code generation for the pipeline was hidden under
the hood; now, we make this an explicit API operation. Besides the
functions for the pipeline actions and the pipeline instructions,
the generated C source code now includes the pipeline specification
structure required for the pip
Add specification data structure and API for the pipeline I/O ports
and related pipeline configuration such as packet mirroring.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 852 +++
lib/pipeline/rte_swx_pip
Add support to export the pipeline specification data structure to a C
source code file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 622 +++
lib/pipeline/rte_swx_pipeline_spec.h | 5 +
2 files changed, 6
Rework the specification file-based pipeline build operation to first
parse the specification file into the previously introduced pipeline
specification data structure, then use this structure to configure
and build the pipeline.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
Add specification data structure for the entire pipeline.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 21 ++
lib/pipeline/rte_swx_pipeline_spec.h | 32
2 files changed, 53 insertions(+)
Move all the pipeline object specification data structures to an
internal header file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 126 +--
lib/pipeline/rte_swx_pipeline_spec.h | 176 +++
2
Add an unique name to every pipeline. This enables the library to
maintain a list of the existing pipeline objects, which can be
queried by the application.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/obj.c | 2 +-
lib/pipeline/rte_
Update the example CLI scripts with the commands for code generation
and shared object library build.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/examples/ethdev.io | 27 +
examples/pipeline/examples/fib.cli| 44 +++---
Remove the tap CLI command, as the file descriptor I/O ports of the
pipeline are now configured trough the I/O specification file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 37 -
examples/pipeline/obj.c | 89 -
Rework the link CLI command for better alignment with the naming
conventions used in the pipeline I/O specification file. Use the
library linked list of devices and remove the application list.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 81 ++
Convert the CLI commands to use the pipeline name query API and remove
the linked list of pipeline objects previously maintained by the
application.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c| 268 -
exam
The pipeline mirroring configuration is done through the I/O
specification file, so this CLI command is no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 76 -
1 file changed, 76 deletions(-)
The pipeline I/O ports configuration is now done through the I/O
specification file, hence these CLI commands are no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 465
1 file changed, 465 d
The pipeline configuration is now done through the I/O specification
file, hence this CLI command is no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 47 -
1 file changed, 47 deletions(-)
d
Add CLI command for the shared object library build operation.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 157 +++-
1 file changed, 153 insertions(+), 4 deletions(-)
diff --git a/examples/pipeline/cli.c b/
Add CLI command for the pipeline code generation operation.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 61 +
1 file changed, 61 insertions(+)
diff --git a/examples/pipeline/cli.c b/examples/pipeline/cl
Previously, the pipeline build operation was done based on the
specification file (typically produced by the P4 compiler), then the C
code with optimized functions for the pipeline actions and
instructions was generated, built into a shared object library, loaded
and installed into the pipeline in
Previously, the C code generation for the pipeline was hidden under
the hood; now, we make this an explicit API operation. Besides the
functions for the pipeline actions and the pipeline instructions,
the generated C source code now includes the pipeline specification
structure required for the pip
Add specification data structure and API for the pipeline I/O ports
and related pipeline configuration such as packet mirroring.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 852 +++
lib/pipeline/rte_swx_pip
Add support to export the pipeline specification data structure to a C
source code file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 622 +++
lib/pipeline/rte_swx_pipeline_spec.h | 5 +
2 files changed, 6
Rework the specification file-based pipeline build operation to first
parse the specification file into the previously introduced pipeline
specification data structure, then use this structure to configure
and build the pipeline.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
Add specification data structure for the entire pipeline.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 21 ++
lib/pipeline/rte_swx_pipeline_spec.h | 32
2 files changed, 53 insertions(+)
Move all the pipeline object specification data structures to an
internal header file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 126 +--
lib/pipeline/rte_swx_pipeline_spec.h | 176 +++
2
Add an unique name to every pipeline. This enables the library to
maintain a list of the existing pipeline objects, which can be
queried by the application.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/obj.c | 2 +-
lib/pipeline/rte_
Update the example CLI scripts with the commands for code generation
and shared object library build.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/examples/ethdev.io | 27 +
examples/pipeline/examples/fib.cli| 44 +++---
Remove the tap CLI command, as the file descriptor I/O ports of the
pipeline are now configured trough the I/O specification file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 37 -
examples/pipeline/obj.c | 89 -
Rework the link CLI command for better alignment with the naming
conventions used in the pipeline I/O specification file. Use the
library linked list of devices and remove the application list.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 81 ++
Convert the CLI commands to use the pipeline name query API and remove
the linked list of pipeline objects previously maintained by the
application.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c| 268 -
exam
The pipeline mirroring configuration is done through the I/O
specification file, so this CLI command is no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 76 -
1 file changed, 76 deletions(-)
The pipeline I/O ports configuration is now done through the I/O
specification file, hence these CLI commands are no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 465
1 file changed, 465 d
The pipeline configuration is now done through the I/O specification
file, hence this CLI command is no longer needed.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 47 -
1 file changed, 47 deletions(-)
d
Add CLI command for the shared object library build operation.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 157 +++-
1 file changed, 153 insertions(+), 4 deletions(-)
diff --git a/examples/pipeline/cli.c b/
Add CLI command for the pipeline code generation operation.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/cli.c | 61 +
1 file changed, 61 insertions(+)
diff --git a/examples/pipeline/cli.c b/examples/pipeline/cl
Previously, the pipeline build operation was done based on the
specification file (typically produced by the P4 compiler), then the C
code with optimized functions for the pipeline actions and
instructions was generated, built into a shared object library, loaded
and installed into the pipeline in
Previously, the C code generation for the pipeline was hidden under
the hood; now, we make this an explicit API operation. Besides the
functions for the pipeline actions and the pipeline instructions,
the generated C source code now includes the pipeline specification
structure required for the pip
Add specification data structure and API for the pipeline I/O ports
and related pipeline configuration such as packet mirroring.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 852 +++
lib/pipeline/rte_swx_pip
Add support to export the pipeline specification data structure to a C
source code file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 622 +++
lib/pipeline/rte_swx_pipeline_spec.h | 5 +
2 files changed, 6
Rework the specification file-based pipeline build operation to first
parse the specification file into the previously introduced pipeline
specification data structure, then use this structure to configure
and build the pipeline.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
Add specification data structure for the entire pipeline.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 21 ++
lib/pipeline/rte_swx_pipeline_spec.h | 32
2 files changed, 53 insertions(+)
Move all the pipeline object specification data structures to an
internal header file.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
lib/pipeline/rte_swx_pipeline_spec.c | 126 +--
lib/pipeline/rte_swx_pipeline_spec.h | 176 +++
2
Add an unique name to every pipeline. This enables the library to
maintain a list of the existing pipeline objects, which can be
queried by the application.
Signed-off-by: Cristian Dumitrescu
Signed-off-by: Kamalakannan R.
---
examples/pipeline/obj.c | 2 +-
lib/pipeline/rte_
On Wed, 27 Jul 2022, 21:53 Honnappa Nagarahalli, <
honnappa.nagaraha...@arm.com> wrote:
>
> >
> > > From: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> > > Sent: Wednesday, 27 July 2022 19.38
> > >
> >
> > [...]
> >
> > > >
> > > > > > Yes, x86 needs 16B alignment for NT load/store
On 7/27/2022 4:36 PM, Dmitry Kozlyuk wrote:
I now understand more about_why_ you want this feature
but became less confident_what_ do you're proposing specifically.
Let me try to give a trivial example of how it would work
to make sure we're on the same page and then we can get
back to detail
I now understand more about _why_ you want this feature
but became less confident _what_ do you're proposing specifically.
>> 2022-07-26 14:33 (UTC-0400), Don Wallwork:
>>> This proposal describes a method for translating any huge page
>>> address from virtual to physical or vice versa using sim
>
> > From: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> > Sent: Wednesday, 27 July 2022 19.38
> >
>
> [...]
>
> > >
> > > > > Yes, x86 needs 16B alignment for NT load/stores But that's
> > supposed
> > > > to be arch
> > > > > specific limitation, that we probably want to hide,
On 7/27/2022 3:12 PM, Stephen Hemminger wrote:
On Wed, 27 Jul 2022 13:20:22 -0400
Don Wallwork wrote:
When drivers need to process a large number of memory blocks,
these are typically packets in the form of mbufs,
which already have IOVA attached, so there is no translation.
Does translation o
On Wed, 27 Jul 2022 13:20:22 -0400
Don Wallwork wrote:
> >
> > When drivers need to process a large number of memory blocks,
> > these are typically packets in the form of mbufs,
> > which already have IOVA attached, so there is no translation.
> > Does translation of mbuf VA to PA with the propo
On Wed, 27 Jul 2022 20:49:59 +0200
Morten Brørup wrote:
> I'm considering rte_memcpy_nt() a performance optimized variant of memcpy(),
> where the performance gain is less cache pollution. Thus, silent fallback to
> memcpy() should suffice.
Have you looked at existing Glibc code? last time I
> From: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> Sent: Wednesday, 27 July 2022 19.38
>
[...]
> >
> > > > Yes, x86 needs 16B alignment for NT load/stores But that's
> supposed
> > > to be arch
> > > > specific limitation, that we probably want to hide, no?
> >
> > Correct. How
> >
> > On Wed, Jul 27, 2022 at 10:14 AM Ruifeng Wang
> > wrote:
> > >
> > > Arm port of ipsec_mb library [1] has different header file name than
> > > the Intel ipsec_mb library. Proper header name is picked according
> > > to the architecture to get the code compile when ipsec_mb is
> > > inst
>
> > From: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> > Sent: Monday, 25 July 2022 03.18
> >
>
> [...]
>
> > > Yes, x86 needs 16B alignment for NT load/stores But that's supposed
> > to be arch
> > > specific limitation, that we probably want to hide, no?
>
> Correct. Howev
On 7/26/2022 3:59 PM, Dmitry Kozlyuk wrote:
Hi Don,
2022-07-26 14:33 (UTC-0400), Don Wallwork:
This proposal describes a method for translating any huge page
address from virtual to physical or vice versa using simple
addition or subtraction of a single fixed value. This allows
devices to effic
One of the conditions to allow LRO offload is the DV configuration.
The function incorrectly checks the DV configuration before initializing
it by the user devarg; hence, LRO cannot be allowed.
This patch moves this check to mlx5_shared_dev_ctx_args_config, where DV
configuration is initialized.
Hi Thomas,
Could you merge this change with the latest DPDK?
Thanks!
Kind Regards,
/Marcin
> -Original Message-
> From: Singh, Jasvinder
> Sent: Tuesday, July 26, 2022 3:49 PM
> To: Danilewicz, MarcinX ; dev@dpdk.org;
> Dumitrescu, Cristian
> Cc: Ajmera, Megha
> Subject: RE: [PATCH
> From: Honnappa Nagarahalli [mailto:honnappa.nagaraha...@arm.com]
> Sent: Monday, 25 July 2022 03.18
>
[...]
> > Yes, x86 needs 16B alignment for NT load/stores But that's supposed
> to be arch
> > specific limitation, that we probably want to hide, no?
Correct. However, optional hints for opt
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Wednesday, 27 July 2022 11.13
>
> On Wed, Jul 27, 2022 at 09:51:04AM +0800, fengchengwen wrote:
> > Hi Bruce,
> >
> > I think escape the string at begin (following function) seem more
> simple:
> > rte_tel_data_string
> >
This patch renames octeon end point driver from octeontx_ep to
octeon_ep to enable single unified driver to support current
OcteonTx and future Octeon PCI endpoint NICs to reflect common
driver for all Octeon based PCI endpoint NICs.
Signed-off-by: Sathesh Edara
---
MAINTAINERS
This patch set renames the net/octeontx_ep driver to net/octeon_ep
and 2nd and 3rd patches add support for basic stats and link status.
changes in v2:
Added new features in the renamed driver.
Sathesh Edara (3):
net: rename octeon ep PMD
net/octeon_ep: support basic stats
net/octeon_ep: su
Added functionality to update link speed, duplex mode and link state.
Signed-off-by: Sathesh Edara
---
doc/guides/nics/features/octeon_ep.ini | 1 +
drivers/net/octeon_ep/otx_ep_ethdev.c | 17 +
2 files changed, 18 insertions(+)
diff --git a/doc/guides/nics/features/octeon_ep.
Added functionality to fetch and reset ethdev stats.
Signed-off-by: Sathesh Edara
---
doc/guides/nics/features/octeon_ep.ini | 1 +
drivers/net/octeon_ep/otx_ep_ethdev.c | 52 ++
2 files changed, 53 insertions(+)
diff --git a/doc/guides/nics/features/octeon_ep.ini
b/d
On Wed, Jul 27, 2022 at 09:51:04AM +0800, fengchengwen wrote:
> Hi Bruce,
>
> I think escape the string at begin (following function) seem more simple:
> rte_tel_data_string
> rte_tel_data_add_array_string
> rte_tel_data_add_dict_string
>
> int
> rte_tel_data_string(struct rte_t
The ice has the feature to extract protocol fields into flex descriptor
by programming per queue. However, the dynamic field for proto_ext are
allocated by PMD, it is the responsibility of application to reserved
the field, before start DPDK.
Application with parse the offset and proto_ext name to
This patch will be updated in the future. We'll fix some issues based on
some review comments from QEMU community.
We intend to add a new vhost protocol message for virtqueue reset.
Please let me know any questions or suggestions you might have.
Thanks
在 2022/7/19 15:26, Kangjie Xu 写道:
Add V
Acked-by: Ashwin Sekhar T K
Hi Ruifeng,
Thanks for this. Initially, I had made a local hack to my IPSEC MB build script
which was creating intel-ipsec-mb.h as a softlink to ipsec-mb.h .
Later I forgot to remove this hack. So I didn't catch this.
Regards,
Ashwin Sekhar T K
> -Original Message-
> From: Ruifeng Wa
I think this delay is tolerable.
Many TCP stacks do not take special care of PUSH packets when receiving them.
All received packets with data will trigger Poll events.
The patch is simple to implement and easy to understand, similar to how the
kernel stack is handled.
From: kumaraparameshwaran
> -Original Message-
> From: David Marchand
> Sent: Wednesday, July 27, 2022 4:34 PM
> To: Ruifeng Wang
> Cc: Fan Zhang ; Pablo de Lara
> ; Wang, Yipeng1
> ; Gobriel, Sameh ;
> Bruce Richardson ; Vladimir Medvedkin
> ; Akhil Goyal ; dev
> ; Honnappa Nagarahalli ;
> nd ; tho...@monjalon.ne
On Wed, Jul 27, 2022 at 10:14 AM Ruifeng Wang wrote:
>
> Arm port of ipsec_mb library [1] has different header file name than
> the Intel ipsec_mb library. Proper header name is picked according to
> the architecture to get the code compile when ipsec_mb is installed on
> Arm platform.
>
> And the
> -Original Message-
> From: Ashwin Sekhar T K
> Sent: Thursday, June 30, 2022 11:41 PM
> To: dev@dpdk.org; Fan Zhang ; Pablo de Lara
>
> Cc: jer...@marvell.com; sk...@marvell.com; skotesh...@marvell.com;
> pbhagavat...@marvell.com; kirankum...@marvell.com;
> psathe...@marvell.com; asek..
On Wed, Jul 27, 2022 at 09:13:18AM +0800, fengchengwen wrote:
> On 2022/7/26 0:35, Bruce Richardson wrote:
> > For string values returned from telemetry, escape any values that cannot
> > normally appear in a json string. According to the json spec[1], the
> > characters than need to be handled are
2022-07-18 09:11 (UTC+0500), Fidaullah Noonari:
> In try_expand_heap() alloc_sz is calculated
> which may result in unnecessary allocation of whole huge page,
> this may cause allocation limit from system or eal
Let me suggest a rewording:
The amount of memory to allocate from the system for heap
On Tue, Jul 26, 2022 at 08:25:05PM +0200, Morten Brørup wrote:
> > From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > Sent: Monday, 25 July 2022 18.36
> > To: dev@dpdk.org
> > Cc: Bruce Richardson; Ciara Power; Keith Wiles
> > Subject: [PATCH v2 02/13] telemetry: fix escaping of invalid
Arm port of ipsec_mb library [1] has different header file name than
the Intel ipsec_mb library. Proper header name is picked according to
the architecture to get the code compile when ipsec_mb is installed on
Arm platform.
And the Arm port currently supports ZUC and SNOW3g. Call to other
algorith
The intel-ipsec-mb header is included by ipsec_mb_private header file.
Hence removed intel-ipsec-mb from files that have ipsec_mb_private
included.
Signed-off-by: Ruifeng Wang
---
drivers/crypto/ipsec_mb/pmd_aesni_gcm_priv.h | 2 --
drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h | 2 --
2 files ch
This patch set integrates Arm port of ipsec_mb library.
ZUC and SNOW3g PMDs are available on Arm platform with this integration.
This series depends on:
http://patches.dpdk.org/project/dpdk/patch/20220630154123.2565439-1-asek...@marvell.com/
Depends-on: patch-113578 ("crypto/ipsec_mb: enable supp
Exclude CRC fields, the minimum Ethernet packet
length is 60 bytes. When the actual packet length
is less than 60 bytes, padding is added to the tail.
When GRO is performed on a packet containing a padding
field, mbuf->pkt_len is the one that contains the
padding field, which leads to the error of
https://bugs.dpdk.org/show_bug.cgi?id=1044
Huang,zhimin (zhiminx.hu...@intel.com) changed:
What|Removed |Added
Resolution|--- |FIXED
Status
Moved the common crypto adapter ops to file specific to eventdev
adapters.
Signed-off-by: Shijith Thotton
---
drivers/event/cnxk/cnxk_eventdev.c | 121 ---
drivers/event/cnxk/cnxk_eventdev.h | 10 +-
drivers/event/cnxk/cnxk_eventdev_adptr.c | 115
89 matches
Mail list logo
