On Thu, Mar 4, 2021 at 4:33 PM Van Haaren, Harry
wrote:
>
> Fix typo in Mattias' email, apologies for noise.
>
> > -Original Message-
> > From: Van Haaren, Harry
> > Sent: Wednesday, March 3, 2021 10:57 AM
> > To: dev@dpdk.org
> > Cc: david.march...@redhat.com; mattias.ronnb...@ericcson.c
The comment got it wrong. The payload length field
does not include the fixed IPv6 header size.
Fixes: 7eca7f7fd09d ("net: add missing endianness annotations")
Fixes: af75078fece3 ("first public release")
Cc: sta...@dpdk.org
Signed-off-by: Ivan Malov
Reviewed-by: Andrew Rybchenko
---
lib/librt
Updated ice recommended matching list for DPDK 21.02.
and also fixed matching kernel driver version for DPDK 20.11.
Fixes: e89aebf3b597 ("doc: update ice user guide")
Cc: sta...@dpdk.org
Signed-off-by: Qi Zhang
---
doc/guides/nics/ice.rst | 12 +++-
1 file changed, 7 insertions(+), 5 de
> -Original Message-
> From: Jerin Jacob Kollanukkaran
> Sent: Sunday, March 7, 2021 9:35 PM
> To: Ruifeng Wang ; Juraj Linkeš
> ; Luca Boccassi ;
> sta...@dpdk.org; dev@dpdk.org; tho...@monjalon.net; Ashwin Sekhar
> Thalakalath Kottilveetil ; Andrew Pinski
>
> Cc: david.march...@redhat.c
04/03/2021 18:14, Ferruh Yigit:
> On 3/1/2021 1:38 PM, Bruce Richardson wrote:
> > On Wed, Sep 30, 2020 at 12:02:40PM +0100, Ferruh Yigit wrote:
> >> Also add missing .ini feature list documentation and document some
> >> existing features including new "Multiprocess aware" feature.
> >>
> >> Signe
Hi
> -Original Message-
> From: Thomas Monjalon
> Sent: Thursday, March 4, 2021 12:46 PM
> Subject: Re: [dpdk-dev] [RFC] ethdev: add sanity packet checks
>
> 04/03/2021 11:00, Ori Kam:
> > From: Thomas Monjalon
> > > 28/02/2021 20:48, Ori Kam:
> > > > Currently, DPDK application can offl
On Mon, Mar 1, 2021 at 10:31 PM Timothy McDaniel
wrote:
>
> This patch set removes DLB V1 from DPDK 21.05.
>
> All DLB V1 customers obtain the source code for that device directly
> from Intel, and will continue to do so in the future.
>
> DLB V2 remains in DPDK, and will be supplemented with supp
On Tue, Feb 23, 2021 at 1:19 AM Timothy McDaniel
wrote:
>
> This patch updates the PMD to initialize response fields
> prior to calling into the PF layer.
>
> Coverity issue: 366187, 366186, 366184, 366166, 366159,
> 366158, 366153, 366145, 366127, 366125, 366120
> Fixes: 8bb077f44
On Thu, Feb 4, 2021 at 6:09 PM Mattias Rönnblom
wrote:
>
> On 2021-02-04 13:34, Jerin Jacob wrote:
> > On Tue, Jan 26, 2021 at 10:07 PM Mattias Rönnblom
> > wrote:
> >> Use C11-style GCC built-in functions for atomic operations.
> >>
> >> Signed-off-by: Mattias Rönnblom
> >> ---
> >> drivers/e
Hi,
> -Original Message-
> From: luca.bocca...@gmail.com
> Sent: Monday, February 22, 2021 5:09 PM
> To: sta...@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe ;
> Akhil Goyal ; Ali Alnubani ;
> benjamin.wal...@intel.com; David Christensen ;
> hariprasad.govindhara...@intel.com; Hemant Agra
> -Original Message-
> From: Ruifeng Wang
> Sent: Monday, March 1, 2021 11:10 AM
> To: Jerin Jacob Kollanukkaran ; Juraj Linkeš
> ; Luca Boccassi ;
> sta...@dpdk.org
> Cc: david.march...@redhat.com; nd ; nd
> Subject: [EXT] RE: [PATCH 20.11] config/arm: replace native machine args
>
>
On Fri, Feb 26, 2021 at 1:31 PM Mattias Rönnblom
wrote:
>
> On 2021-02-25 13:32, Jerin Jacob wrote:
> > On Fri, Feb 19, 2021 at 12:00 AM Mattias Rönnblom
> > wrote:
> >> The purpose of the event dispatcher is primarily to decouple different
> >> parts of an application (e.g., processing pipeline
The Rx metadata might use the metadata register C0 to keep the
values. The same register C0 might be used by kernel for source
vport value handling, kernel uses upper half of the register,
leaving the lower half for application usage.
In the extended metadata mode 1 (dv_xmeta_en devarg is
assigned
This patch add support for the timestamp format settings for
the receive and send queues. If the firmware version x.30.256
or above is installed and the NIC timestamps are configured
with the real-time format, the default zero values for new
added values cause the queue creation reject. The patch
q
This patch adds support for the timestamp format settings for
the receive and send queues. If the firmware version x.30.256
or above is installed and the NIC timestamps are configured
with the real-time format, the default zero values for new
added values cause the queue creation reject. The patch
This patch adds support for the timestamp format settings for
the receive and send queues. If the firmware version x.30.256
or above is installed and the NIC timestamps are configured
with the real-time format, the default zero values for new
added values cause the queue creation reject. The patch
This patch adds support for the timestamp format settings for
the queues pairs. If the firmware version x.30.256 or above
is installed and the NIC timestamps are configured with the
real-time format, the default zero values for new added values
cause the queue creation reject. The patch queries the
This patch handles the NIC supported timestamp formats via DevX.
There are two different timestamp format can be provided potentially.
The free-running is some opaque values captured from internal clock
counter clocked by some independent oscillator. The free-running
frequency is not pre-defined an
There are two different timestamp formats can be provided potentially
by mlx5 supported hardware.
The free-running format provides some opaque values captured from
internal clock counter clocked by some independent oscillator.
The free-running frequency is not pre-defined and should be queried
fro
Currently the memset() will not set a correct src ip that represent
the incremental value of the counter.
This commit will fix this and each flow will have correct IPv6.src
that it's incremental from previous flow and equal to the decimal
values.
Fixes: bf3688f1e816 ("app/flow-perf: add insertion
Take into consideration that the user may call portmask for
any run, thus the app should always check if port is needed
to collect and report or not.
Fixes: 070316d01d3e ("app/flow-perf: add multi-core rule insertion and
deletion")
Fixes: d8099d7ecbd0 ("app/flow-perf: split dump functions")
Cc: d
create_flow and create_meter are not correct names since those
are records that contain creation and deletion, which makes
them more of a record for such data.
Fixes: d8099d7ecbd0 ("app/flow-perf: split dump functions")
Cc: dongz...@nvidia.com
Signed-off-by: Wisam Jaddo
---
app/test-flow-perf/m
Current support for unique data is to compile with config.h
var as FIXED_VALUES as 0, and this is only supported on
compilation time, as a result the user may use only single
mode for each compilation.
Starting with this commit the user will have the ability to
use this feature on the fly by using
rdtsc() is x86 related, while this might fail for other archs,
so it's better to use more generic API for cycles measurement.
Signed-off-by: Wisam Jaddo
---
app/test-flow-perf/main.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/app/test-flow-perf
Wisam Jaddo (5):
app/flow-perf: start using more generic wrapper for cycles
app/flow-perf: add new option to use unique data on the fly
app/flow-perf: fix naming of CPU used structured data
app/flow-perf: fix report total stats for masked ports
app/flow-perf: fix the incremental IPv6 src
25 matches
Mail list logo
