To optimize Rx/Tx burst process,
add NEON vector instructions on arm architecture.
Signed-off-by: liwencheng
---
drivers/net/macb/macb_rxtx.c | 3 +
drivers/net/macb/macb_rxtx_vec_neon.c | 675 ++
drivers/net/macb/meson.build | 4 +
3 files c
v6:
- Fixed build failures across different OS.
v5:
- Putting __rte_unused after the declaration.
- Correct RX-bytes and TX-bytes statistics.
- Initialize the mbuf_initializer.
- Add driver based on 25.07.
- Fixed some code style issues.
v4:
- Fix tab errors in meson.build file.
- Use RTE_LOG_LIN
Correct the RSS algorithm configuration logic, also do some refactor to
the related logic.
Signed-off-by: Chaoyong He
---
drivers/net/nfp/nfp_net_common.c | 121 +--
1 file changed, 81 insertions(+), 40 deletions(-)
diff --git a/drivers/net/nfp/nfp_net_common.c b/dri
This patch series try to correct the RSS algorithm related logic.
Chaoyong He (3):
net/nfp: support get RSS algorithm capability
net/nfp: support get RSS algorithm configuration
net/nfp: correct RSS algorithm configuration logic
drivers/common/nfp/nfp_common.h | 1 +
driver
Use the base code build handling logic in the drivers/meson.build file,
rather than re-implementing it in the driver itself.
Signed-off-by: Bruce Richardson
---
drivers/net/ngbe/base/meson.build | 12 ++--
drivers/net/ngbe/meson.build | 3 ---
2 files changed, 2 insertions(+), 13 d
From: Long Li
For vmbus channels without monitoring support, use kernel UIO interface
to indicate packet through interrupt page and UIO file handle.
Signed-off-by: Long Li
---
Changes:
v4: replace RTE_ATOMIC(uint32_t) * with RTE_ATOMIC(uint32_t *) for declaring
variable
drivers/bus/vmbus/vmb
From: Long Li
The secondary process can access its vmbus device through device private
region. Add and pass it on all call chains leading to vmbus code.
Signed-off-by: Long Li
---
drivers/bus/vmbus/linux/vmbus_uio.c | 2 +-
drivers/bus/vmbus/private.h | 2 +-
drivers/bus/vmbus/rte_bu
From: Long Li
Hyperv host may offer channels without monitor enabled. The max monitor
ID it supports is 128. Over those channels without monitor enabled,
Hyperv does not send or receive large amount of data traffic and almost all
the data traffic is going over the VF.
Change the code to not fail
From: Long Li
Introduce a function get the vmbus device from hn_data. For secondary
process, the vmbus device is in eth_dev's private region.
Signed-off-by: Long Li
---
drivers/net/netvsc/hn_nvs.c | 15 +++
drivers/net/netvsc/hn_nvs.h | 2 ++
2 files changed, 17 insertions(+)
dif
From: Long Li
To prepare for supporting to set hyperv event from secondary process
when the channel has monitoring disable, introduce a private data
region for storing the vmbus device. The secondary process will get
access to its vmbus device in case it needs to signal the host.
Signed-off-by:
From: Long Li
Hyperv may expose VMBUS channels without monitoring enabled. In this case,
it programs almost all the data traffic to VF.
This patchset enabled vmbus/netvsc to use channels without monitoring
enabled.
This needs to change the APIs exposed by drivers/bus/vmbus. Because those
APIs a
> Subject: [EXTERNAL] Re: [Patch v3 6/6] bus/vmbus: set event for channel
> without
> monitoring support
>
> On Fri, 4 Apr 2025 17:35:38 -0700
> lon...@linuxonhyperv.com wrote:
>
> > diff --git a/drivers/bus/vmbus/vmbus_channel.c
> > b/drivers/bus/vmbus/vmbus_channel.c
> > index bccef168d3..81e
On Mon, 7 Apr 2025 06:36:52 +
liwencheng wrote:
> v5:
> - Putting __rte_unused after the declaration.
> - Correct RX-bytes and TX-bytes statistics.
> - Initialize the mbuf_initializer.
> - Add driver based on 25.07.
> - Fixed some code style issues.
>
> v4:
> - Fix tab errors in meson.build
On Mon, Apr 07, 2025 at 05:49:34PM +0200, David Marchand wrote:
> On Mon, Apr 7, 2025 at 5:29 PM Bruce Richardson
> wrote:
> >
> > For SVE, as for AVX2 and AVX-512, support building files for these ISAs
> > from the top-level drivers/meson.build file, rather than having each
> > driver re-implemen
On Mon, Apr 07, 2025 at 08:14:50AM -0700, Stephen Hemminger wrote:
> On Mon, 7 Apr 2025 12:15:13 +0200
> Morten Brørup wrote:
>
> > > From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > > Sent: Monday, 7 April 2025 11.49
> > >
> > > On Mon, Apr 07, 2025 at 09:04:05AM +0200, David Marc
The "--lcores" EAL parameter has a very powerful syntax that can be used
to provide precise control over lcore mappings. The docs however, only
provided a minimal description of what it can do. Augment the docs by
providing some examples of use of the option, and what the resulting
core mappings wo
On Wed, Apr 02, 2025 at 03:08:45PM +0200, David Marchand wrote:
> On Mon, Mar 31, 2025 at 6:10 PM Bruce Richardson
> wrote:
> >
> > Many DPDK drivers use the same pattern for base code handling, having
> > a meson.build file in the base code directory which optionally defines
> > some custom cflag
For SVE, as for AVX2 and AVX-512, support building files for these ISAs
from the top-level drivers/meson.build file, rather than having each
driver re-implement it.
This removes the remaining build task for drivers in DPDK which is
being done by a driver itself, rather than in the generic drivers'
Use the base code build handling logic in the drivers/meson.build file,
rather than re-implementing it in the driver itself.
While making changes similar to that in other drivers, also move content
around dependencies from the base/meson.build file to the main
driver meson.build file, so that the
Use the base code build handling logic in the drivers/meson.build file,
rather than re-implementing it in the driver itself.
Signed-off-by: Bruce Richardson
---
drivers/net/txgbe/base/meson.build | 18 ++
drivers/net/txgbe/meson.build | 3 ---
2 files changed, 2 insertions(
Use the base code build handling logic in the drivers/meson.build file,
rather than re-implementing it in the driver itself.
Signed-off-by: Bruce Richardson
---
drivers/net/qede/base/meson.build | 17 +
drivers/net/qede/meson.build | 1 -
2 files changed, 5 insertions(+), 1
Use the base code build handling logic in the drivers/meson.build file,
rather than re-implementing it in the driver itself.
Signed-off-by: Bruce Richardson
---
drivers/net/hinic/base/meson.build | 16 +---
drivers/net/hinic/meson.build | 1 -
2 files changed, 5 insertions(+),
Use the base code build handling logic in the drivers/meson.build file,
rather than re-implementing it in the drivers.
Signed-off-by: Bruce Richardson
---
drivers/net/intel/e1000/meson.build| 3 ---
drivers/net/intel/fm10k/meson.build| 3 ---
drivers/net/intel/i40e/meson.build | 2
Use the base code build handling logic in the drivers/meson.build file,
rather than re-implementing it in the driver itself.
Signed-off-by: Bruce Richardson
Acked-by: Andrew Rybchenko
---
drivers/common/sfc_efx/base/meson.build | 18 +++---
drivers/common/sfc_efx/meson.build |
Add support to the drivers meson.build file for base code files with
extra cflags for compilation. This should remove the need for custom
logic in each driver.
In future, we may want to move the base code handling down the file a
little in order to get lock checking. However, this lock checking is
Many DPDK drivers use the same pattern for base code handling, having
a meson.build file in the base code directory which optionally defines
some custom cflags for the base code build, then builds the code as a
static library and extracts the objects from it. (The reason behind this
is that, in mes
#
April 3, 2025
Attendees
1. Patrick Robb
2. Paul Szczepanek
3. Luca Vizzarro
4. Aaron Conole
5. Manit Mahajan
#
Minutes
On Mon, 7 Apr 2025 12:15:13 +0200
Morten Brørup wrote:
> > From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > Sent: Monday, 7 April 2025 11.49
> >
> > On Mon, Apr 07, 2025 at 09:04:05AM +0200, David Marchand wrote:
> > > Hello Bruce,
> > >
> > > On Tue, Apr 1, 2025 at 4:08 PM Bruce
On Mon, 7 Apr 2025 10:51:37 +0100
Bruce Richardson wrote:
> On Sat, Apr 05, 2025 at 08:36:23AM -0700, Stephen Hemminger wrote:
> > The process private data allocation was indented incorrectly
> > in the source code, and had unnecessary cast. It is better
> > that the data be allocated on same num
On Wed, 2 Apr 2025 06:58:32 +
liwencheng wrote:
>
> +def unbind_platform_one(dev_name):
> +filename = "/sys/bus/platform/devices/%s/driver" % dev_name
> +
> +if exists(filename):
> +try:
> +f = open(os.path.join(filename, "unbind"), "w")
> +except OSErro
https://bugs.dpdk.org/show_bug.cgi?id=1693
Bug ID: 1693
Summary: ring PMD rte_eth_from_ring does not do what is
expected
Product: DPDK
Version: 25.03
Hardware: All
OS: All
Status: UNCONFIRMED
Hello Andre,
On Thu, Feb 20, 2025 at 9:32 PM Andre Muezerie
wrote:
>
> Now that the issues preventing this lib from be compiled with MSVC
> are fixed it can be included in the compilation.
>
> The "net" library will automatically get compiled as well as it
> has a dependency on "mbuf" which will
On Thu, Apr 3, 2025 at 6:59 PM David Marchand wrote:
>
> So far, each DPDK library (or driver) exposing symbols in an ABI had to
> maintain a version.map and use some macros for symbol versioning,
> specially crafted with the GNU linker in mind.
>
> This series proposes to rework the whole princip
On Mon, Apr 07, 2025 at 02:24:51PM +0100, Bruce Richardson wrote:
> The "--lcores" EAL parameter has a very powerful syntax that can be used
> to provide precise control over lcore mappings. The docs however, only
> provided a minimal description of what it can do. Augment the docs by
> providing s
The "--lcores" EAL parameter has a very powerful syntax that can be used
to provide precise control over lcore mappings. The docs however, only
provided a minimal description of what it can do. Augment the docs by
providing some examples of use of the option, and what the resulting
core mappings wo
On Mon, Apr 07, 2025 at 03:18:36PM +0200, Morten Brørup wrote:
> > From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > Sent: Monday, 7 April 2025 14.42
> >
> > On Mon, Apr 07, 2025 at 02:25:46PM +0200, Morten Brørup wrote:
> > > > From: Bruce Richardson [mailto:bruce.richard...@intel.co
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Monday, 7 April 2025 14.42
>
> On Mon, Apr 07, 2025 at 02:25:46PM +0200, Morten Brørup wrote:
> > > From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > > Sent: Monday, 7 April 2025 13.56
> > >
> > > On Mon, Apr 07, 202
TB Members Attending
-
Aaron Conole
Bruce Richardson (chair)
Hemant Agrawal
Honnappa Nagarahalli
Jerin Jacob
Kevin Traynor
Maxime Coquelin
Morten Brørup
Stephen Hemminger
Thomas Monjalon
NOTE: The technical board meetings are on every second Wednesday at 3pm UTC.
Meetings are p
On Mon, Apr 07, 2025 at 02:25:46PM +0200, Morten Brørup wrote:
> > From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > Sent: Monday, 7 April 2025 13.56
> >
> > On Mon, Apr 07, 2025 at 01:32:59PM +0200, Morten Brørup wrote:
> > > > From: Bruce Richardson [mailto:bruce.richard...@intel.co
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Monday, 7 April 2025 13.56
>
> On Mon, Apr 07, 2025 at 01:32:59PM +0200, Morten Brørup wrote:
> > > From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > > Sent: Monday, 7 April 2025 12.41
> > >
> > > On Mon, Apr 07, 202
On Mon, Apr 07, 2025 at 01:32:59PM +0200, Morten Brørup wrote:
> > From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> > Sent: Monday, 7 April 2025 12.41
> >
> > On Mon, Apr 07, 2025 at 12:15:13PM +0200, Morten Brørup wrote:
> > > > From: Bruce Richardson [mailto:bruce.richard...@intel.co
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Monday, 7 April 2025 12.41
>
> On Mon, Apr 07, 2025 at 12:15:13PM +0200, Morten Brørup wrote:
> > > From: Bruce Richardson [mailto:bruce.richard...@intel.com] Sent:
> > > Monday, 7 April 2025 11.49
> > >
> > > On Mon, Apr 07, 202
On Mon, Apr 07, 2025 at 12:15:13PM +0200, Morten Brørup wrote:
> > From: Bruce Richardson [mailto:bruce.richard...@intel.com] Sent:
> > Monday, 7 April 2025 11.49
> >
> > On Mon, Apr 07, 2025 at 09:04:05AM +0200, David Marchand wrote:
> > > Hello Bruce,
> > >
> > > On Tue, Apr 1, 2025 at 4:08 PM B
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Monday, 7 April 2025 11.49
>
> On Mon, Apr 07, 2025 at 09:04:05AM +0200, David Marchand wrote:
> > Hello Bruce,
> >
> > On Tue, Apr 1, 2025 at 4:08 PM Bruce Richardson
> > wrote:
> > >
> > > On Mon, Mar 24, 2025 at 05:30:26PM +0
v5:
- Putting __rte_unused after the declaration.
- Correct RX-bytes and TX-bytes statistics.
- Initialize the mbuf_initializer.
- Add driver based on 25.07.
- Fixed some code style issues.
v4:
- Fix tab errors in meson.build file.
- Use RTE_LOG_LINE instead of rte_log.
- Replace %l with %PRI*64.
On Sat, Apr 05, 2025 at 08:36:23AM -0700, Stephen Hemminger wrote:
> The process private data allocation was indented incorrectly
> in the source code, and had unnecessary cast. It is better
> that the data be allocated on same numa node as the device
> structure.
>
> Signed-off-by: Stephen Hemmin
On Mon, Apr 07, 2025 at 09:04:05AM +0200, David Marchand wrote:
> Hello Bruce,
>
> On Tue, Apr 1, 2025 at 4:08 PM Bruce Richardson
> wrote:
> >
> > On Mon, Mar 24, 2025 at 05:30:26PM +, Bruce Richardson wrote:
> > > Traditionally, DPDK has had a direct mapping of internal lcore-ids, to
> > >
Streamline code for AVX512 and SSE by consolidating the common code and
adding runtime check for selecting appropriate path based on CPU
capability.
Signed-off-by: Tirthendu Sarkar
---
v3:
- Simplified code for AVX/SSE paths
v2:
- Addressed review comments [Bruce Richardson]
drivers/event/dlb
Currently each rte_node registers separate mbuf dynamic fields for their
own purpose. This leads to wastage of mbuf space as once mbuf get passed
a particular node, the registered dynamic field(by that node) is no
longer used.
This patch series adds a global/common mbuf dynamic field which is
reus
- Used global node mbuf in ip[4|6]_lookup/rewrite nodes
- Redefine node_mbuf_priv1() to rte_node_mbuf_overload_fields_get()
Signed-off-by: Nitin Saxena
---
lib/node/ip4_lookup.c | 14 ---
lib/node/ip4_rewrite.c| 15 +---
lib/node/ip6_lookup.c |
This patch defines rte_node specific dynamic field structure
(rte_node_mbuf_dynfield_t)
rte_node_mbuf_dynfield_t structure holds two types of fields
- Persistent data fields which are preserved across graph walk.
Currently size of persistent data fields is zero.
- Overloadable data fields which
launching ipsec-segw application in event vector mode
after traffic has started results in segfault because
we are receiving few IPSEC packet and application is trying
to decrypt IPSEC packets using lookaside protocol.
This contradicts inline event mode.This patch fixes the same
by freeing IPSEC pa
Hello Bruce,
On Tue, Apr 1, 2025 at 4:08 PM Bruce Richardson
wrote:
>
> On Mon, Mar 24, 2025 at 05:30:26PM +, Bruce Richardson wrote:
> > Traditionally, DPDK has had a direct mapping of internal lcore-ids, to
> > the actual core numbers in use. With higher core count servers becoming
> > more
53 matches
Mail list logo
