From: Shiri Kuzin
Add a new PMD for Mellanox devices- crypto PMD.
The crypto PMD will be supported starting Mellanox ConnectX6 and
BlueField2.
The crypto PMD will add the support of encryption and decryption using
the AES-XTS symmetric algorithm.
The crypto PMD requires rdma-core and uses mlx5
When parsing the virtio net header and packet header for dequeue offload,
we need to perform sanity check on the packet header to ensure:
- No out-of-boundary memory access.
- The packet header and virtio_net header are valid and aligned.
Fixes: d0cf91303d73 ("vhost: add Tx offload capabilitie
Hi Huawei,
> -Original Message-
> From: dev On Behalf Of ???()
> Sent: Thursday, March 11, 2021 01:37
> To: david.march...@redhat.com; maxime.coque...@redhat.com; Yigit, Ferruh
>
> Cc: dev@dpdk.org; Burakov, Anatoly ;
> xuemi...@nvidia.com; gr...@u256.net;
> 谢华伟(此时此刻）
> Subject: [
On Thu, Mar 11, 2021 at 12:01 AM Honnappa Nagarahalli
wrote:
>
> Hello,
> Performance of L3fwd example application is one of the key benchmarks
> in DPDK. However, the application does not have many debugging statistics to
> understand the performance issues. We have added L3fwd as anoth
From: Dapeng Yu
A global ethernet port configuration is assigned to local variable
because in this way the local variable may be updated as required. But
this local variable is not used as input of rte_eth_dev_configure() in
original implementation, and cause that fast mbuf free feature cannot
be
Hi,
BRs,
Xiao
> -Original Message-
> From: Thomas Monjalon
> Sent: Wednesday, March 10, 2021 10:01 PM
> To: dev@dpdk.org
> Cc: Griffin, John ; Trahe, Fiona
> ; Jain, Deepak K ; Ajit
> Khaparde ; Raveendra Padasalagi
> ; Vikas Gupta
> ; Xu, Rosen ; Zhang,
> Tianfei ; Richardson, Bruce
> ;
Hi,
> -Original Message-
> From: Thomas Monjalon
> Sent: Wednesday, March 10, 2021 22:01
> To: dev@dpdk.org
> Cc: Griffin, John ; Trahe, Fiona
> ; Jain, Deepak K ; Ajit
> Khaparde ; Raveendra Padasalagi
> ; Vikas Gupta
> ; Xu, Rosen ; Zhang,
> Tianfei ; Richardson, Bruce
> ; Nipun Gupta ;
From: Lijun Ou
This patch adds multi-process support for testpmd.
The test cmd example as follows:
the primary cmd:
./dpdk-testpmd -a xxx --proc-type=auto -l 0-1 -- -i \
--rxq=4 --txq=4 --num-procs=2 --proc-id=0
the secondary cmd:
./dpdk-testpmd -a xxx --proc-type=auto -l 2-3 -- -i \
--rxq=4 --t
Hi Jan,
Sorry for late response,
First rule is invalid, port only works on FDB domain so need 'transfer' here;
Second rule should be ok, could you please check if the port 1 was enabled on
you dpdk application?
Thanks.
Jonny
> -Original Message-
> From: Jan Viktorin
> Sent: Monday,
From: Kalesh AP
On Thor, Rx timestamp is present in the Rx completion record.
Only 32 bits of the timestamp is present in the completion.
The driver needs to periodically poll the current 48 bit
free running timer using the HWRM_PORT_TS_QUERY command.
It can combine the upper 16 bits from the HWR
From: Kalesh AP
During some fatal firmware error conditions, the PCI config space
register 0x2e which normally contains the subsystem ID will become
0x. This register will revert back to the normal value after
the chip has completed core reset. If we detect this condition,
we can poll this co
From: Kalesh AP
This is a new async message that the firmware can send to check if it
can communicate with the driver. This is an added error detection
scheme that firmware can use if it suspects errors in the PCIe
interface. When the driver receives this async message, it will reply
back echoing
From: Kalesh AP
Moved fw readiness check to a new routine bnxt_check_fw_ready().
During error recovery, driver needs to wait for fw readiness.
For that, it uses bnxt_hwrm_ver_get() function now and that
function does parsing of the VER_GET response as well.
Added a new lightweight function bnxt
From: Venkat Duvvuru
Update queues per VNIC in single queue mode.
bp->rx_num_qs_per_vnic is not initialized in the single queue mode.
As a result of this when an interface is reconfigured to single
queue mode from an existing multiqueue mode, bp->rx_num_qs_per_vnic
is not updated to the value of
From: Kalesh AP
1. Used port id in async event logs.
2. Added a debug log in bnxt_hwrm_func_driver_unregister().
Signed-off-by: Kalesh AP
Reviewed-by: Somnath Kotur
Reviewed-by: Ajit Khaparde
---
drivers/net/bnxt/bnxt_cpr.c | 14 +-
drivers/net/bnxt/bnxt_hwrm.c | 2 ++
2 files
Update HWRM headers to version 1.10.2.15
which updates the backing store API for additional TQM rings.
Add support for 9th TQM ring using latest firmware interface.
Also make sure that we set only necessary bits in the enables
field in backing store request.
Signed-off-by: Ajit Khaparde
Reviewed
From: Kalesh AP
PMD should not set any flags to receive RoCE traffic while
configuring the vnic. Since the PMD does not support RoCE
some of the flags and code is unused. Clean it up.
Fixes: b7778e8a1c00 ("net/bnxt: refactor to properly allocate resources for
PF/VF")
Cc: sta...@dpdk.org
Signed
From: Kalesh AP
Removed an unnecessary extra blank line.
Signed-off-by: Kalesh AP
Reviewed-by: Somnath Kotur
---
drivers/net/bnxt/bnxt_hwrm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/bnxt/bnxt_hwrm.c b/drivers/net/bnxt/bnxt_hwrm.c
index 5366fe72ca..e11502c706 100644
---
From: Kalesh AP
remove HWRM_SEQ_ID_INVALID macro.
Fixes: 804e746c7b73 ("net/bnxt: add hardware resource manager init code")
Cc: sta...@dpdk.org
Signed-off-by: Kalesh AP
Reviewed-by: Somnath Kotur
Reviewed-by: Ajit Khaparde
---
drivers/net/bnxt/bnxt_hwrm.h | 1 -
1 file changed, 1 deletion(-
This patch-set enables building the Intel ice PMD on Windows.
v2 changes:
- Updated patch#1 title to reflect the iavf base code support
- Added cflag '-fno-asynchronous-unwind-tables' to base driver
- Updated doc patch with the DDP documentation and
integrated it
- Add Intel ice PMD support on Windows.
- Remove #include sys/ioctl header file as it is not needed.
- Replace x86intrin.h with rte_vect.h to avoid __m_prefetchw conflicting
types.
- Replace POSIX usleep() API with rte API.
- Add a new macro for the access() API as the original function
has been de
Update word list with VNIC and Thor to catch errors in patch title.
Suggested-by: Ferruh Yigit
Signed-off-by: Ajit Khaparde
---
devtools/words-case.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/devtools/words-case.txt b/devtools/words-case.txt
index 38084ec883..a0ff8eb5b9 100644
---
This patchset contain bnxt bug fixes and enhancements.
Please apply.
v1->v2:
- Updated word list as per recommendation to include VNIC, Thor.
- Fixed checkpatch errors pointed in 2/11.
- Updated release notes to indicate HWRM API version change.
- Check and addressed warnings reported by chec
Enable IAVF driver to build on Windows as it is required
to build ice PMD.
Disable all other drivers from common directory.
This patch also includes fix for a macro redefinition warning
in the IAVF driver.
Signed-off-by: Pallavi Kadam
Reviewed-by: Ranjit Menon
---
drivers/common/cpt/meson.build
Disable loading of external DDP package as it is not
supported on Windows.
Signed-off-by: Pallavi Kadam
Reviewed-by: Ranjit Menon
---
drivers/net/ice/ice_ethdev.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/net/ice/ice_ethdev.c b/drivers/net/ice/ice_ethdev.c
index d22bc92f
Windows socket headers define `s_addr`, `min`, and `max` macros which
break structure definitions containing fields with one of these names.
Undefining those macros would break some consumers as well.
Example 1:
#include
#include
struct in_addr addr;
/* addr.s_addr = 0; ERRO
It is clear from the change that introduced the rte_bsf64 inline
function and an evaluation of usage that the initial revision was
intended to return uint32_t and not int.
It is proposed the return type of int be changed to uint32_t.
-static inline int
+static inline uint32_t
rte_bsf64(uint64_t
On Wed, Mar 10, 2021 at 10:49:42AM -0800, Stephen Hemminger wrote:
> On Tue, 9 Mar 2021 22:41:06 -0800
> Tyler Retzlaff wrote:
>
> > based on the original commit and the usage of rte_bsf64 it appears the
> > function should always have returned uint32_t instead of int which is
> > consistent wit
On 3/10/2021 9:53 PM, Ed Czeck wrote:
On Wed, Mar 10, 2021 at 11:44 AM Ferruh Yigit wrote:
On 3/10/2021 3:02 PM, Ed Czeck wrote:
On Tue, Mar 9, 2021 at 12:36 PM Ferruh Yigit wrote:
On 3/9/2021 4:08 PM, Ed Czeck wrote:
In this commit we generalize the movement of user-specified
meta data b
Signed-off-by: Ferruh Yigit
---
v2:
* there won't be a new driver for dlb2.5
* reword thash library support
---
content/roadmap/_index.md | 10 ++
1 file changed, 10 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index c6a67a986876..f97818266765 100644
-
> -Original Message-
> From: Wisam Monther
> Sent: Wednesday, March 10, 2021 8:56
> To: arybche...@solarflare.com; NBU-Contact-Thomas Monjalon
> ; Alexander Kozyrev ;
> Raslan Darawsheh ; dev@dpdk.org
> Subject: [PATCH v3 0/7] Enhancements and fixes for flow-perf
>
> --
> v2:
> * Add
On Wed, Mar 10, 2021 at 11:44 AM Ferruh Yigit wrote:
>
> On 3/10/2021 3:02 PM, Ed Czeck wrote:
> > On Tue, Mar 9, 2021 at 12:36 PM Ferruh Yigit wrote:
> >>
> >> On 3/9/2021 4:08 PM, Ed Czeck wrote:
> >>> In this commit we generalize the movement of user-specified
> >>> meta data between mbufs and
On 3/10/2021 8:20 PM, David Marchand wrote:
On Wed, Mar 10, 2021 at 7:40 PM Ferruh Yigit wrote:
@@ -41,6 +50,7 @@ This list is obviously neither complete nor guaranteed.
- event vector support to reduce scheduler overhead and to improve performance
- event vector support in SW Rx eventde
On Wed, Mar 10, 2021 at 09:52:58PM +0100, Thomas Monjalon wrote:
> 12/02/2021 20:09, Tyler Retzlaff:
> > Recently installation of driver headers and export of functions was
> > pulled back from being public to private
> >
12/02/2021 20:09, Tyler Retzlaff:
> Recently installation of driver headers and export of functions was
> pulled back from being public to private
> (commit
> df96fd0d73955bdc7ca3909e772ff2ad90
On Wed, Mar 10, 2021 at 7:40 PM Ferruh Yigit wrote:
> @@ -41,6 +50,7 @@ This list is obviously neither complete nor guaranteed.
>
> - event vector support to reduce scheduler overhead and to improve
> performance
> - event vector support in SW Rx eventdev adapter
> +- new dynamic load balance
Tested-by: Kathleen Capella
> -Original Message-
> From: dev On Behalf Of Feifei Wang
> Sent: Tuesday, March 9, 2021 9:40 PM
> To: jer...@marvell.com; Ruifeng Wang ; Beilei Xing
> ; Jeff Guo ; Bruce Richardson
> ; Jianbo Liu
> Cc: dev@dpdk.org; nd ; Feifei Wang ;
> sta...@dpdk.org
> Sub
On Wed, Mar 10, 2021 at 02:48:55PM +0200, Tal Shnaiderman wrote:
> add error number reporting to rte_errno in all
> functions in the rte_thread_tls_* API.
>
> Suggested-by: Anatoly Burakov
> Signed-off-by: Tal Shnaiderman
> ---
> lib/librte_eal/include/rte_thread.h | 14 +++---
> lib/li
> > > > >
> > > > > > > > > >
> > > > > > > > > > On Tue, Mar 09, 2021 at 08:58:39AM +, Juraj Linkeš
> wrote:
> > > > > > > > > > > Honnappa, Thomas, Bruce, Jerin, you've comments in the
> past.
> > > > > > > > > > > Do you have
> > > > > > > > > > any further input?
> > > > > > > > > > >
> >
On Tue, 9 Mar 2021 22:41:06 -0800
Tyler Retzlaff wrote:
> based on the original commit and the usage of rte_bsf64 it appears the
> function should always have returned uint32_t instead of int which is
> consistent with the cast introduced in the return statement.
>
> Fixes: 4e261f551986 ("eal:
Signed-off-by: Ferruh Yigit
---
content/roadmap/_index.md | 10 ++
1 file changed, 10 insertions(+)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index c6a67a986876..9789e132c57e 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -18,6 +18,8 @@
On Wed, 10 Mar 2021 17:27:17 +
Bruce Richardson wrote:
> On Wed, Mar 10, 2021 at 09:21:37AM -0800, Stephen Hemminger wrote:
> > There can be cases such as containers or other runtime environments
> > where DPDK may not be able to access the default runtime path.
> > This patch introduces DPDK
can i use
./sources/dpdk-18.11/drivers/net/vmxnet3/vmxnet3_ethdev.c:1422:
rte_log_set_level(vmxnet3_logtype_driver, RTE_LOG_WARNING);
after EAL driver routine completes ( pci_common.c, etc) its initialization
? Please let me know where do i need to call rte_log_set_level() in EAL
driver init co
Hello,
Performance of L3fwd example application is one of the key benchmarks
in DPDK. However, the application does not have many debugging statistics to
understand the performance issues. We have added L3fwd as another mode/stream
to testpmd which provides enough statistics at various l
On 3/9/2021 10:41 PM, Tyler Retzlaff wrote:
based on the original commit and the usage of rte_bsf64 it appears the
function should always have returned uint32_t instead of int which is
consistent with the cast introduced in the return statement.
Fixes: 4e261f551986 ("eal: add 64-bit bsf and 32-b
On Wed, 10 Mar 2021 23:49:17 +0530
Shanmugasundaram M wrote:
> THanks Steven for the quick response. I want to enable EAL module
> (complete logging at debug level ) only during bootup of fastpath. Once
> bootup is done, i want to move this module log-level to default/ original.
> Currently I'm
THanks Steven for the quick response. I want to enable EAL module
(complete logging at debug level ) only during bootup of fastpath. Once
bootup is done, i want to move this module log-level to default/ original.
Currently I'm using --log-level='.*',8 along with
./sources/fp/common/fp-var.h
On 3/10/2021 7:48 AM, Ciara Loftus wrote:
Single-core performance of AF_XDP at high loads can be poor because
a heavily loaded NAPI context will never enter or allow for busy-polling.
1C testpmd rxonly (both IRQs and PMD on core 0):
./dpdk-testpmd -l 0-1 --vdev=net_af_xdp0,iface=eth0 --main-lcor
Including Declan and Arek.
Hi Linfeng,
Thanks for raising this. I passed it on yesterday to the team, they are
investigating.
Regards,
Fiona
From: Linfeng Li
Sent: Wednesday, March 10, 2021 5:38 PM
To: dev@dpdk.org
Cc: Griffin, John ; Trahe, Fiona
; Jain, Deepak K ; Steve Rizor
; Emil Meng
With I/O BAR, we get PIO(port-mapped I/O) address.
With MMIO(memory-mapped I/O) BAR, we get mapped virtual address.
We distinguish PIO and MMIO by their address range like how kernel does,
i.e, address below 64K is PIO.
ioread/write8/16/32 is provided to access PIO/MMIO.
By the way, for virtio on a
virtio PMD assumes legacy device only supports PIO(port-mapped) BAR
resource. This is wrong. As we need to create lots of devices, adn PIO
resource on x86 is very limited, we expose MMIO(memory-mapped I/O) BAR.
Kernel supports both PIO and MMIO BAR for legacy virtio-pci device, and
for all other p
Currently virtio PMD assumes legacy device uses PIO bar.
There are three ways to get PIO(PortIO) address for virtio legacy device.
1) under igb_uio, get PIO address from uio/uio# sysfs attribute, for
instance: /sys/bus/pci/devices/:00:09.0/uio/uio0/portio/port0/start
2) under uio_pci_ge
On Wed, Mar 10, 2021 at 09:21:37AM -0800, Stephen Hemminger wrote:
> There can be cases such as containers or other runtime environments
> where DPDK may not be able to access the default runtime path.
> This patch introduces DPDK_RUNTIME_DIR as an environment variable
> to allow controlling and ov
The rte_telemetry_init() function is for EAL use only, so can be moved to
the internal header rather than being in the public one.
Signed-off-by: Bruce Richardson
---
lib/librte_eal/freebsd/eal.c | 2 +-
lib/librte_eal/linux/eal.c| 2 +-
lib/librte_telemetry/rte_te
The header file containing the legacy telemetry function prototypes was all
internal-only, so we rename the file to be an internal-only one to make it
clearer it's not for installation.
Signed-off-by: Bruce Richardson
---
lib/librte_metrics/rte_metrics_telemetry.c | 2 +-
lib/li
The function for registration of callbacks for legacy telemetry was
documented as internal-only in the API documents, but marked as
experimental in the version.map file. Since this is an internal-only
function, for consistency we update the version mapping to have it as
internal.
Signed-off-by: Br
Rather than passing back an error string to the caller, take as input the
rte_log function to use, and just use regular logging.
Signed-off-by: Bruce Richardson
---
lib/librte_eal/freebsd/eal.c | 10 ++--
lib/librte_eal/linux/eal.c | 10 ++--
lib/librte_telemetry/rte_telemetry.
This set adds support for using the regular rte_log functions from the telemetry
library; avoiding circular dependencies by having EAL register the telemetry
library itself and then passing the required handles to that library as part of
the telemetry_init call.
Beyond this change, the other three
There can be cases such as containers or other runtime environments
where DPDK may not be able to access the default runtime path.
This patch introduces DPDK_RUNTIME_DIR as an environment variable
to allow controlling and overriding the path.
The example we have is DPDK application running in an u
https://bugs.dpdk.org/show_bug.cgi?id=652
Bug ID: 652
Summary: Link detection failing when DPDK takes control of
XXV710 NIC
Product: DPDK
Version: 18.05
Hardware: All
OS: All
Status: UNCONFIRMED
> -Original Message-
> From: Dharmappa, Savinay
> Sent: Tuesday, March 9, 2021 4:10 PM
> To: Singh, Jasvinder ; Dumitrescu, Cristian
> ; dev@dpdk.org
> Cc: Dharmappa, Savinay
> Subject: [PATCH v2] sched : Initialize tc ov watermark.
>
> tc ov watermark is initialized with computed val
On Wed, Mar 10, 2021 at 02:35:47PM +0100, Thomas Monjalon wrote:
> 10/03/2021 14:26, Bruce Richardson:
> > On Wed, Mar 10, 2021 at 01:33:20PM +0100, Thomas Monjalon wrote:
> > > 10/03/2021 13:19, Bruce Richardson:
> > > > On Wed, Mar 10, 2021 at 12:31:10AM +0100, Thomas Monjalon wrote:
> > > > > Th
On 3/10/2021 3:02 PM, Ed Czeck wrote:
On Tue, Mar 9, 2021 at 12:36 PM Ferruh Yigit wrote:
On 3/9/2021 4:08 PM, Ed Czeck wrote:
In this commit we generalize the movement of user-specified
meta data between mbufs and FPGA AXIS tuser fields using
user-defined hook functions.
- Previous use of P
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Wednesday, March 10, 2021 2:36 PM
>
> 10/03/2021 14:26, Bruce Richardson:
> > On Wed, Mar 10, 2021 at 01:33:20PM +0100, Thomas Monjalon wrote:
> > > 10/03/2021 13:19, Bruce Richardson:
> > > > On Wed, Mar 10, 2021 at 12
On 3/10/2021 3:11 PM, Ed Czeck wrote:
On Tue, Mar 9, 2021 at 12:50 PM Ferruh Yigit wrote:
On 3/9/2021 4:08 PM, Ed Czeck wrote:
- Rename extension functions with rte_pmd_ark prefix
- Move extension prototype to rte_pmd_ark.h
- Update local function documentation
Signed-off-by: Ed Czeck
---
v
On Wed, 10 Mar 2021 12:19:24 +
Bruce Richardson wrote:
> On Wed, Mar 10, 2021 at 12:31:10AM +0100, Thomas Monjalon wrote:
> > The parsing check for invalid log level was not trying to catch
> > irrelevant numeric values.
> > A log level 0 or too high is now a failure in options parsing
> > so
On Tue, Mar 9, 2021 at 12:50 PM Ferruh Yigit wrote:
>
> On 3/9/2021 4:08 PM, Ed Czeck wrote:
> > - Rename extension functions with rte_pmd_ark prefix
> > - Move extension prototype to rte_pmd_ark.h
> > - Update local function documentation
> >
> > Signed-off-by: Ed Czeck
> > ---
> > v3:
> > - spl
On Wed, 10 Mar 2021 12:10:01 +0100
Thomas Monjalon wrote:
> 10/03/2021 12:04, Dharmik Thakkar:
> > Enable volatile considered harmful warning since use of volatile
> > is suspect.
> >
> > Suggested-by: Stephen Hemminger
> > Signed-off-by: Dharmik Thakkar
> > Reviewed-by: Ruifeng Wang
>
> g
On Tue, Mar 9, 2021 at 12:36 PM Ferruh Yigit wrote:
>
> On 3/9/2021 4:08 PM, Ed Czeck wrote:
> > In this commit we generalize the movement of user-specified
> > meta data between mbufs and FPGA AXIS tuser fields using
> > user-defined hook functions.
> >
> > - Previous use of PMD dynfields are rem
On Wed, Mar 10, 2021 at 03:01:07PM +0100, Thomas Monjalon wrote:
> The log levels are configured by using the name of the logs.
> Some drivers are aligned to follow a common log name standard:
> pmd.class.driver[.sub]
> Some "common" drivers skip the "class" part:
> pmd.driver.sub
>
>
Existing API supports counter action to count traffic of a single flow.
The user could use the shared flag to share the action between different
flows. The user gives an id for counter action in creating the flow, and
when he wants to share it with another flow, he uses the same id.
Recent patch [
When compiled as a shared object, and loaded at runtime as a plugin,
the drivers should get the log level set earlier at EAL init
by the user through --log-level option.
The function for applying the log level setting is
rte_log_register_type_and_pick_level().
It is called by most drivers via RTE_
The log levels are configured by using the name of the logs.
Some drivers are aligned to follow a common log name standard:
pmd.class.driver[.sub]
Some "common" drivers skip the "class" part:
pmd.driver.sub
Signed-off-by: Thomas Monjalon
---
doc/guides/cryptodevs/qat.rst
After working on the option "--log-level help",
it became clear that few adjustments were required
for the log registration of some drivers.
Thomas Monjalon (3):
log: choose EAL log type on registration failure
drivers: fix log level after loading
drivers: align log names
doc/guides/crypto
In the unlikely case where something goes wrong
while registering a log type,
the fallback is to use the log type 0, assigned to EAL.
Signed-off-by: Thomas Monjalon
---
lib/librte_eal/include/rte_log.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_eal/include/rte_log.h b/lib/lib
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
When using decap actions it's been set to the data to decap
into the encap_data instead of decap_data, as a results we end
up with bad encap and decap data in many cases.
Fixes: 0c8f1f4ab90e ("app/flow-perf: support raw encap/decap actions")
Cc: sta...@dpdk.org
Signed-off-by: Wisam Jaddo
---
ap
Starting from this commit the app will always
report the first flow latency.
This is useful in debugging to check the first
flow insertion before any caching effect.
Signed-off-by: Wisam Jaddo
---
app/test-flow-perf/main.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/app/test-fl
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
--
v2:
* Add first insertion flow latency calculation.
* Fix for decap data set.
v3:
* Fixes in commit message.
* Fixes the cover page.
Wisam Jaddo (7):
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:
Starting from this commit the app will always
report the first flow latency.
This is useful in debugging to check the first
flow insertion before any caching effect.
Signed-off-by: Wisam Jaddo
---
app/test-flow-perf/main.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/app/test-fl
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
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
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
--
v2:
* Add first insertion flow latency calculation.
* Fix for decap data set.
v3:
* Fixes in commit message.
* Fixes the cover page.
Wisam Jaddo (7):
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:
When using decap actions it's been set to the data to decap
into the encap_data instead of decap_data, as a results we end
up with bad encap and decap data in many cases.
Fixes: 0c8f1f4ab90e ("app/flow-perf: support raw encap/decap actions")
Cc: sta...@dpdk.org
Signed-off-by: Wisam Jaddo
---
ap
Starting from this commit the app will always
report the first flow latency.
This is useful in debugging to check the first
flow insertion before any caching effect.
Signed-off-by: Wisam Jaddo
---
app/test-flow-perf/main.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/app/test-fl
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
changes in V2:
1- Add first flow insertion latency calculation.
2- Fix for decap data in raw decap actions.
Wisam Jaddo (7):
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
Starting from this commit the app will always
report the first flow latency.
This is useful in debugging to check the first
flow insertion before any caching effect.
Signed-off-by: Wisam Jaddo
---
app/test-flow-perf/main.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/app/test-fl
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
1 - 100 of 162 matches
Mail list logo
