> From: Morten Brørup [mailto:m...@smartsharesystems.com]
> Sent: Wednesday, 14 December 2022 11.41
>
> +CC: Mattias, see my comment below about per-thread constructor for
> this
>
> > From: Tomasz Duszynski [mailto:tduszyn...@marvell.com]
> > Sent: Wednesday, 14 December 2022 10.39
> >
> > Hello
On 2022-11-30 08:21, bugzi...@dpdk.org wrote:
> https://protect2.fireeye.com/v1/url?k=31323334-501cfaf3-313273af-454445554331-bcbbbdbd8c05330d&q=1&e=d0faa455-3b1a-4a2d-961c-8bf4a4fbf4ba&u=https%3A%2F%2Fbugs.dpdk.org%2Fshow_bug.cgi%3Fid%3D1135
>
> Bug ID: 1135
> Summary: [D
On 2022-11-11 10:43, Tomasz Duszynski wrote:
> Add support for programming PMU counters and reading their values
> in runtime bypassing kernel completely.
>
> This is especially useful in cases where CPU cores are isolated
> (nohz_full) i.e run dedicated tasks. In such cases one cannot use
> stand
On 2022-12-13 11:43, Tomasz Duszynski wrote:
> Add support for programming PMU counters and reading their values
> in runtime bypassing kernel completely.
>
> This is especially useful in cases where CPU cores are isolated
> (nohz_full) i.e run dedicated tasks. In such cases one cannot use
> stand
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of David Marchand
> Sent: Monday, 6 July 2020 22.53
>
> DPDK components and applications can have their say when a new lcore is
> initialized. For this, they can register a callback for initializing
> and
> releasing their private data.
>
> Sign
On Thu, Dec 15, 2022 at 10:05 AM Morten Brørup
wrote:
>
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of David Marchand
> > Sent: Monday, 6 July 2020 22.53
> >
> > DPDK components and applications can have their say when a new lcore is
> > initialized. For this, they can register a callba
Some dependencies were missing for builds in those two environments:
- for Ubuntu 20.04: libssl-dev, zlib1g-dev,
- for Fedora 35: libarchive-devel, libbsd-devel, jansson-devel,
Signed-off-by: David Marchand
---
.github/workflows/build.yml | 25 ++---
1 file changed, 14 insert
This list is hard to read.
Updating it has been done in an inconsistent way: container based and vm
based builds do not have the same coverage.
Prefer alphabetical order.
Signed-off-by: David Marchand
---
Note: I will likely squash this patch with the second one, but it is
easier to review in th
On Wed, Dec 14, 2022 at 09:30:05AM -0800, Tyler Retzlaff wrote:
> On Tue, Dec 13, 2022 at 06:27:24PM +, Bruce Richardson wrote:
> > For telemetry data, rather than having unsigned 64-bit values and signed
> > 32-bit values, we want to just have unsigned and signed values, each
> > stored with t
On Thu, Dec 15, 2022 at 09:49:06AM +0800, lihuisong (C) wrote:
>
> 在 2022/12/14 2:27, Bruce Richardson 写道:
> > For future standardization on the "uint" name for unsigned values rather
> > than the existing "u64" one, we can for now:
> > * rename all internal values to use uint rather than u64
> >
On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote:
> On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote:
> > For future standardization on the "uint" name for unsigned values rather
> > than the existing "u64" one, we can for now:
> > * rename all internal values to use u
On Tue, Dec 6, 2022 at 1:39 AM Tyler Retzlaff
wrote:
>
> Memory configuration was not being marked as completed add the missing
> call to rte_eal_init() for Windows.
>
> Signed-off-by: Tyler Retzlaff
The change is ok.
The commitlog misses some context: I guess the point is to let
rte_thread_reg
+CC Mattias, I forgot to put you on this discussion
> From: David Marchand [mailto:david.march...@redhat.com]
> Sent: Thursday, 15 December 2022 10.09
llbacks
>
> On Thu, Dec 15, 2022 at 10:05 AM Morten Brørup
> wrote:
> >
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of David Marchand
Some lib telemetry interfaces add the 'u32' and 'u64' data by the
rte_tel_data_add_dict/array_int API. This may cause data conversion
error or data truncation. This patch series uses 'u64' functions to
do this.
In addition, this patch series introduces two APIs to store unsigned
integer values as
The "stdint.h" header is outside '_RTE_TELEMETRY_H_' macro, which cause
this header is unconditional. So this patch moves this header to inside
'_RTE_TELEMETRY_H_'.
Fixes: 99a2dd955fba ("lib: remove librte_ prefix from directory names")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Mor
The 'u32' and 'u64' data can not assigned to 'int' type variable.
They need to use the 'u64' APIs to add.
Fixes: 58b43c1ddfd1 ("ethdev: add telemetry endpoint for device info")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
lib/ethdev/rte_eth
The 'u32' data can not assigned to 'int' type variable. The 'u32' data
needs to use the 'u64' APIs to add.
Fixes: d3d98f5ce9d0 ("cryptodev: support telemetry")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
lib/cryptodev/rte_cryptodev.c | 2 +
The 'u32' and 'u64' data can not assigned to 'int' type variable.
They need to use the 'u64' APIs to add.
Fixes: e6732d0d6e26 ("mem: add telemetry infos")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
lib/eal/common/eal_common_memory.c | 10
The 'u32' and 'u64' data can not assigned to 'int' type variable.
They need to use the 'u64' APIs to add.
Fixes: 2f5c4025abb3 ("mempool: add telemetry endpoint")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
lib/mempool/rte_mempool.c | 24 ++
Sometimes displaying a unsigned integer value as hexadecimal encoded style
is more expected for human consumption, such as, offload capability and
device flag. This patch introduces two APIs to add unsigned integer value
as hexadecimal encoded string to array or dictionary. And user can choose
whet
The 'dev_flags', 'rx_offloads', 'tx_offloads' and 'rss_hf' are better
displayed in hexadecimal format.
Like:
-->old display by input /ethdev/info,0
"dev_flags": 3,
"rx_offloads": 524288,
"tx_offloads": 65536,
"ethdev_rss_hf": 9100
--> now display
"dev_flags": "0x3",
Add test cases for adding hexadecimal unsigned integer value API.
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
app/test/test_telemetry_data.c | 150 +
1 file changed, 150 insertions(+)
diff --git a/app/test/test_telemetry_data.c
On 15/12/2022 03:44, Jiang, YuX wrote:
Hi All,
Hi Yu Jiang. Thanks for testing this. Some comments below.
Update the test status for Intel part. dpdk21.11.3-rc1 validation test is
almost finished, no critical issue is found.
Total find 3 bugs, 2 bugs are fixed on latest stable 21.11.
BUG1:
On Thu, Dec 15, 2022 at 06:31:44PM +0800, Huisong Li wrote:
> Sometimes displaying a unsigned integer value as hexadecimal encoded style
> is more expected for human consumption, such as, offload capability and
> device flag. This patch introduces two APIs to add unsigned integer value
> as hexadec
在 2022/12/14 17:55, humin (Q) 写道:
Acked-by：Min Hu (Connor)
Indeed, it is better to move them to bonding PMD. lgtm
Series-acked-by: Huisong Li
在 2022/12/14 14:13, Chengwen Feng 写道:
This patchset adds device private dump for bonding PMD, and use
rte_eth_dev_priv_dump API to implement testpm
在 2022/12/15 18:46, Bruce Richardson 写道:
On Thu, Dec 15, 2022 at 06:31:44PM +0800, Huisong Li wrote:
Sometimes displaying a unsigned integer value as hexadecimal encoded style
is more expected for human consumption, such as, offload capability and
device flag. This patch introduces two APIs to
> From: lihuisong (C) [mailto:lihuis...@huawei.com]
> Sent: Thursday, 15 December 2022 12.28
>
> 在 2022/12/15 18:46, Bruce Richardson 写道:
> > On Thu, Dec 15, 2022 at 06:31:44PM +0800, Huisong Li wrote:
> >> Sometimes displaying a unsigned integer value as hexadecimal encoded
> style
> >> is more e
On Thu, Dec 15, 2022 at 01:00:40PM +0100, Morten Brørup wrote:
> > From: lihuisong (C) [mailto:lihuis...@huawei.com]
> > Sent: Thursday, 15 December 2022 12.28
> >
> > 在 2022/12/15 18:46, Bruce Richardson 写道:
> > > On Thu, Dec 15, 2022 at 06:31:44PM +0800, Huisong Li wrote:
> > >> Sometimes displa
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Thursday, 15 December 2022 13.16
>
> On Thu, Dec 15, 2022 at 01:00:40PM +0100, Morten Brørup wrote:
> > > From: lihuisong (C) [mailto:lihuis...@huawei.com]
> > > Sent: Thursday, 15 December 2022 12.28
> > >
> > > 在 2022/12/15 18:
在 2022/12/15 20:24, Morten Brørup 写道:
From: Bruce Richardson [mailto:bruce.richard...@intel.com]
Sent: Thursday, 15 December 2022 13.16
On Thu, Dec 15, 2022 at 01:00:40PM +0100, Morten Brørup wrote:
From: lihuisong (C) [mailto:lihuis...@huawei.com]
Sent: Thursday, 15 December 2022 12.28
在 20
On 2022/12/14 18:38, Ferruh Yigit wrote:
> On 12/14/2022 7:25 AM, fengchengwen wrote:
>> On 2022/12/13 19:25, Ferruh Yigit wrote:
>>> On 12/13/2022 10:04 AM, fengchengwen wrote:
Hi Ferruh,
During the test, we need to delineate where go wrong when encountered
e.g. CRC error.
> From: lihuisong (C) [mailto:lihuis...@huawei.com]
> Sent: Thursday, 15 December 2022 13.46
>
> 在 2022/12/15 20:24, Morten Brørup 写道:
> >> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> >> Sent: Thursday, 15 December 2022 13.16
> >>
> >> On Thu, Dec 15, 2022 at 01:00:40PM +0100, Mor
On Thu, Dec 15, 2022 at 01:52:02PM +0100, Morten Brørup wrote:
> > From: lihuisong (C) [mailto:lihuis...@huawei.com]
> > Sent: Thursday, 15 December 2022 13.46
> >
> > 在 2022/12/15 20:24, Morten Brørup 写道:
> > >> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > >> Sent: Thursday, 15
15/12/2022 10:44, Bruce Richardson:
> On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote:
> > On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote:
> > > For future standardization on the "uint" name for unsigned values rather
> > > than the existing "u64" one, we can for no
On Thu, Dec 15, 2022 at 02:36:51PM +0100, Thomas Monjalon wrote:
> 15/12/2022 10:44, Bruce Richardson:
> > On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote:
> > > On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote:
> > > > For future standardization on the "uint" name fo
Hi John,
On 10/26/22 21:46, John Miller wrote:
Add new ark baseband device documentation.
This is the first patch in the series that introduces
the Arkville baseband PMD.
First we create a common/ark directory and move common files
from net/ark to share with the new baseband/ark device.
Next
Hi all,
Here is a new stable release:
https://fast.dpdk.org/rel/dpdk-19.11.14.tar.xz
The git tree is at:
https://dpdk.org/browse/dpdk-stable/?h=19.11
Christian Ehrhardt
---
VERSION| 2 +-
app/test-pmd/meson.build
https://bugs.dpdk.org/show_bug.cgi?id=1149
Bug ID: 1149
Summary: [21.11] lib/ring build failure with gcc 12 and debug
enabled
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRME
https://bugs.dpdk.org/show_bug.cgi?id=1150
Bug ID: 1150
Summary: [21.11] failure to build API's html docs on Fedora 37
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: norma
On Wed, Dec 14, 2022 at 07:22:15PM -0800, Stephen Hemminger wrote:
> On Wed, 14 Dec 2022 15:18:08 -0800
> "Kadam, Pallavi" wrote:
>
> > Hi Stephen,
> >
> > Thanks for enabling this support.
> >
> > On 11/30/2022 5:44 PM, Stephen Hemminger wrote:
> > > This driver builds ok on windows, but need
On 12/15/2022 12:46 PM, fengchengwen wrote:
> On 2022/12/14 18:38, Ferruh Yigit wrote:
>> On 12/14/2022 7:25 AM, fengchengwen wrote:
>>> On 2022/12/13 19:25, Ferruh Yigit wrote:
On 12/13/2022 10:04 AM, fengchengwen wrote:
> Hi Ferruh,
>
> During the test, we need to delineate w
> -Original Message-
> From: Kevin Traynor
> Sent: Tuesday, December 6, 2022 1:30 PM
> To: sta...@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe ;
> Ali Alnubani ; benjamin.wal...@intel.com; David
> Christensen ; Hemant Agrawal
> ; Ian Stokes ; Jerin
> Jacob ; John McNamara ;
> Ju-Hyoung Le
On Thu, Dec 15, 2022 at 09:41:38AM +, Bruce Richardson wrote:
> On Wed, Dec 14, 2022 at 09:30:05AM -0800, Tyler Retzlaff wrote:
> > On Tue, Dec 13, 2022 at 06:27:24PM +, Bruce Richardson wrote:
> > > For telemetry data, rather than having unsigned 64-bit values and signed
> > > 32-bit value
On Thu, Dec 15, 2022 at 09:44:49AM +, Bruce Richardson wrote:
> On Wed, Dec 14, 2022 at 09:38:45AM -0800, Tyler Retzlaff wrote:
> > On Tue, Dec 13, 2022 at 06:27:25PM +, Bruce Richardson wrote:
> > > For future standardization on the "uint" name for unsigned values rather
> > > than the exi
On Thu, Dec 15, 2022 at 09:42:40AM +, Bruce Richardson wrote:
> On Thu, Dec 15, 2022 at 09:49:06AM +0800, lihuisong (C) wrote:
> >
> > 在 2022/12/14 2:27, Bruce Richardson 写道:
> > > For future standardization on the "uint" name for unsigned values rather
> > > than the existing "u64" one, we ca
On Thu, Dec 15, 2022 at 10:59:07AM +0100, David Marchand wrote:
> On Tue, Dec 6, 2022 at 1:39 AM Tyler Retzlaff
> wrote:
> >
> > Memory configuration was not being marked as completed add the missing
> > call to rte_eal_init() for Windows.
> >
> > Signed-off-by: Tyler Retzlaff
>
> The change is
2022-12-15 09:48 (UTC-0800), Tyler Retzlaff:
> On Wed, Dec 14, 2022 at 07:22:15PM -0800, Stephen Hemminger wrote:
> > On Wed, 14 Dec 2022 15:18:08 -0800
> > "Kadam, Pallavi" wrote:
[...]
> > > There is still a build error with clang compiler on Windows
> > > as mentioned by Dmitry:
> > >
> > > ..
Enabled the flag "pmd_supports_disable_iova_as_pa" for octeontx2
compress VF driver files.
Signed-off-by: Mahipal Challa
---
drivers/common/octeontx/meson.build | 1 +
drivers/compress/octeontx/meson.build | 1 +
drivers/mempool/octeontx/meson.build | 1 +
3 files changed, 3 insertions(+)
di
Async burst mode feature support is added, improves the single thread
compression/decompression throughput.
Signed-off-by: Mahipal Challa
---
drivers/compress/octeontx/include/zip_regs.h | 1 +
drivers/compress/octeontx/otx_zip.h | 37 +--
drivers/compress/octeontx/otx_zip_pmd.c
On 2022/12/16 1:50, Ferruh Yigit wrote:
> On 12/15/2022 12:46 PM, fengchengwen wrote:
>> On 2022/12/14 18:38, Ferruh Yigit wrote:
>>> On 12/14/2022 7:25 AM, fengchengwen wrote:
On 2022/12/13 19:25, Ferruh Yigit wrote:
> On 12/13/2022 10:04 AM, fengchengwen wrote:
>> Hi Ferruh,
>>
>
在 2022/12/15 21:08, Bruce Richardson 写道:
On Thu, Dec 15, 2022 at 01:52:02PM +0100, Morten Brørup wrote:
From: lihuisong (C) [mailto:lihuis...@huawei.com]
Sent: Thursday, 15 December 2022 13.46
在 2022/12/15 20:24, Morten Brørup 写道:
From: Bruce Richardson [mailto:bruce.richard...@intel.com]
Se
The 'u32' and 'u64' data can not assigned to 'int' type variable.
They need to use the 'u64' APIs to add.
Fixes: 2f5c4025abb3 ("mempool: add telemetry endpoint")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
lib/mempool/rte_mempool.c | 24 ++
Some lib telemetry interfaces add the 'u32' and 'u64' data by the
rte_tel_data_add_dict/array_int API. This may cause data conversion
error or data truncation. This patch series uses 'u64' functions to
do this.
In addition, this patch series introduces two APIs to store unsigned
integer values as
The "stdint.h" header is outside '_RTE_TELEMETRY_H_' macro, which cause
this header is unconditional. So this patch moves this header to inside
'_RTE_TELEMETRY_H_'.
Fixes: 99a2dd955fba ("lib: remove librte_ prefix from directory names")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Mor
The 'u32' and 'u64' data can not assigned to 'int' type variable.
They need to use the 'u64' APIs to add.
Fixes: 58b43c1ddfd1 ("ethdev: add telemetry endpoint for device info")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
lib/ethdev/rte_eth
The 'u32' data can not assigned to 'int' type variable. The 'u32' data
needs to use the 'u64' APIs to add.
Fixes: d3d98f5ce9d0 ("cryptodev: support telemetry")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
lib/cryptodev/rte_cryptodev.c | 2 +
The 'u32' and 'u64' data can not assigned to 'int' type variable.
They need to use the 'u64' APIs to add.
Fixes: e6732d0d6e26 ("mem: add telemetry infos")
Cc: sta...@dpdk.org
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
lib/eal/common/eal_common_memory.c | 10
Sometimes displaying a unsigned integer value as hexadecimal encoded style
is more expected for human consumption, such as, offload capability and
device flag. This patch introduces two APIs to add unsigned integer value
as hexadecimal encoded string to array or dictionary. And user can choose
whet
Add test cases for adding hexadecimal unsigned integer value API.
Signed-off-by: Huisong Li
Acked-by: Morten Brørup
Acked-by: Chengwen Feng
---
app/test/test_telemetry_data.c | 150 +
1 file changed, 150 insertions(+)
diff --git a/app/test/test_telemetry_data.c
The 'dev_flags', 'rx_offloads', 'tx_offloads' and 'rss_hf' are better
displayed in hexadecimal format.
Like:
-->old display by input /ethdev/info,0
"dev_flags": 3,
"rx_offloads": 524288,
"tx_offloads": 65536,
"ethdev_rss_hf": 9100
--> now display
"dev_flags": "0x3",
Hi
Code looks good to me.
> -Original Message-
> From: Abhishek Maheshwari
> Sent: Thursday, December 15, 2022 11:48 AM
> To: Wang, Xiao W
> Cc: dev@dpdk.org; sta...@dpdk.org; Xia, Chenbo ;
> Mandal, Purna Chandra ; Maheshwari,
> Abhishek
> Subject: [PATCH v4] vdpa/ifc: Match default s
Vhost asynchronous data-path offloads packet copy from the CPU
to the DMA engine. As a result, large packet copy can be accelerated
by the DMA engine, and vhost can free CPU cycles for higher level
functions.
In this patch, we enable asynchronous data-path for vhostpmd.
Asynchronous data path is e
This patch change the interrupt interval from 8160us to 32us
to improve the performance of multi-driver mode.
Signed-off-by: Qiming Yang
---
drivers/net/i40e/i40e_ethdev.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/i40e/i40e_ethdev.h b/drivers/net/i40e/i40e_e
Hi, Akhil
Excuse me for the question.
I am testing UADK crypto performance with dpdk-test-crypto-perf, and
want to use multi-thread or multi-session for better performance, so
trying to use crypto_scheduler.
CMD like
sudo dpdk-test-crypto-perf -l 1,2 --vdev "crypto_uadk0" --vdev
"crypto_uad
> From: Morten Brørup [mailto:m...@smartsharesystems.com]
> Sent: Thursday, 15 December 2022 09.22
>
> > From: Morten Brørup [mailto:m...@smartsharesystems.com]
> > Sent: Wednesday, 14 December 2022 11.41
> >
> > +CC: Mattias, see my comment below about per-thread constructor for
> > this
> >
> >
Hi Kevin,
RedHat QE does not find new issues about the 21.11.3 dpdk during the tests.
We tested below 17 scenarios and all got PASS on RHEL8:
- Guest with device assignment(PF) throughput testing(1G hugepage size):
PASS
- Guest with device assignment(PF) throughput testing(2M hugepage s
66 matches
Mail list logo
