Fix one return value check problem found by the CI.
Coverity issue: 445519
Fixes: 08ea495d624b ("net/nfp: support loading firmware from flash")
Cc: sta...@dpdk.org
Signed-off-by: Chaoyong He
Reviewed-by: Peng Zhang
---
drivers/net/nfp/nfp_ethdev.c | 8 +++-
1 file changed, 7 insertions(+),
Hi Robin,
See inline comments
Thanks,
Nitin
On Thu, Oct 17, 2024 at 1:20 PM Robin Jarry wrote:
>
> Hi Nitin, all,
>
> Nitin Saxena, Oct 17, 2024 at 09:03:
> > Hi Robin/David and all,
> >
> > We realized the feature arc patch series is difficult to understand as
> > a new concept. Our objectives
Release status meeting minutes 2024-10-17
=
Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens
Participants:
* AMD
* ARM
* Intel
* Marvell
* Nvidia
* Red Hat
Release Dates
-
The following are the current/updated working dat
The mempool cache size of mbuf is set to
RTE_MEMPOOL_CACHE_MAX_SIZE as default. This patch allows
users to configure the cache size by "--mbcache", and limits
the paramater to a maximum of RTE_MEMPOOL_CACHE_MAX_SIZE.
Signed-off-by: Jie Hai
---
examples/l3fwd/l3fwd.h | 1 +
examples/l3fwd/main.c
Now the Rx burst size is fixed to MAX_PKT_BURST (32). This
parameter needs to be modified in some performance optimization
scenarios. So an option '--burst' is added to set the burst size
explicitly. The default value is DEFAULT_PKT_BURST (32) and maximum
value is MAX_PKT_BURST (512).
Signed-off-b
Add options to support configuring RX burst size and cache size
of mbuf mempoool.
Jie Hai (2):
examples/l3fwd: add option to set RX burst size
examples/l3fwd: add option to set mbuf cache size
examples/l3fwd/l3fwd.h | 8 +++-
examples/l3fwd/l3fwd_acl.c | 2 +-
examples/l3fwd/l3fwd_em.c
For the series,
Acked-by: Morten Brørup
Introduce ZTE Storage Data Accelerator(ZSDA) drivers
which can help accelerate storage data process.
The official product documenttation web page is:
https://enterprise.zte.com.cn/products.html?id=101
It is recommended to update MAINTAINERS in the
first patch in the new PMD guidelines.
https://pa
Introduce common functions and logging macros.
This patch may have warning:
Warning in drivers/common/zsda/zsda_logs.h:
Do not use variadic argument pack in macros
However, the usage is same to CCP_LOG_ERR which
is in ccp_pmd_private and is merged before 4 mouths.
Signed-off-by: Hanxiao Li
--
Add support for zsdadev queue enqueue.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/zsda_qp.c | 105 ++
drivers/common/zsda/zsda_qp.h | 2 +
2 files changed, 107 insertions(+)
diff --git a/drivers/common/zsda/zsda_qp.c b/drivers/common/zsda/zsda_qp.c
index
The patch provides a series of interfaces for managing
and controlling the configuration, start, stop,
resource management, etc. of compression devices.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/meson.build | 2 +-
drivers/compress/zsda/zsda_comp_pmd.c | 464 +
The patchset adds support for wqe configuration
of compress and decompress, preliminary verification of results
and preparation of checksums.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/meson.build | 12 +-
drivers/compress/zsda/zsda_comp.c | 392 ++
drivers/
The patchset adds support for wqe configuration
of encrypto and decrypto, preliminary verification of results
and preparation of checksums.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/meson.build | 2 +-
drivers/crypto/zsda/zsda_sym.c | 273
drivers/cryp
The patch provides a series of interfaces for driver probe remove,etc.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/meson.build | 1 +
drivers/common/zsda/zsda_device.c | 263 ++
drivers/common/zsda/zsda_device.h | 112 +
3 files changed, 376 inse
Add support for zsdadev queue dequeue.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/zsda_qp.c | 56 +++
drivers/common/zsda/zsda_qp.h | 1 +
2 files changed, 57 insertions(+)
diff --git a/drivers/common/zsda/zsda_qp.c b/drivers/common/zsda/zsda_qp.c
index 8
v11:
- use RTE_LOG_LINE in logging macro.
- fix some known bugs.
v10:
- delete new blank line at EOF
- Cleaning up some code in zsda_log.h
v9:
- add a new feature in default.ini.
- Re-split the patch according to the new PMD guidelines
https://patches.dpdk.org/project/dpdk/patch/20241006184
254.
The patch provides a series of interfaces for managing
and controlling the configuration, start, stop,
resource management, etc. of crypto devices.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/meson.build | 2 +-
drivers/crypto/zsda/zsda_sym_capabilities.h | 111 +
drivers
Add support for zsdadev queue interfaces,
including queue start, stop, create, remove, etc.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/meson.build | 1 +
drivers/common/zsda/zsda_qp.c | 715
drivers/common/zsda/zsda_qp.h | 146 +++
3 files change
add session support for zsda cryptodev.
Signed-off-by: Hanxiao Li
---
drivers/common/zsda/meson.build| 15 +-
drivers/crypto/zsda/zsda_sym_session.c | 512 +
drivers/crypto/zsda/zsda_sym_session.h | 83
3 files changed, 609 insertions(+), 1 deletion(-)
cre
Add the number of zsda devices.
Signed-off-by: Hanxiao Li
---
config/rte_config.h | 4
1 file changed, 4 insertions(+)
diff --git a/config/rte_config.h b/config/rte_config.h
index dd7bb0d35b..e1e85b3291 100644
--- a/config/rte_config.h
+++ b/config/rte_config.h
@@ -117,6 +117,10 @@
#defin
Recheck-request: iol-unit-amd64-testing, iol-unit-arm64-testing
Hi Nitin, all,
Nitin Saxena, Oct 17, 2024 at 09:03:
Hi Robin/David and all,
We realized the feature arc patch series is difficult to understand as
a new concept. Our objectives are following with feature arc changes
1. Allow reusability of standard DPDK nodes (defined in lib/nodes/*)
wit
On Fri, Sep 20, 2024 at 2:57 PM Bruce Richardson
wrote:
>
> This patchset proposed increasing the minimum meson version to 0.57
> and makes changes to update our build files appropriately for that
> change: replacing deprecated functions, removing unnecessary version
> checks and taking advantage
Rework the code responsible for creation of unicast control flow rules,
to allow creation of:
- unicast DMAC flow rules and
- unicast DMAC with VMAN flow rules,
outside of mlx5_traffic_enable() called when port is started.
Signed-off-by: Dariusz Sosnowski
---
drivers/net/mlx5/meson.build
This patch adds support for destroying:
- unicast DMAC control flow rules and
- unicast DMAC with VLAN control flow rules,
without affecting any other control flow rules,
when HWS flow engine is used.
Signed-off-by: Dariusz Sosnowski
---
drivers/net/mlx5/mlx5_flow.h | 8 +++
drivers/
Add 2 internal functions for checking if:
- unicast DMAC control flow rule or
- unicast DMAC with VLAN control flow rule,
was created.
Signed-off-by: Dariusz Sosnowski
---
drivers/net/mlx5/mlx5.h | 11 +++
drivers/net/mlx5/mlx5_flow.c | 37
2 f
All control flow rules in NIC Rx domain, created by HWS flow engine,
were assigned MLX5_HW_CTRL_FLOW_TYPE_DEFAULT_RX_RSS type.
To allow checking if a flow rule with given DMAC or VLAN were created,
the list of associated types is extended with:
- type for unicast DMAC flow rules,
- type for unicas
Whenever a new MAC address is added to the port, mlx5 PMD will:
- Add this address to `dev->data->mac_addrs[]`.
- Destroy all control flow rules.
- Recreate all control flow rules.
Similar logic is also implemented for VLAN filters.
Because of such logic, the latency of adding the new MAC addres
On Fri, Sep 6, 2024 at 6:13 PM Bruce Richardson
wrote:
>
> To make it easier to build and test DPDK on 32-bit x86 add a set of
> cross-compile ini files for a number of common linux distributions.
> This avoids the user having to remember strange meson incantations
> with '-m32' in various args va
All structs and enumerations used for managenement of
HWS control flow rules do not really depend on HWS itself.
In order to allow their reuse with Verbs and DV flow engines and
allow fine-grained creation/destruction of unicast DMAC (with VLAN)
flow rules with these flow engines, this patch rename
This patch:
- Changes MAC address adding/removing handling, so that
only required control rules are added/removed.
As a result, rte_eth_dev_mac_addr_add() or
rte_eth_dev_mac_addr_remove() calls are faster for mlx5 PMD.
- Changes VLAN filtering handling, so that
only required control flow r
Whenever a unicast DMAC or unicast DMAC with VLAN ID control flow rule
is created when working with Verbs or DV flow engine,
add this flow rule to the control flow rule list,
with information required for recognizing it.
Signed-off-by: Dariusz Sosnowski
---
drivers/net/mlx5/mlx5_flow.c| 32 +
This patch extens the mlx5_traffic interface with a couple of functions:
- mlx5_traffic_mac_add() - Create an unicast DMAC flow rule, without
recreating all control flow rules.
- mlx5_traffic_mac_remove() - Remove an unicast DMAC flow rule,
without recreating all control flow rules.
- mlx5_tra
Control flow rules lists and control flow rule lock
can be reused between all flow engines, but their initialization
was done in flow_hw_configure() implementation.
This patch moves it to mlx5_dev_spawn(),
which is called for Verbs, DV and HWS flow engines.
Signed-off-by: Dariusz Sosnowski
---
d
This patch adds the following internal functions for creation of
unicast DMAC flow rules:
- mlx5_legacy_dmac_flow_create() - simple wrapper over
mlx5_ctrl_flow().
- mlx5_legacy_dmac_vlan_flow_create() - simple wrapper over
mlx5_ctrl_flow_vlan().
These will be used as a basis for implementing
Hi all,
What about the following steps:
- update the nodes so they work on the current layer (example: for all L3
nodes, the current mbuf data offset *must* be pointing to the IP header)
- define a public data structure that would be shared across nodes through priv
data, and not dynfields ? Thi
Add more ICMP message types and codes based on RFC 792. Change the
namespace prefix from RTE_IP_ICMP_ to RTE_ICMP_ to allow differentiation
between types and codes.
Signed-off-by: Robin Jarry
---
app/test-pmd/icmpecho.c | 10 +-
lib/net/rte_icmp.h | 31 +-
在 2024/10/17 11:20, Stephen Hemminger 写道:
On Thu, 17 Oct 2024 10:11:13 +0800
"lihuisong (C)" wrote:
Hi Stephen,
在 2024/10/15 23:45, Stephen Hemminger 写道:
On Tue, 15 Oct 2024 17:41:39 +0800
"lihuisong (C)" wrote:
Hi Stephen,
Can you take a look at this reply so as to send out the next
On 10/3/24 23:18, Stephen Hemminger wrote:
Makes sense, but patch has some fuzz against current main branch.
There is also another patch that address the ASAN touch issue.
https://patchwork.dpdk.org/project/dpdk/patch/20240723083419.12435-1-amic...@kalrayinc.com/
I just sent a new version of t
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 organizati
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 patch introduces driver support for power management of uncore
components in AMD EPYC processors.
v2:
- fixed typo in comments section.
- added fabric frequency get support for legacy platforms.
Signed-off-by: Sivaprasad Tummala
---
drivers/power/amd_uncore/amd_uncore.c | 329 +++
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
Update maintainers for drivers/power/*.
Signed-off-by: Sivaprasad Tummala
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6814991735..9f14e8f8d6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1744,6 +1744,7 @@ M: Anatoly Burakov
M: David Hunt
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 organizati
After refactoring the power library, power management operations are now
consistently supported regardless of the operating environment, making
function pointer checks unnecessary and thus removed from applications.
v2:
- removed function pointer validation in l3fwd-power app.
Signed-off-by: Siv
Add implementation for TX datapath.
Signed-off-by: Howard Wang
---
drivers/net/r8169/r8169_ethdev.c | 6 +
drivers/net/r8169/r8169_ethdev.h | 11 +
drivers/net/r8169/r8169_rxtx.c | 681 ++-
3 files changed, 682 insertions(+), 16 deletions(-)
diff --git a/drivers
06/09/2024 19:01, Vladimir Medvedkin:
> Reverse polynomial for an LFSR was initialized improperly which
> could generate improper bit sequence in some situations.
> This patch implements proper polynomial reversing function.
>
> Fixes: 28ebff11c2dc ("hash: add predictable RSS")
> Cc: sta...@dpdk.o
Allocation would fail with ASan enabled if the size and alignment was
equal to half of the page size, e.g.:
size_t pg_sz = 2 * (1 << 20);
rte_malloc(NULL, pg_sz / 2, pg_sz / 2);
In such case, try_expand_heap_primary() only allocated one page but it
is not enough to fit this allocation with such a
Multi-process applications operate on shared hugepage memory but each
process has its own ASan shadow region which is not synchronized with
the other processes. This causes issues when different processes try to
use the same memory because they have their own view of which addresses
are valid.
Fix
On Thu, Oct 17, 2024 at 09:53:18AM +0200, David Marchand wrote:
> On Fri, Sep 20, 2024 at 2:57 PM Bruce Richardson
> wrote:
> >
> > This patchset proposed increasing the minimum meson version to 0.57
> > and makes changes to update our build files appropriately for that
> > change: replacing depre
Now the Rx burst size is fixed to MAX_PKT_BURST (32). This
parameter needs to be modified in some performance optimization
scenarios. So an option '--burst' is added to set the burst size
explicitly. The default value is DEFAULT_PKT_BURST (32) and maximum
value is MAX_PKT_BURST (512).
Signed-off-b
The mempool cache size of mbuf is set to
RTE_MEMPOOL_CACHE_MAX_SIZE as default. This patch allows
users to configure the cache size by "--mbcache", and limits
the parameter to a maximum of RTE_MEMPOOL_CACHE_MAX_SIZE.
Signed-off-by: Jie Hai
Acked-by: Huisong Li
Acked-by: Morten Brørup
---
examp
Add options to support configuring RX burst size and cache size
of mbuf mempoool.
--
v3:
1. add Acked-bys.
2. fix compile error.
--
Jie Hai (2):
examples/l3fwd: add option to set RX burst size
examples/l3fwd: add option to set mbuf cache size
examples/l3fwd/l3fwd.h | 8 +++-
examples/l3
>-Original Message-
>From: Konstantin Ananyev
>Sent: Wednesday, October 16, 2024 10:50 AM
>To: Tomasz Duszynski ; Thomas Monjalon
>
>Cc: ruifeng.w...@arm.com; bruce.richard...@intel.com;
>david.march...@redhat.com; dev@dpdk.org;
>Jerin Jacob ; konstantin.v.anan...@yandex.ru;
>mattias
Hi Robin/David and all,
We realized the feature arc patch series is difficult to understand as
a new concept. Our objectives are following with feature arc changes
1. Allow reusability of standard DPDK nodes (defined in lib/nodes/*)
with out-of-tree applications (like grout). Currently out-of-tre
Hi Robin,
Thanks for the review
Please see my replies inline
Thanks,
Nitin
On Wed, Oct 16, 2024 at 3:08 PM Robin Jarry wrote:
>
> Hi folks,
>
> David Marchand, Oct 16, 2024 at 11:24:
> > On Mon, Oct 14, 2024 at 1:12 PM Nitin Saxena wrote:
> >> I had pushed non RFC patch series before -rc1 date
For the entire series:
Acked-by: Viacheslav Ovsiienko
> -Original Message-
> From: Dariusz Sosnowski
> Sent: Thursday, October 17, 2024 10:57 AM
> To: Slava Ovsiienko ; Bing Zhao
> ; Ori Kam ; Suanming Mou
> ; Matan Azrad
> Cc: dev@dpdk.org
> Subject: [PATCH 00/10] net/mlx5: improve MA
Acked-by: Huisong Li
在 2024/10/17 16:58, Jie Hai 写道:
Now the Rx burst size is fixed to MAX_PKT_BURST (32). This
parameter needs to be modified in some performance optimization
scenarios. So an option '--burst' is added to set the burst size
explicitly. The default value is DEFAULT_PKT_BURST (32
lgtm, Acked-by: Huisong Li
在 2024/10/17 16:58, Jie Hai 写道:
The mempool cache size of mbuf is set to
RTE_MEMPOOL_CACHE_MAX_SIZE as default. This patch allows
users to configure the cache size by "--mbcache", and limits
the paramater to a maximum of RTE_MEMPOOL_CACHE_MAX_SIZE.
Signed-off-by: Jie
Good job.
With belows to change,
Acked-by: Huisong Li
在 2024/10/17 19:02, Sivaprasad Tummala 写道:
This commit fixes an issue in the power library
related to using lcores mapped to different
physical cores (--lcores option in EAL).
Previously, the power library incorrectly accessed
CPU sysfs at
Hi Christophe,
Please see inline comments
Thanks,
Nitin
On Thu, Oct 17, 2024 at 2:02 PM Christophe Fontaine wrote:
>
> Hi all,
>
> What about the following steps:
> - update the nodes so they work on the current layer (example: for all L3
> nodes, the current mbuf data offset *must* be pointin
> >
> Add PM QoS configuration to declease the delay after sleep in case of
> entering deeper idle state.
>
> Signed-off-by: Huisong Li
> Acked-by: Morten Brørup
> ---
> examples/l3fwd-power/main.c | 24
> 1 file changed, 24 i
> This commit fixes an issue in the power library
> related to using lcores mapped to different
> physical cores (--lcores option in EAL).
>
> Previously, the power library incorrectly accessed
> CPU sysfs attributes for power management, treating
> lcore IDs as CPU IDs.
> e.g. with --lcores '1
https://bugs.dpdk.org/show_bug.cgi?id=1566
Bug ID: 1566
Summary: On Windows, some netuio-bound device can not be used
on Windows if at least one device is using Intel ice
drivers
Product: DPDK
Version: 23.11
On Mon, Sep 2, 2024 at 11:58 AM Anatoly Burakov
wrote:
>
> From: Jaroslaw Ilgiewicz
>
> Time variables were designed for 32 bit and 64 bit variables are not
> necessary. Changed all to 32 bit.
>
> Signed-off-by: Jaroslaw Ilgiewicz
> Signed-off-by: Anatoly Burakov
> ---
> drivers/net/i40e/base/
This commit fixes an issue in the power library
related to using lcores mapped to different
physical cores (--lcores option in EAL).
Previously, the power library incorrectly accessed
CPU sysfs attributes for power management, treating
lcore IDs as CPU IDs.
e.g. with --lcores '1@128', lcore_id '1'
When user request to use lcores mapped to different physical
cores using --lcores eal option, power application accesses
incorrect cpu sysfs attribute for checking current frequency
The patch fixes the cpu_id based on the lcore and cpu mappings.
Signed-off-by: Sivaprasad Tummala
---
app/test/te
There's a little tip that can be modified, with that modified:
Acked-by: Chengwen Feng
On 2024/10/17 17:58, Jie Hai wrote:
> The mempool cache size of mbuf is set to
> RTE_MEMPOOL_CACHE_MAX_SIZE as default. This patch allows
> users to configure the cache size by "--mbcache", and limits
> the par
在 2024/10/17 19:02, Sivaprasad Tummala 写道:
When user request to use lcores mapped to different physical
cores using --lcores eal option, power application accesses
incorrect cpu sysfs attribute for checking current frequency
The patch fixes the cpu_id based on the lcore and cpu mappings.
Sign
Hello guys,
I am not clear if this issue is new (and what caused it), but
compilation fails on Rawhide for the net/gve driver (see below for the
log).
Afaics, Intel drivers wrapped __le16 types (and friends) using macros
(example:
https://git.dpdk.org/dpdk/tree/drivers/net/i40e/base/i40e_osdep.h
Hello Robin,
On Thu, Oct 10, 2024 at 9:42 PM Robin Jarry wrote:
>
> As discussed recently [1], here is a first draft of the IPv6 APIs rework. The
> API change was announced before the 24.07 release [2]. This series is intended
> for 24.11.
>
> [1] http://inbox.dpdk.org/dev/d2sr8t1h39cj.jrqfi6jeh.
> This version of the patch is garbled in patchwork which means the CI test
> never
> ran because patch would not apply.
>
> You need cleanup and resubmit it.
I have sent v5 on behalf of Alan.
On Thu, 17 Oct 2024 17:21:57 +0800
Hanxiao Li wrote:
> v11:
> - use RTE_LOG_LINE in logging macro.
> - fix some known bugs.
>
> v10:
> - delete new blank line at EOF
> - Cleaning up some code in zsda_log.h
>
> v9:
> - add a new feature in default.ini.
> - Re-split the patch according to the ne
On Thu, 17 Oct 2024 17:22:02 +0800
Hanxiao Li wrote:
> +static int
> +zsda_get_queue_cfg_by_id(const struct zsda_pci_device *zsda_pci_dev,
> + const uint8_t qid, struct qinfo *qcfg)
> +{
> + struct zsda_admin_req_qcfg req = {0};
> + struct zsda_admin_resp_qcfg resp =
On Thu, 17 Oct 2024 20:03:13 +0100
Bruce Richardson wrote:
> On Thu, Oct 17, 2024 at 07:15:10PM +0200, Morten Brørup wrote:
> > > +/**
> > > + * Process the IPv4 checksum of an IPv4 header without any extensions.
> > > + *
> > > + * The checksum field does NOT have to be set by the caller, the fi
13/10/2024 10:35, Morten Brørup:
> +static_assert(sizeof(struct rte_ether_addr) == 6,
> + "sizeof(struct rte_ether_addr) == 6");
> +static_assert(alignof(struct rte_ether_addr) == 2,
> + "alignof(struct rte_ether_addr) == 2");
Instead of repeating the condition twice,
it wo
Please could we have another review?
22/08/2024 17:32, Alexander Kozyrev:
> Support the IP Encapsulating Security Payload (ESP) in transport mode.
> Currently, we have RTE_PTYPE_TUNNEL_ESP for the ESP tunnel mode.
> Transport mode can be detected by parsing the "Next Header" field.
> The Next Hea
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Thursday, 17 October 2024 22.44
>
> 13/10/2024 10:35, Morten Brørup:
> > +static_assert(sizeof(struct rte_ether_addr) == 6,
> > + "sizeof(struct rte_ether_addr) == 6");
> > +static_assert(alignof(struct rte_ether_addr) == 2,
>
Currently, a number of integer types are typedef'd to their
corresponding upserspace or RTE values. This can be problematic if these
types are already defined somewhere else, as it would cause type
collisions. This patch changes the typedefs to #define macros which are
only defined if the types are
This meeting has changed times. The instructions to join the call are the same.
Adding support for PCIe steering tags in DPDK
On Thu, Oct 17, 2024 at 07:15:10PM +0200, Morten Brørup wrote:
> > +/**
> > + * Process the IPv4 checksum of an IPv4 header without any extensions.
> > + *
> > + * The checksum field does NOT have to be set by the caller, the field
> > + * is skipped by the calculation.
> > + *
> > + * @param ipv4_
> -Original Message-
> From: Akhil Goyal
> Sent: Friday, October 11, 2024 2:18 PM
> To: Kusztal, ArkadiuszX ; dev@dpdk.org
> Cc: Dooley, Brian
> Subject: RE: [EXTERNAL] [PATCH v5 2/4] cryptodev: add ec points to sm2 op
>
> > In the case when PMD cannot support the full process of the
On Wed, 16 Oct 2024 16:22:32 +0800
Chaoyong He wrote:
> From: Long Wu
>
> The previous code used a macro as the data size for mbuf
> to create the mempool and users cannot modify the size.
>
> Now modify the code to support setting the data size of
> mbuf by '--mbuf-size' parameter. If user do
31/07/2024 08:32, Srikanth Yalavarthi:
> Introduced data type conversion functions with support for
> user defined scale factor and zero-point. Updated library
> functions to support asymmetric / affine conversion for
> integer types.
>
> Signed-off-by: Srikanth Yalavarthi
Applied, thanks.
A DPDK community call on adding support for PCIe steering tags is scheduled for
10/23/24 at 9AM CST.
Steering tags allow for the stashing of descriptors and packet data closer to
the CPUs, possibly allowing for lower latency and higher throughput.
This feature requires contributions from CPU vend
-Original Message-
From: Richardson, Bruce
Sent: Thursday, October 17, 2024 11:59 AM
To: dev@dpdk.org
Cc: Kadam, Pallavi ; Richardson, Bruce
Subject: [PATCH] maintainers: remove Pallavi as windows maintainer
Pallavi Kadam is no longer working on DPDK, so she has requested that her n
31/07/2024 08:25, Srikanth Yalavarthi:
> Added scale and zero point to I/O information structure.
> This would provision sharing the recommended sclae factor
> and zero point to the user for quantization process.
>
> Signed-off-by: Srikanth Yalavarthi
Applied with a Doxygen comment fixed.
On 10/17/2024 8:20 PM, lon...@linuxonhyperv.com wrote:
> From: Alan Elder
>
> The previous code allowed the number of Tx queues to be set higher than
> the number of Rx queues. If a packet was sent on a Tx queue with index
>> = number Rx queues there was a segfault due to accessing beyond the en
On 10/18/2024 12:02 AM, Stephen Hemminger wrote:
> On Thu, 17 Oct 2024 22:38:49 +
> Long Li wrote:
>
>>> Subject: Re: [Patch v5] net/netvsc: fix number Tx queues > Rx queues
>>>
>>> On Thu, 17 Oct 2024 12:20:29 -0700
>>> lon...@linuxonhyperv.com wrote:
>>>
+static void
+hn_rx_que
On 10/18/2024 12:42 AM, Joshua Washington wrote:
> Currently, a number of integer types are typedef'd to their
> corresponding upserspace or RTE values. This can be problematic if these
> types are already defined somewhere else, as it would cause type
> collisions. This patch changes the typedefs
https://bugs.dpdk.org/show_bug.cgi?id=1567
Bug ID: 1567
Summary: dts: Replace the helloworld testsuite with a testsuite
which starts testpmd but does nothing
Product: DPDK
Version: unspecified
Hardware: All
25/09/2024 17:47, Stephen Hemminger:
> On Wed, 25 Sep 2024 11:40:54 -0400
> Robin Jarry wrote:
>
> > From: Robin Jarry
> > To: dev@dpdk.org
> > Subject: [PATCH dpdk v2] mbuf: fix strict aliasing error in allocator
> > Date: Wed, 25 Sep 2024 11:40:54 -0400
> >
> > When building an application wi
Hello,
There is a joint Governing Board & Tech Board meeting next Thursday
(October 24) at 9AM EST, when we normally have the DTS meeting. I
think I need to be available to join this, so we will need to
reschedule the DTS call.
I am going to preliminarily move it to Friday at the normal time, but
From: Alan Elder
The previous code allowed the number of Tx queues to be set higher than
the number of Rx queues. If a packet was sent on a Tx queue with index
>= number Rx queues there was a segfault due to accessing beyond the end
of the dev->data->rx_queues[] array.
This commit fixes the iss
> Subject: Re: [Patch v5] net/netvsc: fix number Tx queues > Rx queues
>
> On Thu, 17 Oct 2024 12:20:29 -0700
> lon...@linuxonhyperv.com wrote:
>
> > +static void
> > +hn_rx_queue_free_common(struct hn_rx_queue *rxq) {
> > + if (!rxq)
> > + return;
> > +
> > + rte_free(rxq->rxbuf_in
Add more ICMP message types and codes based on RFC 792. Change the
namespace prefix from RTE_IP_ICMP_ to RTE_ICMP_ to allow differentiation
between types and codes.
Do not include deprecated message types as described in RFC 6918.
Link: https://www.rfc-editor.org/rfc/rfc792
Link: https://www.rfc-
Ferruh Yigit, Oct 18, 2024 at 00:22:
On 10/17/2024 5:02 PM, Stephen Hemminger wrote:
On Thu, 17 Oct 2024 10:33:22 +0200
Robin Jarry wrote:
Add more ICMP message types and codes based on RFC 792. Change the
namespace prefix from RTE_IP_ICMP_ to RTE_ICMP_ to allow differentiation
between types
On 10/17/2024 11:33 PM, Robin Jarry wrote:
> Ferruh Yigit, Oct 18, 2024 at 00:22:
>> On 10/17/2024 5:02 PM, Stephen Hemminger wrote:
>>> On Thu, 17 Oct 2024 10:33:22 +0200
>>> Robin Jarry wrote:
>>>
Add more ICMP message types and codes based on RFC 792. Change the
namespace prefix from
On 10/16/2024 9:17 AM, Chaoyong He wrote:
> From: Long Wu
>
> Before the commit 5126a904fae0
> ("net/nfp: use offload flag to control VXLAN configuration"),
> in the initial logic 'nfp_net_start()' will enable the
> NFP_NET_CFG_CTRL_VXLAN flag if hardware has the capability,
> 'udp_tunnel_port_ad
1 - 100 of 180 matches
Mail list logo
