The Tx function can not check if the meta data process success for
the process function with void return type. This problem exist for
both NFD3 and NFDk logic.
Chaoyong He (2):
net/nfp: fix meta data process problem of NFD3
net/nfp: fix meta data process problem of NFDk
drivers/net/nfp/nfd3/
The Tx function can not check if the meta data process success for
the process function with void return type.
Fix it by change the return type of the meata data function from
void to integer and add the error handle logic in the Tx function.
Fixes: 962791ba6804 ("net/nfp: support VLAN insert wit
The Tx function can not check if the meta data process success for
the process function with void return type.
Fix it by change the return type of the meata data function from
void to integer and add the error handle logic in the Tx function.
Fixes: 7c82b8626af8 ("net/nfp: support VLAN insert wit
On 2/16/2024 5:07 PM, Andrew Boyer wrote:
> +#if defined(RTE_LIBRTE_IONIC_PMD_BARRIER_ERRATA)
> + /* On some devices the standard 'dmb' barrier is insufficient */
> + asm volatile("dsb st" : : : "memory");
> + rte_write64_relaxed(rte_cpu_to_le_64(val), q->db);
> +#else
> rte_write
Add cache guard to per-lcore data structures to prevent false sharing
in scenarios where a next-N-lines (or similar) hardware prefetcher is
used.
Signed-off-by: Mattias Rönnblom
---
lib/dispatcher/rte_dispatcher.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/dispatcher/rte_dispatcher.
Hi, Ferruh,
Thanks for your review.
On 2024/2/8 1:00, Ferruh Yigit wrote:
On 2/5/2024 10:51 AM, Jie Hai wrote:
This patch adds "filter" and "names" fields to "rte_dev_reg_info"
structure. Names of registers in data fields can be reported and
the registers can be filtered by their names.
For co
> From: Mattias Rönnblom [mailto:mattias.ronnb...@ericsson.com]
> Sent: Tuesday, 20 February 2024 09.35
>
> Add cache guard to per-lcore data structures to prevent false sharing
> in scenarios where a next-N-lines (or similar) hardware prefetcher is
> used.
>
> Signed-off-by: Mattias Rönnblom
>
This RFC presents a new API for static per-lcore id
data allocation.
Please refer to the API documentation for both a
rationale for this new API, and a comparison to the alternatives
available.
The adoption of this API would affect many different DPDK modules, but
the author updated only a few,
Replace keeping PRNG state in a RTE_MAX_LCORE-sized static array of
cache-aligned and RTE_CACHE_GUARDed struct instances with keeping the
same state in a more cache-friendly lcore variable.
RFC v3:
* Remove cache alignment on unregistered threads' rte_rand_state.
(Morten Brørup)
Signed-off-by
Add test suite to exercise the API.
RFC v2:
* Improve alignment-related test coverage.
Signed-off-by: Mattias Rönnblom
---
app/test/meson.build | 1 +
app/test/test_lcore_var.c | 407 ++
2 files changed, 408 insertions(+)
create mode 100644 app/test
Introduce DPDK per-lcore id variables, or lcore variables for short.
An lcore variable has one value for every current and future lcore
id-equipped thread.
The primary use case is for statically allocating
small chunks of often-used data, which is related logically, but where
there are performan
Keep per-lcore power intrinsics state in a lcore variable to reduce
cache working set size and avoid any CPU next-line-prefetching causing
false sharing.
Signed-off-by: Mattias Rönnblom
---
lib/eal/x86/rte_power_intrinsics.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-
Replace static array of cache-aligned structs with an lcore variable,
to slightly benefit code simplicity and performance.
Signed-off-by: Mattias Rönnblom
---
lib/eal/common/rte_service.c | 119 ---
1 file changed, 68 insertions(+), 51 deletions(-)
diff --git a/l
Replace static array of cache-aligned structs with an lcore variable,
to slightly benefit code simplicity and performance.
RFC v3:
* Replace for loop with FOREACH macro.
Signed-off-by: Mattias Rönnblom
---
lib/power/rte_power_pmd_mgmt.c | 36 --
1 file changed,
On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote:
> Introduce DPDK per-lcore id variables, or lcore variables for short.
>
> An lcore variable has one value for every current and future lcore
> id-equipped thread.
>
> The primary use case is for statically allocating
> small chun
From: Pengfei Sun
In function mlx5_dev_configure, dev->data->tx_queues is assigned
to priv->txqs. When a member is removed from a bond, the function
eth_dev_tx_queue_config is called to release dev->data->tx_queues.
However, function mlx5_dev_close will access priv->txqs again and
cause the use a
These are very useful insights Ferruh. I think RTE_LOG_DP() is something
that would have been more suitable here.
Also, the DEBUG statement combined with a statistic will be more useful
than ERR from developer perspective if they see a potential memory leak in
their program.
On Mon, Feb 19, 2024,
On 2024-02-20 10:11, Bruce Richardson wrote:
On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote:
Introduce DPDK per-lcore id variables, or lcore variables for short.
An lcore variable has one value for every current and future lcore
id-equipped thread.
The primary use case is fo
The registers can be dumped through the API rte_eth_dev_get_reg_info.
However, only register values are exported, which is inconvenient
for users to interpret. Therefore, an extension of the structure
"rte_dev_reg_info" and a new API rte_eth_dev_get_reg_info_ext
is added to support the capability o
This patch adds "filter" and "names" fields to "rte_dev_reg_info"
structure. Names of registers in data fields can be reported and
the registers can be filtered by their names.
The new API rte_eth_dev_get_reg_info_ext() is added to support
reporting names and filtering by names. And the original A
This patch adds a telemetry command for registers dump,
and supports get registers with specified names.
The length of the string exported by telemetry is limited
by MAX_OUTPUT_LEN. Therefore, the filter should be more
precise.
An example usage is shown below:
--> /ethdev/regs,0,INTR
{
"/ethdev/
Since the driver is going to support reporting names of
all registers, remove the counter and insert of separators
between different register modules.
Signed-off-by: Jie Hai
---
drivers/net/hns3/hns3_regs.c | 67 ++--
1 file changed, 18 insertions(+), 49 deletions
Since the driver dumps the queue interrupt registers according
to the intr_tqps_num, the counter should be the same.
Fixes: acb3260fac5c ("net/hns3: fix dump register out of range")
Fixes: 936eda25e8da ("net/hns3: support dump register")
Signed-off-by: Jie Hai
Cc: sta...@dpdk.org
---
drivers/ne
This patch adds names for all registers to be dumped.
For those who can be directly accessed by their addresses,
a new structure containing both name and address is added
and the related arrays is refactored and renamed.
For the remaining modules, there may be different meanings
on different platf
This patch supports reporting names of the dfx registers
which filtering them by names.
Signed-off-by: Jie Hai
---
drivers/net/hns3/hns3_regs.c | 277 +--
1 file changed, 230 insertions(+), 47 deletions(-)
diff --git a/drivers/net/hns3/hns3_regs.c b/drivers/net/h
This patch supports reporting names of registers which
can be directly accessed by addresses and filtering
them by names.
Signed-off-by: Jie Hai
---
drivers/net/hns3/hns3_regs.c | 198 +--
1 file changed, 167 insertions(+), 31 deletions(-)
diff --git a/drivers/ne
Since now Inline IPsec in cn9k is using same opcode as LA,
remove the definitions of fast path opcode.
Also fix devarg handling for ipsec_out_max_sa to allow 32-bit.
Fixes: fe5846bcc076 ("net/cnxk: add devargs for min-max SPI")
Signed-off-by: Nithin Dabilpuram
---
v2:
- Fixed commit messages
Define inbound and outbound IPsec data type for PMD API's
rte_pmd_cnxk_hw_sa_read() and rte_pmd_cnxk_hw_sa_write().
Signed-off-by: Nithin Dabilpuram
---
drivers/net/cnxk/cn10k_ethdev_sec.c | 18 +-
drivers/net/cnxk/rte_pmd_cnxk.h | 397 +++-
2 files changed, 411 inse
Add transport mode to security capabilities since it
is supported by UCODE.
Signed-off-by: Nithin Dabilpuram
---
drivers/net/cnxk/cn9k_ethdev_sec.c | 33 ++
1 file changed, 33 insertions(+)
diff --git a/drivers/net/cnxk/cn9k_ethdev_sec.c
b/drivers/net/cnxk/cn9k_ethd
From: Satha Rao
New API to dump detailed SQ entries.
Signed-off-by: Satha Rao
---
drivers/common/cnxk/roc_nix.h | 2 +
drivers/common/cnxk/roc_nix_debug.c | 172
drivers/common/cnxk/version.map | 1 +
3 files changed, 175 insertions(+)
diff --git a/d
From: Satha Rao
New API to dump selected descriptor entries from SQE list.
Signed-off-by: Satha Rao
---
drivers/net/cnxk/cnxk_ethdev.c | 1 +
drivers/net/cnxk/cnxk_ethdev.h | 2 ++
drivers/net/cnxk/cnxk_ethdev_ops.c | 10 ++
3 files changed, 13 insertions(+)
diff --git a/dri
In case where cnxk_nix_mtu_set() is called before
data->min_rx_buf_size is set, use buf size from first RQ's
mempool.
Fixes: 34b46320f446 ("net/cnxk: perform early MTU setup for event mode")
Cc: sta...@dpdk.org
Signed-off-by: Nithin Dabilpuram
---
drivers/net/cnxk/cnxk_ethdev_ops.c | 25 +++
Skip setting Tx MTU separately as now the Tx credit configuration
is based on max MTU possible for that link.
Also init MTU with max value for that port.
Signed-off-by: Nithin Dabilpuram
---
drivers/common/cnxk/roc_nix.c | 2 +-
drivers/common/cnxk/roc_nix.h | 2 --
drivers/net/cnxk/
From: Sunil Kumar Kori
Device can support maximum frame size up to 9212 bytes. While configuring
mtu, overhead is considered as ethernet header size, crc and
2 * (vlan tags) which translates to 26 bytes.
Exposed overhead to the user via rte_eth_dev_info() is 18 bytes which were
leading to set wr
From: Kommula Shiva Shankar
This patch updates queue entries copy in reta table
based on data type
Signed-off-by: Kommula Shiva Shankar
---
drivers/common/cnxk/roc_nix_rss.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/common/cnxk/roc_nix_rss.c
b/drivers/com
Indirect mbuf can be pointing to data from different pool. Use the right
aura in NIX send header in SG2 and SG case.
Fixes: 862e28128707 ("net/cnxk: add vector Tx for CN9K")
Fixes: f71b7dbbf04b ("net/cnxk: add vector Tx for CN10K")
Fixes: 7e95c11df4f1 ("net/cnxk: add multi-segment Tx for CN9K")
Fi
From: Rahul Bhansali
Fix missing check cookies with multi-seg offload case
Fixes: 3626d5195d49 ("net/cnxk: add multi-segment Tx for CN10K")
Cc: sta...@dpdk.org
Signed-off-by: Rahul Bhansali
---
drivers/net/cnxk/cn10k_tx.h | 21 -
1 file changed, 20 insertions(+), 1 deletio
IO attribute is needed to mbox structs to avoid unaligned or pair
access causing by compiler optimization. Add them to structs
where it is missing.
Fixes: 503b82de2cbf ("common/cnxk: add mbox request and response definitions")
Fixes: ddf955d3917e ("common/cnxk: support CPT second pass")
Cc: sta...
Use SQ enable and disable API in TM setup to affect
the state change.
Signed-off-by: Nithin Dabilpuram
---
drivers/common/cnxk/roc_nix_tm_ops.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/common/cnxk/roc_nix_tm_ops.c
b/drivers/common/cnxk/roc_nix_tm_ops.c
ind
On Tue, Feb 20, 2024 at 11:47:14AM +0100, Mattias Rönnblom wrote:
> On 2024-02-20 10:11, Bruce Richardson wrote:
> > On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote:
> > > Introduce DPDK per-lcore id variables, or lcore variables for short.
> > >
> > > An lcore variable has one va
VIRTIO_F_ORDER_PLATFORM is needed feature when working with
real HW platforms that are exposing virtio-net devices
via VDPA framework. This feature helps in having more
real ordering requirements between descriptor updates and
notification data updates. Hence enable it if the
device supports the fe
When packet gets received with error it is reported in CQE
structure and PMD analyzes the error syndrome and provides
two options - either reset the entire queue for the critical
errors, or just ignore the packet.
The non-vectorized rx_burst did not ignore the non-critical
error packets, and in ca
The judgement "obj->callback == NULL" is dead code which can't be
reached, because verify_arg_saver() already make sure obj->callback
must not be NULL when arg->val_saver is NULL.
Signed-off-by: Chengwen Feng
---
app/test/test_argparse.c| 7 ---
lib/argparse/rte_argparse.c | 6 --
2
I found a couple of issues when I revisited the argparse_autotest
output, so got this patchset.
Chengwen Feng (4):
argparse: refine error message
argparse: remove dead code
argparse: fix argument flags operate as uint32 type
test/argparse: refine testcases
app/test/test_argparse.c| 6
The struct rte_argparse_arg's flags was 64bit type, uint64_t should be
used instead of uint32_t where the operation happened.
Also, the flags' bit16 was also unused, so don't test bit16 in testcase
test_argparse_invalid_arg_flags.
Fixes: 6c5c6571601c ("argparse: verify argument config")
Fixes: 31
This patch refines the error message.
Signed-off-by: Chengwen Feng
---
lib/argparse/rte_argparse.c | 31 +--
1 file changed, 17 insertions(+), 14 deletions(-)
diff --git a/lib/argparse/rte_argparse.c b/lib/argparse/rte_argparse.c
index 2d953f1694..48738cd07b 100644
-
Refine testcases, including:
1. add testcase comment.
2. argv[0] should set obj->prog_name.
3. set val_set as NULL in test_argparse_invalid_arg_flags, let it
test to the specified code logic.
4. enable index verification in opt_callback_parse_int_of_no_val.
Fixes: 6c5c6571601c ("argparse: verify a
Hello Patrick,
Note: incorporating a function(s) to load different mlnx device firmware as a
part of the testsuite is an interesting touch. Do you mind explaining why it is
made a part of the testing framework, as opposed to a pre-step for the user to
complete ahead of running the framework? Do
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Tuesday, 20 February 2024 12.39
>
> On Tue, Feb 20, 2024 at 11:47:14AM +0100, Mattias Rönnblom wrote:
> > On 2024-02-20 10:11, Bruce Richardson wrote:
> > > On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote:
> > >
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Sunday, 18 February 2024 19.04
>
> 24/01/2024 12:21, Morten Brørup:
> > --- a/app/test/test_mempool_perf.c
> > +++ b/app/test/test_mempool_perf.c
> > @@ -1,6 +1,6 @@
> > /* SPDX-License-Identifier: BSD-3-Clause
> > * Copyright(c) 2010
Hi,
> -Original Message-
> From: Yunjian Wang
> Sent: Tuesday, February 20, 2024 10:32
> To: dev@dpdk.org
> Cc: Dariusz Sosnowski ; Ori Kam
> ; Matan Azrad ; Slava Ovsiienko
> ; Suanming Mou ;
> luyi...@huawei.com; Pengfei Sun ;
> sta...@dpdk.org
> Subject: [PATCH] net/mlx5: fix use after
Bursts of up to 64 or 128 packets are not uncommon, so increase the
maximum tested get and put burst sizes from 32 to 128.
For convenience, also test get and put burst sizes of
RTE_MEMPOOL_CACHE_MAX_SIZE.
Some applications keep more than 512 objects, so increase the maximum
number of kept objects
> -Original Message-
> From: Slava Ovsiienko
> Sent: Tuesday, February 20, 2024 12:45
> To: dev@dpdk.org
> Cc: Matan Azrad ; Raslan Darawsheh
> ; Ori Kam ; Dariusz Sosnowski
> ; sta...@dpdk.org
> Subject: [PATCH] net/mlx5: fix error packets drop in the regular Rx
>
> When packet gets rece
This patch set contains the mlx5 PMD implementation for NAT64.
Update in v2:
1. separate from the RTE and testpmd common part.
2. reorder the commits.
3. bug fix, code polishing and document update.
Bing Zhao (4):
net/mlx5: fetch the available registers for NAT64
net/mlx5: create NAT64
From: Erez Shitrit
Add support of new action mlx5dr_action_create_nat64.
The new action allows to modify IP packets from version to version, IPV6
to IPV4 and vice versa.
Signed-off-by: Erez Shitrit
Signed-off-by: Bing Zhao
---
drivers/net/mlx5/hws/mlx5dr.h| 29 ++
drivers/net/mlx5/hw
REG_C_6 is used as the 1st one and since it is reserved internally
by default, there is no impact.
The remaining 2 registers will be fetched from the available TAGs
array from right to left. They will not be masked in the array due
to the fact that not all the rules will use NAT64 action.
Signed-
The NAT64 DR actions can be shared among the tables. All these
actions can be created during configuring the flow queues and saved
for the future usage.
Even the actions can be shared now, inside per each flow rule, the
actual hardware resources are unique.
Signed-off-by: Bing Zhao
---
doc/guid
The action will handle the IPv4 and IPv6 headers translation. It will
add / remove IPv6 address prefix by default.
To use the user specific address, another rule to modify the
addresses of the IP header is needed.
Signed-off-by: Bing Zhao
---
drivers/net/mlx5/mlx5_flow_hw.c | 20 +++
NAT64 is treated as a modify header action. The action order and
limitation should be the same as that of modify header in each
domain.
Since the last 2 TAG registers will be used implicitly in the
address backup mode, the values in these registers are no longer
valid after the NAT64 action. The a
This patch set contains the mlx5 PMD implementation for NAT64.
Update in v3:
1. code style and typo.
Update in v2:
1. separate from the RTE and testpmd common part.
2. reorder the commits.
3. bug fix, code polishing and document update.
Bing Zhao (4):
net/mlx5: fetch the available regi
From: Erez Shitrit
Add support of new action mlx5dr_action_create_nat64.
The new action allows to modify IP packets from version to version, IPV6
to IPV4 and vice versa.
Signed-off-by: Erez Shitrit
Signed-off-by: Bing Zhao
---
drivers/net/mlx5/hws/mlx5dr.h| 29 ++
drivers/net/mlx5/hw
REG_C_6 is used as the 1st one and since it is reserved internally
by default, there is no impact.
The remaining 2 registers will be fetched from the available TAGs
array from right to left. They will not be masked in the array due
to the fact that not all the rules will use NAT64 action.
Signed-
The NAT64 DR actions can be shared among the tables. All these
actions can be created during configuring the flow queues and saved
for the future usage.
Even the actions can be shared now, inside per each flow rule, the
actual hardware resources are unique.
Signed-off-by: Bing Zhao
---
doc/guid
NAT64 is treated as a modify header action. The action order and
limitation should be the same as that of modify header in each
domain.
Since the last 2 TAG registers will be used implicitly in the
address backup mode, the values in these registers are no longer
valid after the NAT64 action. The a
The action will handle the IPv4 and IPv6 headers translation. It will
add / remove IPv6 address prefix by default.
To use the user specific address, another rule to modify the
addresses of the IP header is needed.
Signed-off-by: Bing Zhao
---
drivers/net/mlx5/mlx5_flow_hw.c | 20 +++
> On Feb 20, 2024, at 2:28 AM, Ferruh Yigit wrote:
>
> On 2/16/2024 5:07 PM, Andrew Boyer wrote:
>> +#if defined(RTE_LIBRTE_IONIC_PMD_BARRIER_ERRATA)
>> + /* On some devices the standard 'dmb' barrier is insufficient */
>> + asm volatile("dsb st" : : : "memory");
>> + rte_write64_relaxed(rte_cp
On Tue, 20 Feb 2024 18:58:17 +0800
Jie Hai wrote:
> +* **Added support for dumping regiters with names and filter.**
Spelling
On Tue, 20 Feb 2024 18:58:17 +0800
Jie Hai wrote:
> This patch adds "filter" and "names" fields to "rte_dev_reg_info"
> structure. Names of registers in data fields can be reported and
> the registers can be filtered by their names.
>
> The new API rte_eth_dev_get_reg_info_ext() is added to supp
On Tue, 20 Feb 2024 18:58:17 +0800
Jie Hai wrote:
> @@ -20,6 +25,12 @@ struct rte_dev_reg_info {
> uint32_t length; /**< Number of registers to fetch */
> uint32_t width; /**< Size of device register */
> uint32_t version; /**< Device version */
> + /**
> + * Filter for
On Tue, 20 Feb 2024 18:58:17 +0800
Jie Hai wrote:
> int
> rte_eth_dev_get_reg_info(uint16_t port_id, struct rte_dev_reg_info *info)
> +{
> + struct rte_dev_reg_info reg_info = { 0 };
> + int ret;
> +
> + if (info == NULL) {
> + RTE_ETHDEV_LOG_LINE(ERR,
> +
Hi all,
I want to poll the CI group and dev community about a proposed feature
addition to the CI retest request framework. Currently, you can respond to
a patchseries or patch email, requesting a retest like so:
Recheck-request: iol-compile-amd64-testing, iol-unit-amd64-testing
Labs who have ad
> From: Mattias Rönnblom [mailto:mattias.ronnb...@ericsson.com]
> Sent: Tuesday, 20 February 2024 09.49
>
[...]
> @@ -124,11 +129,10 @@ struct rte_rand_state *__rte_rand_get_state(void)
>
> idx = rte_lcore_id();
>
> - /* last instance reserved for unregistered non-EAL threads */
>
This patchset refactors the power management library, addressing both
core and uncore power management. The primary changes involve the creation
of dedicated directories for each driver within 'drivers/power/core/*' and
'drivers/power/uncore/*'.
This refactor significantly improves code organiza
This patch introduces a comprehensive refactor to the core power
management library. The primary focus is on improving modularity
and organization by relocating specific driver implementations
from the 'lib/power' directory to dedicated directories within
'drivers/power/core/*'. The adjustment of m
This patchset refactors the power management library, addressing both
core and uncore power management. The primary changes involve the creation
of dedicated directories for each driver within 'drivers/power/core/*' and
'drivers/power/uncore/*'.
This refactor significantly improves code organiza
This patch refactors the power management library, addressing uncore
power management. The primary changes involve the creation of dedicated
directories for each driver within 'drivers/power/uncore/*'. The
adjustment of meson.build files enables the selective activation
of individual drivers.
This
On 2024-02-20 12:39, Bruce Richardson wrote:
On Tue, Feb 20, 2024 at 11:47:14AM +0100, Mattias Rönnblom wrote:
On 2024-02-20 10:11, Bruce Richardson wrote:
On Tue, Feb 20, 2024 at 09:49:03AM +0100, Mattias Rönnblom wrote:
Introduce DPDK per-lcore id variables, or lcore variables for short.
An
On Sat, Feb 10, 2024 at 08:24:29AM +0100, Mattias Rönnblom wrote:
> On 2024-02-09 09:43, Jerin Jacob wrote:
> > On Thu, Feb 8, 2024 at 3:20 PM Mattias Rönnblom
> > wrote:
> > >
> > > On 2024-02-07 11:14, Jerin Jacob wrote:
> > > > On Fri, Feb 2, 2024 at 7:29 PM Bruce Richardson
> > > > wrote:
>
On Wed, Feb 07, 2024 at 03:44:37PM +0530, Jerin Jacob wrote:
> On Fri, Feb 2, 2024 at 7:29 PM Bruce Richardson
> wrote:
> >
> > Make some textual improvements to the introduction to eventdev and event
> > devices in the eventdev header file. This text appears in the doxygen
> > output for the head
On Wed, Feb 07, 2024 at 04:00:04PM +0530, Jerin Jacob wrote:
> On Sat, Feb 3, 2024 at 12:59 PM Bruce Richardson
> wrote:
> >
> > Update the device capability docs, to:
> >
> > * include more cross-references
> > * split longer text into paragraphs, in most cases with each flag having
> > a singl
On Sun, Feb 18, 2024 at 06:38:22PM +0100, Thomas Monjalon wrote:
> 10/01/2024 17:58, Tyler Retzlaff:
> > On Wed, Jan 10, 2024 at 03:01:03PM +, Bruce Richardson wrote:
> > > The default behaviour of "ld.lld" has changed, so it now prints out
> > > warnings about entries in the version.map file w
On Sun, Feb 18, 2024 at 01:39:52PM +0100, Thomas Monjalon wrote:
> 15/02/2024 07:21, Tyler Retzlaff:
> > Provide a macro that allows conditional expansion of RTE_MARKER fields
> > to empty to allow rte_mbuf to be used with MSVC. It is proposed that
> > we announce the fields to be __rte_deprecated
On Thu, Feb 08, 2024 at 11:04:03AM +0100, Mattias Rönnblom wrote:
> On 2024-02-08 10:18, Jerin Jacob wrote:
> > On Fri, Feb 2, 2024 at 6:11 PM Bruce Richardson
> > wrote:
> > >
> > > The description of ordered and atomic scheduling given in the eventdev
> > > doxygen documentation was not always
On Sun, Feb 18, 2024 at 04:22:15PM +0100, Thomas Monjalon wrote:
> 18/02/2024 14:07, Morten Brørup:
> > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > > 15/02/2024 07:21, Tyler Retzlaff:
> > > > --- a/lib/eal/include/rte_common.h
> > > > +++ b/lib/eal/include/rte_common.h
> > > > @@ -582,6
On Fri, Feb 09, 2024 at 02:44:04PM +0530, Jerin Jacob wrote:
> On Fri, Feb 2, 2024 at 6:11 PM Bruce Richardson
> wrote:
> >
> > Clarify the meaning of the NEW, FORWARD and RELEASE event types.
> > For the fields in "rte_event" struct, enhance the comments on each to
> > clarify the field's use, an
On Fri, Feb 09, 2024 at 02:44:04PM +0530, Jerin Jacob wrote:
> On Fri, Feb 2, 2024 at 6:11 PM Bruce Richardson
> wrote:
> >
> > Clarify the meaning of the NEW, FORWARD and RELEASE event types.
> > For the fields in "rte_event" struct, enhance the comments on each to
> > clarify the field's use, an
On Sun, Feb 18, 2024 at 05:44:48PM +0100, Thomas Monjalon wrote:
> 18/02/2024 17:38, Morten Brørup:
> > > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > > Sent: Sunday, 18 February 2024 16.35
> > >
> > > 18/02/2024 13:53, Morten Brørup:
> > > > > From: Thomas Monjalon [mailto:tho...@monjal
20/02/2024 18:20, Tyler Retzlaff:
> On Sun, Feb 18, 2024 at 01:39:52PM +0100, Thomas Monjalon wrote:
> > 15/02/2024 07:21, Tyler Retzlaff:
> > > Provide a macro that allows conditional expansion of RTE_MARKER fields
> > > to empty to allow rte_mbuf to be used with MSVC. It is proposed that
> > > we
On Fri, Feb 09, 2024 at 02:44:04PM +0530, Jerin Jacob wrote:
> On Fri, Feb 2, 2024 at 6:11 PM Bruce Richardson
> wrote:
> >
> > Clarify the meaning of the NEW, FORWARD and RELEASE event types.
> > For the fields in "rte_event" struct, enhance the comments on each to
> > clarify the field's use, an
On Sun, Feb 18, 2024 at 04:31:50PM +0100, Thomas Monjalon wrote:
> 18/02/2024 15:51, Mattias Rönnblom:
> > On 2024-02-18 13:24, Thomas Monjalon wrote:
> > > 15/02/2024 23:20, Tyler Retzlaff:
> > >> Provide a new macro __rte_attribute(a) that when directly used
> > >> compiles to empty for MSVC and
Patrick Robb writes:
> Hi all,
>
> I want to poll the CI group and dev community about a proposed feature
> addition to the CI retest request framework.
> Currently, you can respond to a patchseries or patch email, requesting a
> retest like so:
>
> Recheck-request: iol-compile-amd64-testing, i
On Tue, Feb 20, 2024 at 1:12 PM Aaron Conole wrote:
>
> Why not something like:
>
> Recheck-request: [attribute-list],[test-list]...
>
> For example, then we can do:
>
> Recheck-request: rebase=[identifier],
>
> where identifier is a branch specifier (or the word 'latest')?
>
I hadn't thought
20/02/2024 19:06, Tyler Retzlaff:
> On Sun, Feb 18, 2024 at 04:31:50PM +0100, Thomas Monjalon wrote:
> > 18/02/2024 15:51, Mattias Rönnblom:
> > > On 2024-02-18 13:24, Thomas Monjalon wrote:
> > > > 15/02/2024 23:20, Tyler Retzlaff:
> > > >> Provide a new macro __rte_attribute(a) that when directly
On Feb 19, 2024, at 9:02 PM, Wathsala Wathawana Vithanage
wrote:
Caution: This message originated from an External Source. Use proper caution
when opening attachments, clicking links, or responding.
-Original Message-
From: Wathsala Wathawana Vithanage
mailto:wathsala.vithan...@arm
I appreciate that you gave me suggestions and comments. I will make changes
according to all your recommendations, but before that, I want to make
everyone's minds clear. Then, I will apply modifications.
On Tue, Feb 20, 2024 at 2:35 AM Honnappa Nagarahalli <
honnappa.nagaraha...@arm.com> wrote:
> Not sure if we want to do the same. Two reasons.
>
> 1. Searching the netvsc source, I don't see a place that it set
> hv->vlan_strip to
> false. It means !hv->vlan_string is always false, and rte_vlan_insert(&m)
> never
> run.
It's set here:
drivers/net/netvsc/hn_ethdev.c: hv->vlan_strip = !
20/02/2024 18:53, Thomas Monjalon:
> 20/02/2024 18:20, Tyler Retzlaff:
> > On Sun, Feb 18, 2024 at 01:39:52PM +0100, Thomas Monjalon wrote:
> > > 15/02/2024 07:21, Tyler Retzlaff:
> > > > Provide a macro that allows conditional expansion of RTE_MARKER fields
> > > > to empty to allow rte_mbuf to be
On Tue, 20 Feb 2024 03:29:04 +
bugzi...@dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=1381
>
> Bug ID: 1381
>Summary: TAP device can not support 17 queues
>Product: DPDK
>Version: 23.11
> Hardware: All
> OS: A
On Tue, Feb 20, 2024 at 08:16:23PM +0100, Thomas Monjalon wrote:
> 20/02/2024 18:53, Thomas Monjalon:
> > 20/02/2024 18:20, Tyler Retzlaff:
> > > On Sun, Feb 18, 2024 at 01:39:52PM +0100, Thomas Monjalon wrote:
> > > > 15/02/2024 07:21, Tyler Retzlaff:
> > > > > Provide a macro that allows conditio
https://bugs.dpdk.org/show_bug.cgi?id=1382
Bug ID: 1382
Summary: tap device does not support multiple flow rules with
same priority
Product: DPDK
Version: 23.11
Hardware: All
OS: All
Status: UNCO
1 - 100 of 129 matches
Mail list logo
