Hi Ferruh,
> -Original Message-
> From: Li, Miao
> Sent: Monday, October 25, 2021 10:47 PM
> To: dev@dpdk.org
> Cc: Xia, Chenbo ; maxime.coque...@redhat.com; Li, Miao
>
> Subject: [PATCH v8 0/5] Support power monitor in virtio/vhost PMD
>
> This patchset implements rte_power_monitor API
https://bugs.dpdk.org/show_bug.cgi?id=834
Bug ID: 834
Summary: eventdev/eth_rx: callback not invoked in vector
timeout case
Product: DPDK
Version: 21.08
Hardware: All
OS: All
Status: UNCONFIRMED
From: Dapeng Yu
After DCF is reset by PF, the DCF device un-initialization cannot
function normally since the resource is already invalidated. So
reset DCF twice is necessary, the first reset re-initializes the DCF,
only then second reset can clean the filters successfully.
This patch detects th
Hi Maxime,
> -Original Message-
> From: Maxime Coquelin
> Sent: Monday, October 18, 2021 9:02 PM
> To: dev@dpdk.org; Xia, Chenbo ; Hu, Jiayu
> ; Wang, YuanX ; Ma,
> WenwuX ; Richardson, Bruce
> ; Mcnamara, John
> ; david.march...@redhat.com
> Cc: Maxime Coquelin
> Subject: [PATCH v1 08/1
> +#define CRYPTO_CAPS_SZ \
> + (RTE_ALIGN_CEIL(sizeof(struct rte_cryptodev_capabilities), \
> + sizeof(uint64_t)) /\
> + sizeof(uint64_t))
> +
> +static int
> +crypto_caps_array(struct rte_tel_data *d,
On Sun, Oct 24, 2021 at 3:12 PM Raslan Darawsheh wrote:
> > Build is broken on RHEL7 following introduction of this new protocol.
> >
> > Fixes: 3a929df1f286 ("ethdev: support L2TPv2 and PPP procotol")
> >
> > Signed-off-by: David Marchand
> Tested-by: Raslan Darawsheh
Applied, thanks.
--
Da
On 2021-10-19 20:14, jer...@marvell.com wrote:
> From: Jerin Jacob
>
>
> Dataplane Workload Accelerator library
> ==
>
> Definition of Dataplane Workload Accelerator
>
> Dataplane Workload Accelerator(DWA) typically c
From: Dapeng Yu
When the switch flow rules are redirected, if rule is removed but not
added successfully, the rule will lost meta data, and cannot be added.
This patch saves the flow rule's meta, so when the flow rule is added
again, the meta can be used to make addition succeed.
Fixes: 397b4b3
On Sat, Oct 23, 2021 at 2:40 PM David Marchand
wrote:
> On Sat, Oct 23, 2021 at 2:18 PM Xueming Li wrote:
> >
> > In layer argument test function, kvargs are parsed and checked without
> > free. This patch calls rte_kvargs_free() function to avoid memory leak.
> >
>
> Coverity issue: 373631
> > F
https://bugs.dpdk.org/show_bug.cgi?id=835
Bug ID: 835
Summary: Previous patch introduced bugs in
rte_ipv4_fragment_packet functions
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status
The patch ("ip_frag: fix fragmenting IPv4 fragment") introduces
a bug and needs to be rolled back. This is because the patch
and variables "flag_offset" conflict with each other.
Bugzilla ID: 835
Fixes: 567473433b7e ("ip_frag: fix fragmenting IPv4 fragment")
Cc: sta...@dpdk.org
Signed-off-by: huic
Add the test content of the fragment_offset(offset and MF)
to the test_ip_frag function. Add test data for a fragment
that is not the last fragment.
Signed-off-by: huichao cai
---
app/test/test_ipfrag.c | 95 +-
1 file changed, 79 insertions(+), 16
On Mon, Oct 25, 2021 at 1:05 PM Mattias Rönnblom
wrote:
>
> On 2021-10-19 20:14, jer...@marvell.com wrote:
> > From: Jerin Jacob
> >
> >
> > Dataplane Workload Accelerator library
> > ==
> >
> > Definition of Dataplane Workload Accelerator
> > -
> Subject: [EXT] [PATCH 1/2] ipsec: add transmit segmentation offload support
>
Title should be ipsec: support TSO
> Add support for transmit segmentation offload to inline crypto processing
> mode. This offload is not supported by other offload modes, as at a
> minimum it requires inline crypto
> -邮件原件-
> 发件人: Ananyev, Konstantin
> 发送时间: Friday, October 22, 2021 12:25 AM
> 收件人: Feifei Wang ; Ruifeng Wang
>
> 抄送: dev@dpdk.org; nd
> 主题: RE: [PATCH v4 1/5] eal: add new definitions for wait scheme
>
> > Introduce macros as generic interface for address monitoring.
> >
> > Signed
> -邮件原件-
> 发件人: Jerin Jacob
> 发送时间: Friday, October 22, 2021 8:10 AM
> 收件人: Feifei Wang
> 抄送: Ruifeng Wang ; Ananyev, Konstantin
> ; dpdk-dev ; nd
>
> 主题: Re: [dpdk-dev] [PATCH v4 1/5] eal: add new definitions for wait scheme
>
> On Wed, Oct 20, 2021 at 2:16 PM Feifei Wang
> wrote:
> >
24/10/2021 13:48, Ananyev, Konstantin:
>
> > > > > When stopping a port, the data path Tx and Rx burst functions
> > > should
> > > > > be stopped firstly conventionally. Then the dummy functions are
> > > used
> > > > > to replace the callback functions provided by the PMD.
> > > > >
> > > > > Wh
On Mon, Oct 25, 2021 at 3:01 PM Feifei Wang wrote:
>
> > -邮件原件-
> > 发件人: Jerin Jacob
> > 发送时间: Friday, October 22, 2021 8:10 AM
> > 收件人: Feifei Wang
> > 抄送: Ruifeng Wang ; Ananyev, Konstantin
> > ; dpdk-dev ; nd
> >
> > 主题: Re: [dpdk-dev] [PATCH v4 1/5] eal: add new definitions for wait
On Mon, Oct 25, 2021 at 11:43 AM Thomas Monjalon wrote:
> > Correctly behaving app should never call these stub functions and should
> > never see these messages.
> > If your app ended up inside this function, then there something really
> > wrong is going on,
> > that can cause app crash, silen
22/10/2021 06:34, Shijith Thotton:
> >>
> >> Removed freeing of unallocated mempool in event timer adapter create unit
> >> test.
> >>
> >> Fixes: d1f3385d0076 ("test: add event timer adapter auto-test")
> >>
> >> Signed-off-by: Shijith Thotton
> >Acked-by: Erik Gabriel Carrillo
>
> Thomas, Ple
09/09/2021 22:11, Carrillo, Erik G:
> > From: Shijith Thotton
> >
> > Removed freeing of unallocated mempool in event timer adapter create unit
> > test.
> >
> > Fixes: d1f3385d0076 ("test: add event timer adapter auto-test")
> >
> > Signed-off-by: Shijith Thotton
> Acked-by: Erik Gabriel Carr
Hi Jiayu,
On 10/25/21 09:22, Hu, Jiayu wrote:
Hi Maxime,
-Original Message-
From: Maxime Coquelin
Sent: Monday, October 18, 2021 9:02 PM
To: dev@dpdk.org; Xia, Chenbo ; Hu, Jiayu
; Wang, YuanX ; Ma,
WenwuX ; Richardson, Bruce
; Mcnamara, John
; david.march...@redhat.com
Cc: Maxime Coq
https://bugs.dpdk.org/show_bug.cgi?id=836
Bug ID: 836
Summary: DPDK doesn't build under meson 0.60
Product: DPDK
Version: 21.08
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priorit
2021-10-24 22:04 (UTC+0200), David Marchand:
> From: Harman Kalra
>
> Removing direct access to interrupt handle structure fields,
> rather use respective get set APIs for the same.
> Making changes to all the libraries access the interrupt handle fields.
>
> Implementing alarm cleanup routine,
Hi David,
With some nits below,
Acked-by: Dmitry Kozlyuk
2021-10-24 22:04 (UTC+0200), David Marchand:
> From: Harman Kalra
>
> Dynamically allocating the efds and elist array os intr_handle
Typo: "os" -> "of"
> structure, based on size provided by user. Eg size can be
> MSIX interrupts suppo
VF representors do not own dedicated m-ports and thus cannot
be referred to as traffic endpoints in flow items or actions.
Fixes: a62ec90522a6 ("net/sfc: add port representors infrastructure")
Fixes: f55b61cec94a ("net/sfc: support port representor flow item")
Signed-off-by: Ivan Malov
Reviewed-
Make these messages more specific.
Signed-off-by: Ivan Malov
Reviewed-by: Andrew Rybchenko
---
drivers/net/sfc/sfc_mae.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/sfc/sfc_mae.c b/drivers/net/sfc/sfc_mae.c
index 84b13925ff..a4a22f32c6 100644
--- a/driv
The function in question has an unfortunate name that reads
like finding a SW switch port entry. In fact just one of
the two m-ports is retrieved from that entry.
Signed-off-by: Ivan Malov
Reviewed-by: Andrew Rybchenko
---
drivers/net/sfc/sfc_mae.c| 10 +-
drivers/net/sfc/sfc_switch
In accordance with patches [1-4], MAE admin ethdev represents a
network port and not the PF which it sits on. Rework the way
how "ethdev" and "entity" m-ports are assigned in SW switch
port entries of independent ethdevs. Explain in comments.
[1] commit 081e42dab11d ("ethdev: add port representor
Add support for item REPRESENTED_PORT to match on traffic entering
the embedded switch from the entity represented by the given
ethdev (network port or VF).
Signed-off-by: Ivan Malov
Reviewed-by: Andrew Rybchenko
---
doc/guides/nics/features/sfc.ini | 1 +
doc/guides/nics/sfc_efx.rst | 2
Add support for actions PORT_REPRESENTOR and REPRESENTED_PORT.
The former should be used instead of ambiguous PORT_ID.
The latter sends traffic to the entity represented by
the given ethdev (network port or VF).
Signed-off-by: Ivan Malov
Reviewed-by: Andrew Rybchenko
---
doc/guides/nics/featu
[1] has deprecated the use of direction attributes in "transfer"
flows. Ignore them during the transition period.
[1] commit 9d2a349b388a ("ethdev: deprecate direction attributes
in transfer flows")
Signed-off-by: Ivan Malov
Reviewed-by: Andrew Rybchenko
---
drivers/net/sfc/sfc_flow.c | 4 ++--
On Mon, Oct 25, 2021 at 12:49 PM Dmitry Kozlyuk
wrote:
> > diff --git a/lib/eal/freebsd/eal_alarm.c b/lib/eal/freebsd/eal_alarm.c
> > index c38b2e04f8..1a8fcf24c5 100644
> > --- a/lib/eal/freebsd/eal_alarm.c
> > +++ b/lib/eal/freebsd/eal_alarm.c
> > @@ -32,7 +32,7 @@
> >
> > struct alarm_entry {
On Mon, Oct 25, 2021 at 12:49 PM Dmitry Kozlyuk
wrote:
> > diff --git a/lib/eal/common/eal_common_interrupts.c
> > b/lib/eal/common/eal_common_interrupts.c
> > index 3285c4335f..7feb9da8fa 100644
> > --- a/lib/eal/common/eal_common_interrupts.c
> > +++ b/lib/eal/common/eal_common_interrupts.c
> [
DPDK sched library is equipped with mechanism that secures it from the
bufferbloat problem
which is a situation when excess buffers in the network cause high latency and
latency
variation. Currently, it supports RED for active queue management. However, more
advanced queue management is required
Implement PIE based congestion management based on rfc8033
Signed-off-by: Liguzinski, WojciechX
--
Changes in V18:
- Resolved merge conflict in lib/sched/meson.build after rebasing ontop of main
- Reverted whitespace change in app_thread.c - comment from Stephen Hemminger
Changes in V17:
- Corre
patch add support enable PIE or RED by
parsing config file.
Signed-off-by: Liguzinski, WojciechX
---
config/rte_config.h| 1 -
examples/qos_sched/cfg_file.c | 127 +++--
examples/qos_sched/cfg_file.h | 5 +
examples/qos_sched/init.c | 27 +++--
examples/qo
Adding the PIE support for IP Pipeline
Signed-off-by: Liguzinski, WojciechX
---
examples/ip_pipeline/tmgr.c | 142 +++-
1 file changed, 74 insertions(+), 68 deletions(-)
diff --git a/examples/ip_pipeline/tmgr.c b/examples/ip_pipeline/tmgr.c
index e4e364cbc0..b138
Added PIE related information to documentation.
Signed-off-by: Liguzinski, WojciechX
---
doc/guides/prog_guide/glossary.rst | 3 +
doc/guides/prog_guide/qos_framework.rst | 64 +---
doc/guides/prog_guide/traffic_management.rst | 13 +++-
3 files changed, 68 insert
Tests for PIE code added to test application.
Signed-off-by: Liguzinski, WojciechX
---
app/test/meson.build |4 +
app/test/test_pie.c | 1065 ++
lib/sched/rte_pie.c |6 +-
lib/sched/rte_pie.h | 17 +-
4 files changed, 1085 insertions(+), 7 del
21/10/2021 05:23, Yogesh Jangra:
> The instruction_data array was incorrectly indexed, which resulted in
> the array index getting out of bounds and sometimes segfault.
>
> Fixes: a1711f (“pipeline: add SWX Rx and extract instructions“)
> Cc: sta...@dpdk.org
>
> Signed-off-by: Yogesh Jangra
> Ac
Windows EAL did not detect IOVA mode and worked incorrectly
if physical addresses could not be obtained
(if virt2phys driver was missing or inaccessible).
In this case, rte_mem_virt2iova() reported RTE_BAD_IOVA for any address.
Inability to obtain IOVA, be it PA or VA, should cause a failure
for th
17/09/2021 12:32, Yogesh Jangra:
> Add support for configurable number of loops through the input PCAP
> file for the source port. Added an additional parameter to source
> port CLI command.
>
> Signed-off-by: Yogesh Jangra
> Acked-by: Cristian Dumitrescu
Applied, thanks.
Endianness is already handled by the checks on RTE_BYTE_ORDER.
Marking bitfields with endianness types is at best unneeded, at worse it
breaks build with OVS (with sparse enabled).
Example:
../../lib/ofp-packet.c: note: in included file (through
.../ovs/dpdk-dir/build/include/rte_flow.h, ../../l
Support the MLX5 crypto driver on Windows OS by moving the driver's
control path communication with the Kernel to be OS agnostic.
---
v3: Remove code which was already introduced in previous patches.
Rebase on master and remove "Depends-on" message.
v2: Split build change for mlx5 only and
Add needed DV enums used by the crypto PMD and missing
for Windows OS.
Signed-off-by: Tal Shnaiderman
Acked-by: Matan Azrad
---
drivers/common/mlx5/windows/mlx5_win_defs.h | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/common/mlx5/windows/mlx5_win_defs.h
b/drivers/co
Remove the usage of PTHREAD_MUTEX_INITIALIZER which is not
support in Windows and initialize priv_list_lock in RTE_INIT.
Signed-off-by: Tal Shnaiderman
Acked-by: Matan Azrad
---
drivers/crypto/mlx5/mlx5_crypto.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/cryp
Remove the check and build failure from crypto/meson.build
in case building for Windows OS.
Add this check/failure in the meson.build file of each crypto PMD
that is not enforcing it to allow PMD support for Windows
per driver when applicable.
Signed-off-by: Tal Shnaiderman
Acked-by: Matan Azrad
18/10/2021 03:22, Yogesh Jangra:
> Enable restricting the scope of an action to regular table entries or
> to the table default entry in order to support the P4 language
> tableonly or defaultonly annotations.
>
> Signed-off-by: Yogesh Jangra
> Acked-by: Cristian Dumitrescu
Applied, thanks.
The size of the UMR WQE allocated object is decided by a sizof
operation on the struct, however since the struct contains
a union of flexible array members this sizeof results can differ
between compilers.
GCC for example treats the union as 0 sized, MSVC adds a padding
of 16Bits.
To resolve the
Add support for mlx5 crypto pmd on Windows OS.
Add changes to release note and pmd guide.
Signed-off-by: Tal Shnaiderman
Acked-by: Matan Azrad
---
doc/guides/cryptodevs/mlx5.rst | 15 ---
doc/guides/rel_notes/release_21_11.rst | 1 +
drivers/common/mlx5/version.
> > > Correctly behaving app should never call these stub functions and should
> > > never see these messages.
> > > If your app ended up inside this function, then there something really
> > > wrong is going on,
> > > that can cause app crash, silent memory corruption, NIC HW hang, or many
> >
On Mon, Oct 25, 2021 at 3:04 PM Raslan Darawsheh wrote:
>
> Hi,
>
> > -Original Message-
> > From: dev On Behalf Of Harman Kalra
> > Sent: Friday, October 22, 2021 11:49 PM
> > To: dev@dpdk.org
> > Cc: david.march...@redhat.com; dmitry.kozl...@gmail.com;
> > m...@ashroe.eu; NBU-Contact-Th
> > This API was introduced in 18.05, therefore removing
> > experimental tag to promote it to stable state
> >
> > Signed-off-by: Jasvinder Singh
> Acked-by: Ray Kinsella
Applied, thanks.
25/10/2021 14:55, Ananyev, Konstantin:
>
> > > > Correctly behaving app should never call these stub functions and
> > > > should never see these messages.
> > > > If your app ended up inside this function, then there something really
> > > > wrong is going on,
> > > > that can cause app crash,
On Mon, Oct 25, 2021 at 3:27 PM Thomas Monjalon wrote:
> > > > There is a concern about getting efficient log report,
> > > > especially when looking at CI issues.
> > >
> > > +1.
> > > The current solution with logs is a real pain.
> >
> > Are you guys talking about problems with
> > app/test/sam
On Sat, Oct 23, 2021 at 12:09:19AM +0300, Dmitry Kozlyuk wrote:
> When mempool had been created with RTE_MEMPOOL_F_NO_IOVA_CONTIG flag
> but later populated with valid IOVA, RTE_MEMPOOL_F_NON_IO was unset,
> while it should be kept. The unit test did not catch this
> because rte_mempool_populate_de
> > From: Aman Singh
> >
> > As suse version numbering is inconsistent to determine Linux kernel API to
> > be used. In this patch we check parameter of 'ndo_tx_timeout'
> > API directly from the kernel source. This is done only for suse build.
> >
> > Bugzilla ID: 812
> > Cc: sta...@dpdk.org
>
Moving struct rte_intr_handle as an internal structure to
avoid any ABI breakages in future. Since this structure defines
some static arrays and changing respective macros breaks the ABI.
Eg:
Currently RTE_MAX_RXTX_INTR_VEC_ID imposes a limit of maximum 512
MSI-X interrupts that can be defined for
From: Harman Kalra
Prototype/Implement get set APIs for interrupt handle fields.
User won't be able to access any of the interrupt handle fields
directly while should use these get/set APIs to access/manipulate
them.
Internal interrupt header i.e. rte_eal_interrupt.h is rearranged,
as APIs defin
From: Harman Kalra
Making changes to the interrupt framework to use interrupt handle
APIs to get/set any field.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v6:
- fixed compilation on FreeBSD,
Changes since v5:
- used new helper rte_intr_instance_dup,
---
lib/
From: Harman Kalra
Updating the interrupt testsuite to make use of interrupt
handle get set APIs.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v5:
- fixed leak on when some interrupt handle can't be allocated,
---
app/test/test_interrupts.c | 164 ++
From: Harman Kalra
Removing direct access to interrupt handle structure fields,
rather use respective get set APIs for the same.
Making changes to all the libraries access the interrupt handle fields.
Implementing alarm cleanup routine, where the memory allocated
for interrupt instance can be fr
From: Harman Kalra
Removing direct access to interrupt handle structure fields,
rather use respective get set APIs for the same.
Making changes to all the libraries access the interrupt handle fields.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v5:
- split from
From: Harman Kalra
Moving interrupt handle structure definition inside a EAL private
header to make its fields totally opaque to the outside world.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v5:
- let rte_intr_handle fields untouched:
- split vfio / uio fd re
From: Harman Kalra
VFIO/UIO are mutually exclusive, storing file descriptor in a single
field is enough.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v5:
- split from patch5,
---
lib/eal/common/eal_common_interrupts.c | 6 +++---
lib/eal/common/eal_interrupts.h
From: Harman Kalra
Dynamically allocating the efds and elist array of intr_handle
structure, based on size provided by user. Eg size can be
MSIX interrupts supported by a PCI device.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
Acked-by: Dmitry Kozlyuk
---
Changes since v6:
- rem
Moving struct rte_intr_handle as an internal structure to
avoid any ABI breakages in future. Since this structure defines
some static arrays and changing respective macros breaks the ABI.
Eg:
Currently RTE_MAX_RXTX_INTR_VEC_ID imposes a limit of maximum 512
MSI-X interrupts that can be defined for
From: Harman Kalra
Prototype/Implement get set APIs for interrupt handle fields.
User won't be able to access any of the interrupt handle fields
directly while should use these get/set APIs to access/manipulate
them.
Internal interrupt header i.e. rte_eal_interrupt.h is rearranged,
as APIs defin
From: Harman Kalra
Making changes to the interrupt framework to use interrupt handle
APIs to get/set any field.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v6:
- fixed compilation on FreeBSD,
Changes since v5:
- used new helper rte_intr_instance_dup,
---
lib/
From: Harman Kalra
Updating the interrupt testsuite to make use of interrupt
handle get set APIs.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v5:
- fixed leak on when some interrupt handle can't be allocated,
---
app/test/test_interrupts.c | 164 ++
From: Harman Kalra
Removing direct access to interrupt handle structure fields,
rather use respective get set APIs for the same.
Making changes to all the libraries access the interrupt handle fields.
Implementing alarm cleanup routine, where the memory allocated
for interrupt instance can be fr
From: Harman Kalra
Removing direct access to interrupt handle structure fields,
rather use respective get set APIs for the same.
Making changes to all the libraries access the interrupt handle fields.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v5:
- split from
From: Harman Kalra
Moving interrupt handle structure definition inside a EAL private
header to make its fields totally opaque to the outside world.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v5:
- let rte_intr_handle fields untouched:
- split vfio / uio fd re
From: Harman Kalra
VFIO/UIO are mutually exclusive, storing file descriptor in a single
field is enough.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
---
Changes since v5:
- split from patch5,
---
lib/eal/common/eal_common_interrupts.c | 6 +++---
lib/eal/common/eal_interrupts.h
> > > Introduce macros as generic interface for address monitoring.
> > >
> > > Signed-off-by: Feifei Wang
> > > Reviewed-by: Ruifeng Wang
> > > ---
> > > lib/eal/arm/include/rte_pause_64.h | 126
> > > lib/eal/include/generic/rte_pause.h |
> > > 32 +++
> > >
From: Harman Kalra
Dynamically allocating the efds and elist array of intr_handle
structure, based on size provided by user. Eg size can be
MSIX interrupts supported by a PCI device.
Signed-off-by: Harman Kalra
Signed-off-by: David Marchand
Acked-by: Dmitry Kozlyuk
---
Changes since v6:
- rem
Minutes of Technical Board Meeting, 2021-Oct-20
Members Attending
-
-Bruce
-Ferruh
-Hemant
-Honnappa
-Jerin
-Kevin
-Konstantin (Chair)
-Maxime
-Stephen
-Thomas
NOTE: The technical board meetings every second Wednesday at
https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public,
25/10/2021 15:33, Olivier Matz:
> On Sat, Oct 23, 2021 at 12:09:19AM +0300, Dmitry Kozlyuk wrote:
> > When mempool had been created with RTE_MEMPOOL_F_NO_IOVA_CONTIG flag
> > but later populated with valid IOVA, RTE_MEMPOOL_F_NON_IO was unset,
> > while it should be kept. The unit test did not catc
20/10/2021 21:31, Robin Jarry:
> Hello,
>
> 2021-10-19, David Marchand:
> > Migration to argparse was incomplete.
> >
> > $ dpdk-pmdinfo.py -p $(which dpdk-testpmd)
> > Traceback (most recent call last):
> > File "/usr/bin/dpdk-pmdinfo.py", line 626, in
> > main()
> > File "/usr/bin/dpdk
15/10/2021 14:26, Olivier Matz:
> On Fri, Oct 15, 2021 at 10:39:41AM +0200, David Marchand wrote:
> > This option should be prefixed with -- for consistency with others.
> >
> > Fixes: a103a97e7191 ("eal: allow user to override default mempool driver")
> > Cc: sta...@dpdk.org
> >
> > Signed-off-b
21/10/2021 10:51, Eli Britstein:
> Functions and macros in x86 rte_memcpy.h may cause cast-align warnings,
> when using strict cast align flag with supporting gcc:
> gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
> CFLAGS="-Wcast-align=strict" make V=1 -C examples/l2fwd clean static
>
> For example:
> I
14/10/2021 18:21, Jie Zhou:
> Enable building subset of libraries that tests depend on for Windows
>
> Signed-off-by: Jie Zhou
> ---
> lib/meson.build | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/meson.build b/lib/meson.build
> index b2ba7258d8..bd6c27deef 100644
> --- a/lib/m
14/10/2021 14:26, Aaron Conole:
> Juraj Linkeš writes:
>
> > The way we're building DPDK in CI, with -Dmachine=default, has not been
> > updated when the option got replaced to preserve a backwards-complatible
> > build call to facilitate ABI verification between DPDK versions. Update
> > the cal
14/10/2021 10:20, Bruce Richardson:
> On Thu, Oct 14, 2021 at 04:54:18AM +0800, Kefu Chai wrote:
> > RTE_MBUF_REFCNT_ATOMIC = 0 is not necessary for applications like
> > Seastar, where it's safe to assume that the mbuf refcnt is only
> > updated by a single core only.
> >
> > Signed-off-by: Kefu
Options used to be sorted alphabetically.
It looks easier to read when major options are first,
then path tuning, libs options, and drivers options.
Signed-off-by: Thomas Monjalon
---
meson_options.txt | 75 ---
1 file changed, 39 insertions(+), 36 del
On Mon, Oct 25, 2021 at 6:53 AM Honnappa Nagarahalli
wrote:
>
> v3:
> a) Added Fixes, Cc:stable#dpdk.org in 1/6
> b) Merged 3/6 & 4/6 and moved after the first commit in the series
> c) Merged 2/6 & 5/6 as they need to be in a single commit
> d) Removed use of volatile in 6/6 (Konstantin)
>
> rte_
25/10/2021 18:17, Thomas Monjalon:
> Options used to be sorted alphabetically.
> It looks easier to read when major options are first,
> then path tuning, libs options, and drivers options.
Even better, we could insert a blank line between each option.
10/09/2021 11:46, Mcnamara, John:
> From: Medvedkin, Vladimir
>
> The git diff makes this look like the ifdef is moving but I see that you are
> moving the doc into the right place so Doxygen can pick it up.
>
> Acked-by: John McNamara
title: hash: fix Doxygen comment of Toeplitz file
Applie
21/10/2021 20:54, Vladimir Medvedkin:
> This patch adds performance tests for different implementations
> of the Toeplitz hash function.
Please name them.
> Signed-off-by: Vladimir Medvedkin
There are some garbage,
> @@ -320,6 +321,7 @@ perf_test_names = [
> 'hash_readwrite_lf_perf_au
Hi,
> -Original Message-
> From: dev On Behalf Of Harman Kalra
> Sent: Friday, October 22, 2021 11:49 PM
> To: dev@dpdk.org
> Cc: david.march...@redhat.com; dmitry.kozl...@gmail.com;
> m...@ashroe.eu; NBU-Contact-Thomas Monjalon ;
> Harman Kalra
> Subject: [dpdk-dev] [PATCH v5 0/6] make
Vladimir, your patches are late and not perfect.
You need reviews. Please ask other maintainers to help with reviews.
21/10/2021 20:54, Vladimir Medvedkin:
> This patch adds documentation for the new optimized Toeplitz hash
> implementation using GFNI.
>
> Signed-off-by: Vladimir Medvedkin
> --
21/10/2021 20:54, Vladimir Medvedkin:
> This patch add a new Toeplitz hash implementation using
> Galios Fields New Instructions (GFNI).
>
> Signed-off-by: Vladimir Medvedkin
> Acked-by: Konstantin Ananyev
> ---
> --- a/lib/hash/version.map
> +++ b/lib/hash/version.map
> @@ -39,10 +39,12 @@ EXPE
22/10/2021 11:07, Bruce Richardson:
> On Thu, Oct 21, 2021 at 06:15:49PM +0100, Vladimir Medvedkin wrote:
> > This patch fixes buffer overflow reported by ASAN,
> > please reference https://bugs.dpdk.org/show_bug.cgi?id=819
> >
> > The rte_lpm6 keeps routing information for control plane purpose
>
06/09/2021 17:54, Vladimir Medvedkin:
> Fixes: 03b8372a9a73 ("rib: fix max depth IPv6 lookup")
> Cc: ohily...@iol.unh.edu
> Cc: sta...@dpdk.org
>
> Signed-off-by: Vladimir Medvedkin
An explanation would have been appreciated.
> - index = (depth & (UINT8_MAX - 1)) / CHAR_BIT;
> + index =
06/09/2021 17:55, Vladimir Medvedkin:
> This patch adds a new parameter to the fib configuration to specify
> the size of the extension for internal RIB structure.
It looks to be an announced API change.
What happens if the new field is not initialized in the app?
At least it would deserve a note
On Thu, 21 Oct 2021 19:54:29 +0100
Vladimir Medvedkin wrote:
> +static uint8_t default_rss_key[] = {
Should this be const?
That way you can make sure API isn't modifying it.
Hi,
> -Original Message-
> From: David Marchand
> Sent: Monday, October 25, 2021 5:27 PM
> To: hka...@marvell.com; dev@dpdk.org
> Cc: dmitry.kozl...@gmail.com; Raslan Darawsheh ;
> NBU-Contact-Thomas Monjalon
> Subject: [PATCH v8 0/9] make rte_intr_handle internal
>
> Moving struct rte_i
On 10/25/2021 5:20 AM, Dmitry Kozlyuk wrote:
Windows EAL did not detect IOVA mode and worked incorrectly
if physical addresses could not be obtained
(if virt2phys driver was missing or inaccessible).
In this case, rte_mem_virt2iova() reported RTE_BAD_IOVA for any address.
Inability to obtain IO
> > From a Telemetry usage point of view,
> >
> > Acked-by: Ciara Power
>
> Agree, this patch is much more in keeping with the existing way of working
> than the v1.
>
> Acked-by: Bruce Richardson
Applied, thanks.
1 - 100 of 169 matches
Mail list logo
