On Sat, Oct 24, 2020 at 6:18 PM Honnappa Nagarahalli
wrote:
>
> Hi David,
> Checkpatch CI is showing "WARNING" on a lot of the patches in this
> series, but it does not list any real warnings. Any idea what is happening?
I reported it to Thomas last night.
Thomas has fixed a few things
Current dynamic mbuf design is that the driver will register the needed
field and flags at the device probing time, this will make iavf PMD use
different names to register the dynamic mbuf field and flags, but both
of them use the exactly same protocol extraction metadata.
This will run out of the
25/10/2020 08:16, David Marchand:
> On Sat, Oct 24, 2020 at 6:18 PM Honnappa Nagarahalli
> wrote:
> >
> > Hi David,
> > Checkpatch CI is showing "WARNING" on a lot of the patches in this
> > series, but it does not list any real warnings. Any idea what is happening?
>
> I reported it to
Hi,
> -Original Message-
> From: dev On Behalf Of Andrey Vesnovaty
> Sent: Friday, October 23, 2020 1:24 PM
> To: dev@dpdk.org
> Cc: j...@marvell.com; jerinjac...@gmail.com; NBU-Contact-Thomas
> Monjalon ; ferruh.yi...@intel.com;
> step...@networkplumber.org; bruce.richard...@intel.com; O
Tunnel Offload API provides hardware independent, unified model
to offload tunneled traffic. Key model elements are:
- apply matches to both outer and inner packet headers
during entire offload procedure;
- restore outer header of partially offloaded packet;
- model is implemented as a set of
Hi,
> -Original Message-
> From: Gregory Etelson
> Sent: Sunday, October 25, 2020 4:08 PM
> To: dev@dpdk.org
> Cc: Gregory Etelson ; Matan Azrad
> ; Raslan Darawsheh ; Eli Britstein
> ; Oz Shlomo ; Slava Ovsiienko
> ; Shahaf Shuler
> Subject: [PATCH v5] net/mlx5: implement tunnel offload
The fields ``has_vlan`` and ``has_more_vlan`` were added in rte_flow by
patch [1].
Using these fields, the application can match all the VLAN options by
single flow: any, VLAN only and non-VLAN only.
Add the support for the fields.
By the way, add the support for QinQ packets matching.
VLAN\QinQ
Hello Wei Hu,
> diff --git a/drivers/net/hns3/meson.build b/drivers/net/hns3/meson.build
> index bf69ad4..ca0f21a 100644
> --- a/drivers/net/hns3/meson.build
> +++ b/drivers/net/hns3/meson.build
> @@ -31,4 +31,9 @@ deps += ['hash']
>
> if arch_subdir == 'arm' and dpdk_conf.get('RTE_ARCH_64')
>
Hello Leyi, Qi, Ferruh,
On Fri, Oct 23, 2020 at 6:37 AM Leyi Rong wrote:
> diff --git a/drivers/net/ice/meson.build b/drivers/net/ice/meson.build
> index 254595af85..85e8baf912 100644
> --- a/drivers/net/ice/meson.build
> +++ b/drivers/net/ice/meson.build
> @@ -34,6 +34,17 @@ if arch_subdir == 'x
This patch series changes the use of the terms blacklist and whitelist
and instead uses block and allow. The change is most visible
in the options passed to DPDK programs for marking which devices
to use.
The options are also shortened because they can be used for
not just PCI devices. When DPDK
Use the new terminology blocked to describe when devices
are excluded from being used.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
Acked-by: Hemant Agrawal
---
drivers/bus/dpaa/dpaa_bus.c| 7 +++
drivers/bus/fslmc/fslmc_bus.c | 9 -
drivers/bus/fslmc/fsl
Replace -w / --pci-whitelist with -a / --allow options
and --pci-blacklist with --block.
The -b short option remains unchanged.
Allow the old options for now, but print a nag
warning since old options are deprecated.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
lib/librte_eal/c
This patch renames the enum values in the EAL include files.
As a backward compatible temporary migration tool, define
a replacement mapping for old values.
The old names relating to blacklist and whitelist are replaced
by block list and allow list, but applications may be using the
older compatib
There are two areas where documentation needed update.
The first was use of whitelist when describing address
filtering.
The other is the legacy -w whitelist option for PCI
which is used in many examples
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
doc/guides/cryptodevs/dpaa2_s
Test the renamed blocklist and allowlist arguments.
Use new terms in test variable names as well.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
app/test/autotest.py| 16 ++--
app/test/autotest_runner.py | 18 ++---
app/test/test.c | 2 +-
app/
Add type argument to dir24_8_get_lookup_fn()
Now it supports 3 different lookup implementations:
RTE_FIB_DIR24_8_SCALAR_MACRO
RTE_FIB_DIR24_8_SCALAR_INLINE
RTE_FIB_DIR24_8_SCALAR_UNI
Add new rte_fib_set_lookup_fn() - user can change lookup
function type runtime.
Signed-off-by: Vladimir Medvedk
This patch series implements vectorized lookup using AVX512 for
ipv4 dir24_8 and ipv6 trie algorithms.
Also introduced rte_fib_set_lookup_fn() to change lookup function type.
Added option to select lookup function type in testfib application.
v14:
- remove unnecessary FIB types
v13:
- reflect t
Add type argument to trie_get_lookup_fn()
Now it only supports RTE_FIB6_TRIE_SCALAR
Add new rte_fib6_set_lookup_fn() - user can change lookup
function type runtime.
Signed-off-by: Vladimir Medvedkin
Acked-by: Konstantin Ananyev
---
lib/librte_fib/rte_fib6.c | 20 +++-
lib/libr
Move dir24_8 table layout and lookup definition into the
private header file. This is necessary for implementing a
vectorized lookup function in a separate .с file.
Signed-off-by: Vladimir Medvedkin
Acked-by: Konstantin Ananyev
---
lib/librte_fib/dir24_8.c | 225 +---
Add new lookup implementation for DIR24_8 algorithm using
AVX512 instruction set
Signed-off-by: Vladimir Medvedkin
Acked-by: Konstantin Ananyev
---
doc/guides/rel_notes/release_20_11.rst | 3 +
lib/librte_fib/dir24_8.c | 39
lib/librte_fib/dir24_8_avx512.c| 165
Move trie table layout and lookup definition into the
private header file. This is necessary for implementing a
vectorized lookup function in a separate .с file.
Signed-off-by: Vladimir Medvedkin
Acked-by: Konstantin Ananyev
---
lib/librte_fib/trie.c | 121 --
Add new lookup implementation for FIB6 trie algorithm using
AVX512 instruction set
Signed-off-by: Vladimir Medvedkin
Acked-by: Konstantin Ananyev
---
doc/guides/rel_notes/release_20_11.rst | 2 +-
lib/librte_fib/meson.build | 17 +++
lib/librte_fib/rte_fib6.c | 2 +
Added -v option to switch between different lookup implementations
to measure their performance and correctness.
Signed-off-by: Vladimir Medvedkin
---
app/test-fib/main.c | 65 ++---
1 file changed, 62 insertions(+), 3 deletions(-)
diff --git a/ap
FIB type RTE_FIB_TYPE_MAX is used only for sanity checks,
remove it to prevent applications start using it.
The same is for FIB6's RTE_FIB6_TYPE_MAX.
Signed-off-by: Vladimir Medvedkin
---
app/test/test_fib.c | 2 +-
app/test/test_fib6.c | 2 +-
lib/librte_fib/rte_fib.c | 2 +-
lib/li
29/03/2019 16:09, Burakov, Anatoly:
> On 29-Mar-19 2:14 PM, Thomas Monjalon wrote:
> > 18/03/2019 12:56, Hajkowski:
> >> From: Marcin Hajkowski
> >> --- a/doc/guides/rel_notes/release_19_05.rst
> >> +++ b/doc/guides/rel_notes/release_19_05.rst
> >> @@ -120,6 +120,8 @@ API Changes
> >> + * power:
On Sun, Oct 25, 2020 at 5:59 PM Stephen Hemminger
wrote:
> @@ -61,7 +61,7 @@ do_recursive_call(void)
> { "test_main_lcore_flag", no_action },
> { "test_invalid_n_flag", no_action },
> { "test_no_hpet_flag", no_action },
> -
This patch series changes the use of the terms blacklist and whitelist
and instead uses block and allow. The change is most visible
in the options passed to DPDK programs for marking which devices
to use.
The options are also shortened because they can be used for
not just PCI devices. When DPDK
Use the new terminology blocked to describe when devices
are excluded from being used.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
Acked-by: Hemant Agrawal
---
drivers/bus/dpaa/dpaa_bus.c| 7 +++
drivers/bus/fslmc/fslmc_bus.c | 9 -
drivers/bus/fslmc/fsl
Replace -w / --pci-whitelist with -a / --allow options
and --pci-blacklist with --block.
The -b short option remains unchanged.
Allow the old options for now, but print a nag
warning since old options are deprecated.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
lib/librte_eal/c
This patch renames the enum values in the EAL include files.
As a backward compatible temporary migration tool, define
a replacement mapping for old values.
The old names relating to blacklist and whitelist are replaced
by block list and allow list, but applications may be using the
older compatib
There are two areas where documentation needed update.
The first was use of whitelist when describing address
filtering.
The other is the legacy -w whitelist option for PCI
which is used in many examples
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
doc/guides/cryptodevs/dpaa2_s
Test the renamed blocklist and allowlist arguments.
Use new terms in test variable names as well.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
app/test/autotest.py| 16 +--
app/test/autotest_runner.py | 18 ++---
app/test/test.c | 2 +-
app/t
This patch series changes the use of the terms blacklist and whitelist
and instead uses block and allow. The change is most visible
in the options passed to DPDK programs for marking which devices
to use.
The options are also shortened because they can be used for
not just PCI devices. When DPDK
Replace -w / --pci-whitelist with -a / --allow options
and --pci-blacklist with --block.
The -b short option remains unchanged.
Allow the old options for now, but print a nag
warning since old options are deprecated.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
lib/librte_eal/c
Use the new terminology blocked to describe when devices
are excluded from being used.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
Acked-by: Hemant Agrawal
---
drivers/bus/dpaa/dpaa_bus.c| 7 +++
drivers/bus/fslmc/fslmc_bus.c | 9 -
drivers/bus/fslmc/fsl
This patch renames the enum values in the EAL include files.
As a backward compatible temporary migration tool, define
a replacement mapping for old values.
The old names relating to blacklist and whitelist are replaced
by block list and allow list, but applications may be using the
older compatib
There are two areas where documentation needed update.
The first was use of whitelist when describing address
filtering.
The other is the legacy -w whitelist option for PCI
which is used in many examples
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
doc/guides/cryptodevs/dpaa2_s
Test the renamed blocklist and allowlist arguments.
Use new terms in test variable names as well.
Signed-off-by: Stephen Hemminger
Acked-by: Luca Boccassi
---
app/test/autotest.py| 16 +--
app/test/autotest_runner.py | 18 ++---
app/test/test.c | 2 +-
app/t
On Sun, 25 Oct 2020 19:47:16 +0100
David Marchand wrote:
> On Sun, Oct 25, 2020 at 5:59 PM Stephen Hemminger
> wrote:
> > @@ -61,7 +61,7 @@ do_recursive_call(void)
> > { "test_main_lcore_flag", no_action },
> > { "test_invalid_n_flag", no_action },
On Tue, Oct 20, 2020 at 6:43 PM David Marchand
wrote:
>
> Hello,
Hi
>
> On Sat, Sep 12, 2020 at 9:53 PM Gaëtan Rivet wrote:
> >
> > On 08/07/20 17:03 +0500, Muhammad Bilal wrote:
> > > while using memif with app, the resources are not cleaned on exit,
> > > So an error occurred on running it seco
At 2020-10-23 22:46:42, "Ananyev, Konstantin"
wrote:
>> From: yang_y_yi
>> Sent: Friday, October 23, 2020 2:18 PM
>> To: Ananyev, Konstantin
>> Cc: dev@dpdk.org; Hu, Jiayu ; techbo...@dpdk.org;
>> tho...@monjalon.net; yangy...@inspur.com
>> Subject: Re:RE: [PATCH v2] gso: fix free issue of mbu
> -Original Message-
> From: Zhang, Tianfei
> Sent: Friday, October 23, 2020 5:00 PM
> To: dev@dpdk.org; Xu, Rosen ; Zhang, Qi Z
>
> Cc: Zhang, Tianfei
> Subject: [PATCH v3 0/5] raw/ifpga/base: An improvement for multi-process
>
> This patches set will improve the ifpga base driver r
> -Original Message-
> From: Jesse Brandeburg
> Sent: Saturday, October 24, 2020 4:22 AM
> To: Johnson, Brian ; tho...@monjalon.net;
> david.march...@redhat.com
> Cc: Brandeburg, Jesse ; dev@dpdk.org; Zhang,
> Qi Z
> Subject: [PATCH v2 0/2] intel: fix writeback
>
> This patch series i
On Mon, Oct 26, 2020 at 08:57:30AM +0800, yang_y_yi wrote:
> At 2020-10-23 22:46:42, "Ananyev, Konstantin"
> wrote:
>
> >> From: yang_y_yi
> >> Sent: Friday, October 23, 2020 2:18 PM
> >> To: Ananyev, Konstantin
> >> Cc: dev@dpdk.org; Hu, Jiayu ; techbo...@dpdk.org;
> >> tho...@monjalon.net; y
Thanks Shougang,
Yes, I will update them.
BR,
Alvin
> -Original Message-
> From: Wang, ShougangX
> Sent: Friday, October 23, 2020 4:43 PM
> To: Zhang, AlvinX ; dev@dpdk.org
> Subject: RE: [dpdk-dev] [RFC] net/i40e: refactor of hash flow
>
> Hi, Alvin
>
> > -Original Message-
>
At 2020-10-26 10:06:09, "Jiayu Hu" wrote:
>On Mon, Oct 26, 2020 at 08:57:30AM +0800, yang_y_yi wrote:
>> At 2020-10-23 22:46:42, "Ananyev, Konstantin"
>> wrote:
>>
>> >> From: yang_y_yi
>> >> Sent: Friday, October 23, 2020 2:18 PM
>> >> To: Ananyev, Konstantin
>> >> Cc: dev@dpdk.org; Hu, Jiayu
In examples, DPDK header files are external,
so they must be enclosed with angle brackets, not quotes.
Signed-off-by: Thomas Monjalon
---
examples/bbdev_app/main.c | 30 +-
examples/bond/main.c | 11 --
examples/tep_termination/vxlan
The mbuf field userdata (aliased as udata64)
was announced to be removed for two reasons:
- applications, libraries and drivers used the same field
for different purposes, with a risk of usage conflict.
- this field always used 8 bytes even if unneeded
Some dynamic fields are created when
Since the kernel module is not part of EAL anymore,
there is no need to have the common KNI header file in EAL.
The file rte_kni_common.h is moved to librte_kni.
Signed-off-by: Thomas Monjalon
---
kernel/linux/kni/meson.build | 2 +-
lib/librte_eal/linux/include/
Replace "in a in PMD" with "in a PMD".
Fixes: 4958ca3a443a ("mbuf: support dynamic fields and flags")
Cc: sta...@dpdk.org
Signed-off-by: Thomas Monjalon
---
lib/librte_mbuf/rte_mbuf_dyn.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_mbuf/rte_mbuf_dyn.h b/lib/li
The test worker_loopback used the deprecated mbuf field udata64.
It is moved to a dynamic field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
drivers/event/sw/sw_evdev_selftest.c | 22 +++---
1 file changed, 19 insertions(+), 3 deletions(-)
diff --git
The device-specific metadata was stored in the deprecated field udata64.
It is moved to a dynamic mbuf field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
doc/guides/prog_guide/rte_security.rst| 9 +
drivers/crypto/octeontx2/otx2_cryptodev_sec.c | 5 +
The node_mbuf_priv1 was stored in the deprecated mbuf field udata64.
It is moved to a dynamic field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
lib/librte_node/ip4_lookup.c | 7 +++
lib/librte_node/ip4_rewrite.c | 10 ++
lib/librte_node/node_private.h
The second field of metadata is reserved for user data
which is a deprecated mbuf field.
The usage of mbuf udata64 is removed
and the corresponding ark metadata field is annotated as ignored.
Signed-off-by: Thomas Monjalon
---
drivers/net/ark/ark_ddm.h | 2 +-
drivers/net/ark/ark_ethdev_rx
The segment count, used for MSS guess,
was stored in the deprecated mbuf field udata64.
It is moved to a dynamic field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
drivers/net/vmxnet3/vmxnet3_ethdev.c | 15 +++
drivers/net/vmxnet3/vmxnet3_ethdev.h | 2 ++
The CFA code from mark was stored in the deprecated mbuf field udata64.
It is moved to a dynamic field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
drivers/net/bnxt/bnxt_ethdev.c | 19 +++
drivers/net/bnxt/bnxt_rxr.c | 5 -
drivers/net/bnxt/b
The test used the deprecated mbuf field udata64.
It is moved to a dynamic field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
app/test/test_graph.c | 93 +--
1 file changed, 55 insertions(+), 38 deletions(-)
diff --git a/app/tes
The test used the deprecated mbuf field udata64.
It is moved to a dynamic field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
app/test/test_distributor.c | 27 ++-
1 file changed, 22 insertions(+), 5 deletions(-)
diff --git a/app/test/test_dist
The order test stored the flow ID in the deprecated mbuf field udata64.
It is moved to a dynamic field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
app/test-eventdev/test_order_atq.c| 4 ++--
app/test-eventdev/test_order_common.c | 16 +++-
app/test-e
The example used the deprecated mbuf field udata64 as input mbuf pointer.
It is moved to a dynamic field in order to allow removal of udata64.
Signed-off-by: Thomas Monjalon
---
examples/bbdev_app/main.c | 37 +++--
1 file changed, 27 insertions(+), 10 deletions(-
The example used the deprecated mbuf field udata64.
It is moved to a dynamic field in order to allow removal of udata64.
Note: RTE_MBUF_DYNFIELD_TIMESTAMP_NAME is an existing mbuf field name.
Signed-off-by: Thomas Monjalon
---
doc/guides/sample_app_ug/rxtx_callbacks.rst | 4 ++--
examples/rxtx
As announced in the deprecation note, the field userdata / udata64
is removed to give more space to the dynamic fields.
Signed-off-by: Thomas Monjalon
---
doc/guides/rel_notes/deprecation.rst | 1 -
doc/guides/rel_notes/release_20_11.rst | 3 +++
lib/librte_kni/rte_kni_common.h| 3 +--
On Mon, Oct 26, 2020 at 10:12:24AM +0800, yang_y_yi wrote:
> At 2020-10-26 10:06:09, "Jiayu Hu" wrote:
>
> >On Mon, Oct 26, 2020 at 08:57:30AM +0800, yang_y_yi wrote:
> >> At 2020-10-23 22:46:42, "Ananyev, Konstantin"
> >>
> >> wrote:
> >>
> >> >> From: yang_y_yi
> >> >> Sent: Friday, October
From: Beilei Xing
Currently, can't create more than one following flow for
ETH + VLAN pattern.
1. flow create 0 ingress pattern eth / vlan vid is 350 / end
actions queue index 2 / end
2. flow create 0 ingress pattern eth / vlan vid is 351 / end
actions queue index 3 / end
The root cause i
From: Yi Yang
rte_gso_segment decreased refcnt of pkt by one, but
it is wrong if pkt is external mbuf, pkt won't be
freed because of incorrect refcnt, the result is
application can't allocate mbuf from mempool because
mbufs in mempool are run out of.
One correct way is application should call
rt
65 matches
Mail list logo
