Commit 29a1c9107bb disabled interrupts on FreeBSD for the vmxnet3 driver
as they are not supported. Rx queue interrupts were missed by this
change, don't attempt to enable them on FreeBSD.
Without this change applications enabling interrupts encounter an
immediate abort on FreeBSD.
Signed-off-by:
On Wed, Mar 20, 2024 at 11:02 PM Robin Jarry wrote:
>
> In some cases, the node context data is used to store two pointers
> because the data is larger than the reserved 16 bytes. Having to define
> intermediate structures just to be able to cast is tedious. Add two
> pointers that take the same s
21/03/2024 03:02, huangdengdui:
>
> On 2024/3/20 20:31, Ferruh Yigit wrote:
> > On 3/18/2024 9:26 PM, Damodharam Ammepalli wrote:
> >> On Mon, Mar 18, 2024 at 7:56 AM Thomas Monjalon
> >> wrote:
> >>>
> >>> 12/03/2024 08:52, Dengdui Huang:
> Some speeds can be achieved with different number
21/03/2024 02:25, Ma, WenwuX:
> Hi, Thomas
>
> From: Thomas Monjalon
> > 20/03/2024 08:23, Wenwu Ma:
> > > The structure rte_dma_dev needs to be aligned to the cache line, but
> > > the return value of malloc may not be aligned to the cache line. When
> > > we use memset to clear the rte_dma_dev
This commit fixes following issues in the QAT testsuite for
the RSA algorithm:
1) Incorrectly set keys in the internal functions are now
set in the calling function.
2) Camel case functions were changed to the snake case.
Fixes: 9b5465867fb8 ("test/crypto: add RSA none padding cases")
Cc: sta...@
> -Original Message-
> From: Kusztal, ArkadiuszX
> Sent: Thursday, March 21, 2024 8:35 AM
> To: dev@dpdk.org
> Cc: gak...@marvell.com; Power, Ciara ; Kusztal,
> ArkadiuszX ; sta...@dpdk.org
> Subject: [PATCH v3] app/test: fix rsa tests in qat suite
>
> This commit fixes following issue
Add tested Intel platforms with Intel NICs to v24.03 release note.
Signed-off-by: Yu Jiang
---
doc/guides/rel_notes/release_24_03.rst | 133 +
1 file changed, 133 insertions(+)
diff --git a/doc/guides/rel_notes/release_24_03.rst
b/doc/guides/rel_notes/release_24_03.rst
Hi, Thomas
> -Original Message-
> From: Thomas Monjalon
> Sent: Thursday, March 21, 2024 4:31 PM
> To: fengcheng...@huawei.com; Ma, WenwuX
> Cc: dev@dpdk.org; Jiale, SongX ; sta...@dpdk.org
> Subject: Re: [PATCH v3] dmadev: fix structure alignment
>
> 21/03/2024 02:25, Ma, WenwuX:
> > H
Hi, Thomas
> -Original Message-
> From: Thomas Monjalon
> Sent: Thursday, March 21, 2024 4:31 PM
> To: fengcheng...@huawei.com; Ma, WenwuX
> Cc: dev@dpdk.org; Jiale, SongX ; sta...@dpdk.org
> Subject: Re: [PATCH v3] dmadev: fix structure alignment
>
> 21/03/2024 02:25, Ma, WenwuX:
> > H
19/03/2024 08:24, Morten Brørup:
> > From: Sivaprasad Tummala [mailto:sivaprasad.tumm...@amd.com]
> > Sent: Monday, 18 March 2024 18.32
> >
> > Currently the config option allows lcore IDs up to 255,
> > irrespective of RTE_MAX_LCORES and needs to be fixed.
> >
> > The patch allows config options
Commit 29a1c9107bb disabled interrupts on FreeBSD for the vmxnet3 driver
as they are not supported. Rx queue interrupts were missed by this
change, don't attempt to enable them on FreeBSD.
Without this change applications enabling interrupts encounter an
immediate abort on FreeBSD.
Signed-off-by:
21/03/2024 10:18, Ma, WenwuX:
> From: Thomas Monjalon
> > 21/03/2024 02:25, Ma, WenwuX:
> > > From: Thomas Monjalon
> > > > 20/03/2024 08:23, Wenwu Ma:
> > > > > The structure rte_dma_dev needs to be aligned to the cache line,
> > > > > but the return value of malloc may not be aligned to the cac
We should cleanup vq resubmit info when set_inflight_fd
before set_vring_kick which will check if there is any
inflight io waiting for resubmission.
Otherwise, when the vm is rebooting immediately after
reconnecting to the vhost target (inflight io has not
been resubmitted yet), the vhost backend
Hello Tom,
On Thu, Mar 21, 2024 at 11:00 AM Tom Jones wrote:
>
> Commit 29a1c9107bb disabled interrupts on FreeBSD for the vmxnet3 driver
> as they are not supported. Rx queue interrupts were missed by this
> change, don't attempt to enable them on FreeBSD.
>
> Without this change applications en
On Wed, Mar 20, 2024 at 03:01:36PM -0700, Tyler Retzlaff wrote:
> RTE_MARKER typedefs are a GCC extension unsupported by MSVC. Remove
> RTE_MARKER fields from rte_mbuf struct.
>
> Maintain alignment of fields after removed cacheline1 marker by placing
> C11 alignas(RTE_CACHE_LINE_MIN_SIZE).
>
> P
Commit 29a1c9107bb disabled interrupts on FreeBSD for the vmxnet3 driver
as they are not supported. Rx queue interrupts were missed by this
change, don't attempt to enable them on FreeBSD.
Without this change applications enabling interrupts encounter an
immediate abort on FreeBSD.
Fixes: 40d5676
On Thu, Mar 21, 2024, at 10:15, David Marchand wrote:
> Hello Tom,
>
> On Thu, Mar 21, 2024 at 11:00 AM Tom Jones wrote:
>>
>> Commit 29a1c9107bb disabled interrupts on FreeBSD for the vmxnet3 driver
>> as they are not supported. Rx queue interrupts were missed by this
>> change, don't attempt
On 3/21/2024 6:56 AM, Chaoyong He wrote:
> From: Long Wu
>
> Meta data parsing should be controlled by meta data flag. So use
> flag to determine if receive function can use 'port_id' meta data.
>
> Fixes: 580ea0b09a7c ("net/nfp: fix Rx descriptor")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Long
[AMD Official Use Only - General]
Hi Morten,
> -Original Message-
> From: Morten Brørup
> Sent: Tuesday, March 19, 2024 12:54 PM
> To: Tummala, Sivaprasad ;
> david.h...@intel.com; anatoly.bura...@intel.com; jer...@marvell.com;
> radu.nico...@intel.com; gak...@marvell.com; cristian.dumit
[AMD Official Use Only - General]
Hi Thomas,
> -Original Message-
> From: Thomas Monjalon
> Sent: Thursday, March 21, 2024 3:25 PM
> To: Tummala, Sivaprasad
> Cc: david.h...@intel.com; anatoly.bura...@intel.com; jer...@marvell.com;
> radu.nico...@intel.com; gak...@marvell.com; cristian.
21/03/2024 12:05, Tummala, Sivaprasad:
> From: Thomas Monjalon
> > 19/03/2024 08:24, Morten Brørup:
> > > > From: Sivaprasad Tummala [mailto:sivaprasad.tumm...@amd.com]
> > > > Sent: Monday, 18 March 2024 18.32
> > > >
> > > > Currently the config option allows lcore IDs up to 255, irrespective
>
> From: lihuisong (C) [mailto:lihuis...@huawei.com]
> Sent: Thursday, 21 March 2024 04.04
>
> Hi Moren,
>
> Thanks for your revew.
>
> 在 2024/3/20 22:05, Morten Brørup 写道:
> >> From: Huisong Li [mailto:lihuis...@huawei.com]
> >> Sent: Wednesday, 20 March 2024 11.55
> >>
> >> The system-wide CPU
The check to detect if a rule is in resize was done incorrectly,
this can lead to an incorrect function call upon completion for
rules which are not in resize (move).
Since the resize_info is in a union we cannot rely only on the
pointer value but also need to make sure the matcher is in resize
pro
From: Erez Shitrit
In root tables matcher and rule need to have their port-id, otherwise
the translate function that done in dpdk layer will not get the right
attributes.
For that whenever the matcher is matching the source-port we need to get
the relevant port-id before calling the translate fun
On 3/21/2024 10:31 AM, Tom Jones wrote:
> Commit 29a1c9107bb disabled interrupts on FreeBSD for the vmxnet3 driver
> as they are not supported. Rx queue interrupts were missed by this
> change, don't attempt to enable them on FreeBSD.
>
> Without this change applications enabling interrupts encoun
> From: Kevin Traynor
> ...
> Update the policy to indicate 3 years maintenance for LTS releases, but
> note that it depends on community support.
Acked-by: John McNamara
From: Erez Shitrit
In root tables matcher and rule need to have their port-id, otherwise
the translate function that done in dpdk layer will not get the right
attributes.
For that whenever the matcher is matching the source-port we need to get
the relevant port-id before calling the translate fun
Release status meeting minutes 2024-03-21
=
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 date
On Thu, Mar 21, 2024 at 10:32:02AM +, Bruce Richardson wrote:
> On Wed, Mar 20, 2024 at 03:01:36PM -0700, Tyler Retzlaff wrote:
> > RTE_MARKER typedefs are a GCC extension unsupported by MSVC. Remove
> > RTE_MARKER fields from rte_mbuf struct.
> >
> > Maintain alignment of fields after removed
On Wed, 20 Mar 2024 14:05:56 -0700
Tyler Retzlaff wrote:
> MSVC struct packing is not compatible with GCC provide a macro that can
> be used to push existing pack value and sets packing to 1-byte. The
> existing __rte_packed macro is then used to restore the pack value
> prior to the push.
>
> I
On Thu, Mar 21, 2024 at 08:32:19AM -0700, Stephen Hemminger wrote:
> On Wed, 20 Mar 2024 14:05:56 -0700
> Tyler Retzlaff wrote:
>
> > MSVC struct packing is not compatible with GCC provide a macro that can
> > be used to push existing pack value and sets packing to 1-byte. The
> > existing __rte_
On Wed, Mar 20, 2024 at 02:05:58PM -0700, Tyler Retzlaff wrote:
> Add __rte_msvc_pack to all __rte_packed structs to cause packing
> when building with MSVC.
>
> Signed-off-by: Tyler Retzlaff
> ---
> lib/eal/common/eal_private.h | 1 +
> lib/eal/include/rte_memory.h | 1 +
> lib/eal/in
On Thu, Mar 21, 2024 at 11:06:34AM +0100, Thomas Monjalon wrote:
> 21/03/2024 10:18, Ma, WenwuX:
> > From: Thomas Monjalon
> > > 21/03/2024 02:25, Ma, WenwuX:
> > > > From: Thomas Monjalon
> > > > > 20/03/2024 08:23, Wenwu Ma:
> > > > > > The structure rte_dma_dev needs to be aligned to the cache
It is useful for application to be able to set the default log
stream before call rte_eal_init(). This makes all messages go
to the new default.
For example, to skip using syslog; just doing
rte_openlog_stream(stderr);
There is no reason for helper command line applications to clutter
sys
On Wed, Mar 20, 2024 at 02:06:03PM -0700, Tyler Retzlaff wrote:
> Add __rte_msvc_pushpack(1) to all __rte_packed structs to cause packing
> when building with MSVC.
>
> Signed-off-by: Tyler Retzlaff
> ---
> drivers/dma/ioat/ioat_hw_defs.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a
Add documentation of new log-timestamp and log-color options.
Signed-off-by: Stephen Hemminger
---
doc/guides/linux_gsg/eal_args.include.rst | 54 +++
1 file changed, 46 insertions(+), 8 deletions(-)
diff --git a/doc/guides/linux_gsg/eal_args.include.rst
b/doc/guides/linux_
The message already goes through logging, and does not need
to be printed on stderr. Message level should be ALERT
to match function name.
Signed-off-by: Stephen Hemminger
---
lib/eal/freebsd/eal.c | 3 +--
lib/eal/linux/eal.c | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --g
Like dmesg, colorize the log output (unless redirected to file).
Timestamp is green, the subsystem is in yellow and the message
is red if urgent, boldface if an error, and normal for info and
debug messages.
Signed-off-by: Stephen Hemminger
---
lib/eal/common/eal_common_options.c | 10 +++
lib/
Having different prototypes on different platforms can lead
to lots of unnecessary workarounds. Looks like the version of
getopt used from windows was based on an older out of date
version from FreeBSD.
This patch changes getopt, getopt_long, etc to have the same const
attributes as Linux and Fre
Improvements and unification of logging library (for 24.07 release).
This is update to earlier patch set. It adds two new features
to the console log output.
* Putting a timestamp on console output which is useful for
analyzing performance of startup codes. Timestamp is optional
and mus
Want to make sure that as many log messages as possible
get added with the real log stream. Despite the comment,
there is no dependency on memzones in current code.
Signed-off-by: Stephen Hemminger
---
lib/eal/freebsd/eal.c | 14 +++---
lib/eal/linux/eal.c | 16
The code to parse for log-level option should be same on
all OS variants.
Signed-off-by: Stephen Hemminger
---
lib/eal/common/eal_common_options.c | 46 +
lib/eal/common/eal_options.h| 1 +
lib/eal/freebsd/eal.c | 42 --
FreeBSD and Linux logging code can use common code. This also
fixes FreeBSD not using syslog.
Signed-off-by: Stephen Hemminger
---
doc/guides/linux_gsg/linux_eal_parameters.rst | 27 ---
doc/guides/prog_guide/log_lib.rst | 18 +++--
lib/eal/freebsd/eal.c
The rte_exit() output format confuses the timestamp and coloring
options. Change it to use be a single line with proper prefix.
Before:
[ 0.006481] EAL: Error - exiting with code: 1
Cause: [ 0.006489] Cannot init EAL: Permission denied
After:
[ 0.006238] EAL: Error - exiting with co
When debugging driver or startup issues, it is useful to have
a timestamp on each message printed. The messages in syslog
already have a timestamp, but often syslog is not available
during testing.
There are multiple timestamp formats similar to Linux dmesg.
The default is time relative since star
> From: Tyler Retzlaff [mailto:roret...@linux.microsoft.com]
> Sent: Thursday, 21 March 2024 16.31
>
> On Thu, Mar 21, 2024 at 10:32:02AM +, Bruce Richardson wrote:
> > On Wed, Mar 20, 2024 at 03:01:36PM -0700, Tyler Retzlaff wrote:
> > > RTE_MARKER typedefs are a GCC extension unsupported by
On 3/5/2024 8:10 AM, Jiawen Wu wrote:
> On Wed, Feb 7, 2024 11:13 AM, ferruh.yi...@amd.com wrote:
>> On 2/1/2024 3:00 AM, Jiawen Wu wrote:
>>> To optimize Rx/Tx burst process, add SSE/NEON vector instructions on
>>> x86/arm architecture.
>>>
>>
>> Do you have any performance improvement number with
On Thu, Mar 21, 2024 at 08:33:23AM -0700, Stephen Hemminger wrote:
> On Wed, 20 Mar 2024 13:50:46 -0700
> Tyler Retzlaff wrote:
>
> > This series converts all non-generic built atomics to use the rte_atomic
> > macros that allow optional enablement of standard C11 atomics.
> >
> > Use of generic
On Wed, Mar 20, 2024 at 02:06:05PM -0700, Tyler Retzlaff wrote:
> Add __rte_msvc_pushpack(1) to all __rte_packed structs to cause packing
> when building with MSVC.
>
> Signed-off-by: Tyler Retzlaff
> ---
> drivers/net/iavf/iavf_ipsec_crypto.h | 3 +++
> drivers/net/iavf/iavf_rxtx.c | 1
On 3/5/2024 8:10 AM, Jiawen Wu wrote:
<...>
>>> +++ b/drivers/net/txgbe/txgbe_rxtx_vec_neon.c
>>> @@ -0,0 +1,604 @@
>>> +/* SPDX-License-Identifier: BSD-3-Clause
>>> + * Copyright(c) 2015-2024 Beijing WangXun Technology Co., Ltd.
>>> + * Copyright(c) 2010-2015 Intel Corporation
>>> + */
>>> +
>>>
On Wed, Mar 20, 2024 at 02:06:09PM -0700, Tyler Retzlaff wrote:
> Add __rte_msvc_pushpack(1) to all __rte_packed structs to cause packing
> when building with MSVC.
>
> Signed-off-by: Tyler Retzlaff
> ---
> app/test-pmd/csumonly.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/app/tes
On Wed, Mar 20, 2024 at 02:06:11PM -0700, Tyler Retzlaff wrote:
> Add __rte_msvc_pushpack(1) to all __rte_packed structs to cause packing
> when building with MSVC.
>
> Signed-off-by: Tyler Retzlaff
> ---
> examples/common/neon/port_group.h | 1 +
> examples/ip_pipeline/cli.c| 5 +
>
On Thu, Mar 21, 2024 at 09:00:19AM -0700, Stephen Hemminger wrote:
> The code to parse for log-level option should be same on
> all OS variants.
>
> Signed-off-by: Stephen Hemminger
> ---
Acked-by: Tyler Retzlaff
On Thu, Mar 21, 2024 at 09:00:22AM -0700, Stephen Hemminger wrote:
> The rte_exit() output format confuses the timestamp and coloring
> options. Change it to use be a single line with proper prefix.
>
> Before:
> [ 0.006481] EAL: Error - exiting with code: 1
> Cause: [ 0.006489] Cannot i
07/03/2024 11:06, sk...@marvell.com:
> From: Sunil Kumar Kori
>
> Set of CLI commands are classified into following types;
>
> - Commands which must be used in script only.
> - Commands which must be used via telnet session only.
> - Commands which can be used either in script or via telnet sess
On Thu, Mar 21, 2024 at 09:00:23AM -0700, Stephen Hemminger wrote:
> It is useful for application to be able to set the default log
> stream before call rte_eal_init(). This makes all messages go
> to the new default.
>
> For example, to skip using syslog; just doing
> rte_openlog_stream(std
20/03/2024 22:12, Tyler Retzlaff:
> +#ifdef RTE_TOOLCHAIN_MSVC
> +#include
> +#else
> #include
> +#endif
It is not the same include in MSVC?
Is it something we want to wrap in a DPDK header file?
On Thu, Mar 21, 2024 at 09:00:24AM -0700, Stephen Hemminger wrote:
> When debugging driver or startup issues, it is useful to have
> a timestamp on each message printed. The messages in syslog
> already have a timestamp, but often syslog is not available
> during testing.
>
> There are multiple ti
20/03/2024 10:58, Power, Ciara:
> From: Sivaramakrishnan, VenkatX
> >
> > Missing GEN2, GEN3 and GEN4 devices updated for the QAT compression.
> >
> > Signed-off-by: Sivaramakrishnan Venkat
> > ---
> > doc/guides/compressdevs/qat_comp.rst | 4
> > 1 file changed, 4 insertions(+)
> >
> >
On Thu, 21 Mar 2024 10:11:31 -0700
Tyler Retzlaff wrote:
> >
> >
> > +Console timestamp
> > +~
> > +
> > +On Linux and FreeBSD, an optional timestamp can be added before each
> > +message by adding the ``--log-timestamp`` option.
>
> i don't think Windows should be excluded
07/03/2024 18:50, Tyler Retzlaff:
> On Thu, Mar 07, 2024 at 05:14:02PM +0100, David Marchand wrote:
> > All types exposed in a public header must be prefixed with rte_.
> >
> > Fixes: e3e579f5bab5 ("argparse: introduce argparse library")
> >
> > Signed-off-by: David Marchand
>
> Acked-by: Tyler
19/10/2020 17:25, Stephen Hemminger:
> On Mon, 19 Oct 2020 16:11:19 +0200
> Thomas Monjalon wrote:
>
> > There was no ack or conclusion for this patch.
> >
> > 17/08/2020 17:11, Stephen Hemminger:
> > > On Mon, 17 Aug 2020 11:37:40 +0100
> > > Bruce Richardson wrote:
> > >
> > > > On Fri, Au
On Thu, Mar 21, 2024 at 06:09:01PM +0100, Thomas Monjalon wrote:
> 20/03/2024 22:12, Tyler Retzlaff:
> > +#ifdef RTE_TOOLCHAIN_MSVC
> > +#include
> > +#else
> > #include
> > +#endif
>
> It is not the same include in MSVC?
unfortunately intrin.h is vestigial in the monolithic approach. to use
a
18/03/2024 12:18, Chengwen Feng:
> I found a couple of issues when I revisited the argparse_autotest
> output, so got this patchset.
>
> Chengwen Feng (6):
> argparse: refine error message
> argparse: remove dead code
> argparse: replace flag enum with marco
> argparse: fix argument flags
On Thu, Mar 21, 2024 at 10:16:36AM -0700, Stephen Hemminger wrote:
> On Thu, 21 Mar 2024 10:11:31 -0700
> Tyler Retzlaff wrote:
>
> > >
> > >
> > > +Console timestamp
> > > +~
> > > +
> > > +On Linux and FreeBSD, an optional timestamp can be added before each
> > > +message by
March 21, 2024
#
Attendees
1. Patrick Robb
2. Aaron Conole
3. Nicholas Pratte
4. Jeremy Spewock
5. Cody Cheng
#
Minutes
On Thu, Mar 21, 2024 at 04:27:26PM +, Ferruh Yigit wrote:
> On 3/5/2024 8:10 AM, Jiawen Wu wrote:
>
> <...>
>
> >>> +++ b/drivers/net/txgbe/txgbe_rxtx_vec_neon.c
> >>> @@ -0,0 +1,604 @@
> >>> +/* SPDX-License-Identifier: BSD-3-Clause
> >>> + * Copyright(c) 2015-2024 Beijing WangXun Technology
21/03/2024 18:27, Tyler Retzlaff:
> On Thu, Mar 21, 2024 at 06:09:01PM +0100, Thomas Monjalon wrote:
> > 20/03/2024 22:12, Tyler Retzlaff:
> > > +#ifdef RTE_TOOLCHAIN_MSVC
> > > +#include
> > > +#else
> > > #include
> > > +#endif
> >
> > It is not the same include in MSVC?
>
> unfortunately in
Tyler Retzlaff writes:
> Replace the use of gcc builtin __atomic_xxx intrinsics with
> corresponding rte_atomic_xxx optional rte stdatomic API.
>
> Signed-off-by: Tyler Retzlaff
> ---
> drivers/net/sfc/meson.build | 5 ++---
> drivers/net/sfc/sfc_mae_counter.c | 30 +++---
On Thu, Mar 21, 2024 at 02:11:00PM -0400, Aaron Conole wrote:
> Tyler Retzlaff writes:
>
> > Replace the use of gcc builtin __atomic_xxx intrinsics with
> > corresponding rte_atomic_xxx optional rte stdatomic API.
> >
> > Signed-off-by: Tyler Retzlaff
> > ---
> > drivers/net/sfc/meson.build
On Thu, Mar 21, 2024 at 07:01:17PM +0100, Thomas Monjalon wrote:
> 21/03/2024 18:27, Tyler Retzlaff:
> > On Thu, Mar 21, 2024 at 06:09:01PM +0100, Thomas Monjalon wrote:
> > > 20/03/2024 22:12, Tyler Retzlaff:
> > > > +#ifdef RTE_TOOLCHAIN_MSVC
> > > > +#include
> > > > +#else
> > > > #include
>
[AMD Official Use Only - General]
> -Original Message-
> From: Thomas Monjalon
> Sent: Thursday, March 21, 2024 4:48 PM
> To: Tummala, Sivaprasad
> Cc: david.h...@intel.com; anatoly.bura...@intel.com; jer...@marvell.com;
> radu.nico...@intel.com; gak...@marvell.com; cristian.dumitre...@i
Currently application supports queue IDs up to 255
and max queues of 256 irrespective of device support.
This limits the number of active lcores to 256.
The patch fixes these constraints by increasing
the queue IDs to support up to 65535.
Fixes: af75078fece3 ("first public release")
Cc: sta...@dp
With modern CPUs, it is possible to have higher
CPU count thus we can have higher RTE_MAX_LCORES.
In DPDK sample applications, the current config
lcore options are hard limited to 255.
The patchset fixes these constraints by allowing
all lcore IDs up to RTE_MAX_LCORES. Also the queue
IDs are incre
Currently application supports queue IDs up to 255
and max queues of 256 irrespective of device support.
This limits the number of active lcores to 256.
The patch fixes these constraints by increasing
the queue IDs to support up to 65535.
Fixes: f88e7c175a68 ("examples/l3fwd-power: add high/regul
Currently application supports queue IDs up to 255
and max queues of 256 irrespective of device support.
This limits the number of active lcores to 256.
The patch fixes these constraints by increasing
the queue IDs to support up to 65535.
Fixes: 08bd1a174461 ("examples/l3fwd-graph: add graph-base
Currently application supports queue IDs up to 255
and max queues of 256 irrespective of device support.
This limits the number of active lcores to 256.
The patch fixes these constraints by increasing
the queue IDs to support up to 65535.
Signed-off-by: Sivaprasad Tummala
Acked-by: Konstantin An
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch fixes these constraints by allowing all
lcore IDs up to RTE_MAX_LCORES.
Fixes: af75078fece3 ("first public release")
Cc: sta...@dpdk.org
Signed-off-by: Sivaprasad Tummala
Acke
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch fixes these constraints by allowing all
lcore IDs up to RTE_MAX_LCORES.
Fixes: f88e7c175a68 ("examples/l3fwd-power: add high/regular perf cores
options")
Cc: radu.nico...@intel
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch fixes these constraints by allowing all
lcore IDs up to RTE_MAX_LCORES. Also the queue
IDs are increased to support up to 65535.
Fixes: 08bd1a174461 ("examples/l3fwd-graph: add
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch fixes these constraints by allowing all
lcore IDs up to RTE_MAX_LCORES. Also the queue
IDs are increased to support up to 65535.
Fixes: d299106e8e31 ("examples/ipsec-secgw: add
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch fixes these constraints by allowing all
lcore IDs up to RTE_MAX_LCORES. Also the queue
IDs are increased to support up to 65535.
Fixes: de3cfa2c9823 ("sched: initial import")
Cc
Currently the config option allows lcore IDs up to 255,
irrespective of RTE_MAX_LCORES and needs to be fixed.
The patch fixes these constraints by allowing all
lcore IDs up to RTE_MAX_LCORES. Also the queue
IDs are increased to support up to 65535.
Fixes: 0e8f47491f09 ("examples/vm_power: add com
Currently application supports port IDs up to 255
irrespective of RTE_MAX_ETHPORTS.
The patch fixes these constraints by allowing port
IDs up to RTE_MAX_ETHPORTS.
Fixes: af75078fece3 ("first public release")
Cc: sta...@dpdk.org
Signed-off-by: Sivaprasad Tummala
Acked-by: Konstantin Ananyev
Ack
Currently application supports port IDs up to 255
irrespective of RTE_MAX_ETHPORTS.
The patch fixes these constraints by allowing port
IDs up to RTE_MAX_ETHPORTS.
Fixes: f88e7c175a68 ("examples/l3fwd-power: add high/regular perf cores
options")
Cc: radu.nico...@intel.com
Cc: sta...@dpdk.org
Sig
Currently application supports port IDs up to 255
irrespective of RTE_MAX_ETHPORTS.
The patch fixes these constraints by allowing port
IDs up to RTE_MAX_ETHPORTS.
Fixes: d299106e8e31 ("examples/ipsec-secgw: add IPsec sample application")
Cc: sergio.gonzalez.mon...@intel.com
Cc: sta...@dpdk.org
S
With modern CPUs, it is possible to have higher
CPU count thus we can have higher RTE_MAX_LCORES.
In DPDK sample applications, the current config
lcore options are hard limited to 255.
The patchset fixes these constraints by allowing
all lcore IDs up to RTE_MAX_LCORES. Also the queue
IDs are incre
Currently application supports port IDs up to 255
irrespective of RTE_MAX_ETHPORTS.
The patch fixes these constraints by allowing port
IDs up to RTE_MAX_ETHPORTS.
Fixes: 08bd1a174461 ("examples/l3fwd-graph: add graph-based l3fwd skeleton")
Cc: ndabilpu...@marvell.com
Cc: sta...@dpdk.org
Signed-o
This series converts all non-generic built atomics to use the rte_atomic
macros that allow optional enablement of standard C11 atomics.
Use of generic atomics for non-scalar types are not converted in this
change and will be evaluated as a part of a separate series.
Note if this series ends up re
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/ixgbe/ixgbe_ethdev.c | 14 --
drivers/net/ixgbe/ixgbe_ethdev.h | 2 +-
drivers/net/ixgbe/ixgbe_rxtx.c | 4 ++--
3 fil
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/mlx5/linux/mlx5_ethdev_os.c | 6 +-
drivers/net/mlx5/linux/mlx5_verbs.c | 9 ++-
drivers/net/mlx5/mlx5.c |
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/iavf/iavf.h | 16
drivers/net/iavf/iavf_rxtx.c | 4 ++--
drivers/net/iavf/iavf_rxtx_vec_neon
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/ice/base/ice_osdep.h | 4 ++--
drivers/net/ice/ice_dcf.c| 6 +++---
drivers/net/ice/ice_dcf.h| 2 +-
drivers/net/i
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/hns3/hns3_cmd.c | 18 ++--
drivers/net/hns3/hns3_dcb.c | 2 +-
drivers/net/hns3/hns3_ethdev.c| 36 ++
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/i40e/i40e_ethdev.c| 4 ++--
drivers/net/i40e/i40e_rxtx.c | 6 +++---
drivers/net/i40e/i40e_rxtx_vec_neon.c | 2 +-
3
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/bnxt/bnxt_cpr.h | 4 ++--
drivers/net/bnxt/bnxt_rxq.h | 2 +-
drivers/net/bnxt/bnxt_rxr.c | 13 ++
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/cpfl/cpfl_ethdev.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/net/cpfl/cpfl_ethdev.c b/drive
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/af_xdp/rte_eth_af_xdp.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/drivers/net/af_xdp/
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/octeon_ep/cnxk_ep_rx.h| 5 +++--
drivers/net/octeon_ep/cnxk_ep_tx.c| 5 +++--
drivers/net/octeon_ep/cnxk_ep_vf.c| 8 -
Replace the use of gcc builtin __atomic_xxx intrinsics with
corresponding rte_atomic_xxx optional rte stdatomic API.
Signed-off-by: Tyler Retzlaff
---
drivers/net/octeontx/octeontx_ethdev.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/octeontx/octeontx_
1 - 100 of 149 matches
Mail list logo
