On Thu, May 28, 2020 at 9:08 PM Ananyev, Konstantin
wrote:
>
>
> > > Hi Anatoly,
> > >
> > >>
> > >> Add two new power management intrinsics, and provide an implementation
> > >> in eal/x86 based on UMONITOR/UMWAIT instructions. The instructions
> > >> are implemented as raw byte opcodes because t
On Tue, 26 May 2020 19:24:55 +0200
Hrvoje Habjanic wrote:
> In function rte_sched_subport_free (lib/librte_sched/rte_sched.c,
> line 865), there is code to free all allocated stuff related to
> scheduler subport. First there are some checks, and in the end,
> rte_bitmap_free is called.
>
> Now,
On Wed, 27 May 2020 15:31:41 +0100
Andrew Rybchenko wrote:
> SW VLAN insertion relies on Ethernet addresses location in contigous
> memory (do not split across mbuf segments). There is no any formal
> requirements on data location and mbuf structure which guarantee it.
> So, check it explicitly t
Add the dependent header files explicitly, so that the user just needs
to include the 'rte_uuid.h' header file directly to avoid compile error:
(1). rte_uuid.h:97:55: error: unknown type name ‘size_t’
(2). rte_uuid.h:58:2: error: implicit declaration of function ‘memcpy’
Fixes: 6bc67c497a51 ("ea
v15: Add the missed EXPERIMENTAL warning for API doxgen.
v14: Rebase the patch for 20.08 release note.
v13: Rename the EAL get VF token function, and leave the freebsd type as empty.
v12: support to vfio devices with VF token and no token.
v11: Use the eal parameter to pass the VF token, then n
The kernel module vfio-pci introduces the VF token to enable SR-IOV
support since 5.7.
The VF token can be set by a vfio-pci based PF driver and must be known
by the vfio-pci based VF driver in order to gain access to the device.
Signed-off-by: Haiyue Wang
Acked-by: Anatoly Burakov
Acked-by: An
> -Original Message-
> From: Ye, Xiaolong
> Sent: Friday, May 29, 2020 09:26
> To: Wang, Haiyue
> Cc: dev@dpdk.org; Burakov, Anatoly ;
> tho...@monjalon.net;
> jer...@marvell.com; david.march...@redhat.com; arybche...@solarflare.com
> Subject: Re: [dpdk-dev] [PATCH v14 2/2] eal: support
On 05/28, Haiyue Wang wrote:
>The kernel module vfio-pci introduces the VF token to enable SR-IOV
>support since 5.7.
>
>The VF token can be set by a vfio-pci based PF driver and must be known
>by the vfio-pci based VF driver in order to gain access to the device.
>
>Signed-off-by: Haiyue Wang
>Ac
On 05/28, Haiyue Wang wrote:
>The PCI DSN (device serial number) to format package file name should be
>lowercase values.
>
>Fixes: d1c91179e952 ("net/ice: check DSN package file firstly")
>
>Signed-off-by: Haiyue Wang
>---
> drivers/net/ice/ice_dcf_parent.c | 4 ++--
> 1 file changed, 2 insertions
Added -Werror in meson file to consider all the warnings
as errors on Windows.
Signed-off-by: Pallavi Kadam
Reviewed-by: Ranjit Menon
---
config/meson.build | 4
1 file changed, 4 insertions(+)
diff --git a/config/meson.build b/config/meson.build
index 43ab11310..c3c1c0c4e 100644
--- a/co
This patchset fixes all the Windows compiler warnings generated using
Clang and MinGW compiler.
Henceforth, all the warnings will be treated as errors on Windows.
v3 changes:
Fixed pthread warning
Added -Werror on Windows
Fixed MinGW warnings
v2 changes:
Excluded d
Fixed bunch of warnings when compiling using clang on Windows
such as the use of an unsafe string function (strerror),
[-Wunused-variable], [-Wunused-function] in eal_common_options.c
[-Wunused-const-variable] in getopt.c and [-Wunused-parameter]
in eal_common_thread.c.
Also fixed warnings generate
>
> Hello Honnappa,
>
> On Fri, May 22, 2020 at 4:16 PM Honnappa Nagarahalli
> wrote:
> > > @@ -11,7 +11,8 @@
> > > * Wireless base band device abstraction APIs.
> > > *
> > > * @warning
> > > - * @b EXPERIMENTAL: this API may change without prior notice
> > > + * @b EXPERIMENTAL:
> > >
> > Zoom vs Skype
> > -
> >
> > * Linux foundation is providing zoom accounts and should we switch the
> meetings
> > to the Zoom, as done in the regular CI meetings?
> >
> > * It seems Skype is not performing well on Linux
> >
> > * There can be some limitations using Zoom for some
On Thu, 28 May 2020 16:55:55 +0100
Ferruh Yigit wrote:
> Minutes 28 May 2020
> ---
>
> Agenda:
> * Release Dates
> * Zoom vs Skype
> * 20.05 retrospective
> * LTS
>
> Participants:
> * Arm
> * Debian/Microsoft
> * Intel
> * Mellanox
> * NXP
> * Red Hat
>
>
> Release Dates
> --
On Thu, 28 May 2020 20:03:07 +0800
wangyunjian wrote:
> From: Yunjian Wang
>
> We do not need and should not allocate memory for device.name.
> The device.name should be set point to the devargs->name.
>
> Fixes: 831dba47bd36 ("bus/vmbus: add Hyper-V virtual bus support")
> Cc: sta...@dpdk.org
Minutes 28 May 2020
---
Agenda:
* Release Dates
* Zoom vs Skype
* 20.05 retrospective
* LTS
Participants:
* Arm
* Debian/Microsoft
* Intel
* Mellanox
* NXP
* Red Hat
Release Dates
-
* v20.05 is released on Tuesday 26 May
* https://mails.dpdk.org/archives/dev/2020-
Hi Olivier,
On Fri, May 15, 2020 at 07:27:46PM +0530, Nithin Dabilpuram wrote:
> On Fri, May 15, 2020 at 10:30:30AM +, Ananyev, Konstantin wrote:
> >
> > > On Thu, May 14, 2020 at 10:29:31PM +0200, Olivier Matz wrote:
> > > > Hi Nithin,
> > > >
> > > > On Tue, May 05, 2020 at 11:49:20AM +0530
> > Hi Anatoly,
> >
> >>
> >> Add two new power management intrinsics, and provide an implementation
> >> in eal/x86 based on UMONITOR/UMWAIT instructions. The instructions
> >> are implemented as raw byte opcodes because there is not yet widespread
> >> compiler support for these instructions.
>
28/05/2020 17:04, Gage Eads:
> The stack library was first released in 19.05, and its interfaces have been
> stable since their initial introduction. This commit promotes the full
> interface to stable, starting with the 20.11 major version.
>
> Signed-off-by: Gage Eads
> ---
> doc/guides/rel_no
The stack library was first released in 19.05, and its interfaces have been
stable since their initial introduction. This commit promotes the full
interface to stable, starting with the 20.11 major version.
Signed-off-by: Gage Eads
---
doc/guides/rel_notes/release_20_11.rst | 3 +++
lib/librte_
28/05/2020 16:37, Power, Ciara:
> From: Thomas Monjalon
> >06/05/2020 11:55, Ciara Power:
> >> This patch modifies the arguments expected by the check-git-log
> >> script, to match the format of arguments for the checkpatches script.
> >> Both scripts now take certain argument options in the same
On Thu, May 28, 2020 at 03:40:18PM +0100, Burakov, Anatoly wrote:
> On 28-May-20 12:39 PM, Ananyev, Konstantin wrote:
> > Hi Anatoly,
> >
> > >
> > > Add two new power management intrinsics, and provide an implementation
> > > in eal/x86 based on UMONITOR/UMWAIT instructions. The instructions
> >
On Thu, 28 May 2020 12:46:49 +0100
"Burakov, Anatoly" wrote:
> On 25-May-20 1:37 AM, Dmitry Kozlyuk wrote:
> > All supported OS create memory segment lists (MSL) and reserve VA space
> > for them in a nearly identical way. Move common code into EAL private
> > functions to reduce duplication.
> >
On 28-May-20 12:39 PM, Ananyev, Konstantin wrote:
Hi Anatoly,
Add two new power management intrinsics, and provide an implementation
in eal/x86 based on UMONITOR/UMWAIT instructions. The instructions
are implemented as raw byte opcodes because there is not yet widespread
compiler support for t
Hi Thomas,
>-Original Message-
>From: Thomas Monjalon
>Sent: Sunday 24 May 2020 21:58
>To: Power, Ciara
>Cc: dev@dpdk.org
>Subject: Re: [dpdk-dev] [PATCH v2 1/2] devtools: standardize script
>arguments
>
>06/05/2020 11:55, Ciara Power:
>> This patch modifies the arguments expected by th
On Thu, May 28, 2020 at 02:18:32PM +, Eads, Gage wrote:
>
>
> > -Original Message-
> > From: Thomas Monjalon
> > Sent: Thursday, May 28, 2020 3:11 AM
> > To: Eads, Gage ; Ray Kinsella
> > Cc: dev@dpdk.org; david.march...@redhat.com; nhor...@tuxdriver.com;
> > phil.y...@arm.com; honn
> -Original Message-
> From: Thomas Monjalon
> Sent: Thursday, May 28, 2020 3:11 AM
> To: Eads, Gage ; Ray Kinsella
> Cc: dev@dpdk.org; david.march...@redhat.com; nhor...@tuxdriver.com;
> phil.y...@arm.com; honnappa.nagaraha...@arm.com;
> olivier.m...@6wind.com
> Subject: Re: [PATCH] s
On Thu, 28 May 2020 13:21:06 +0100
"Burakov, Anatoly" wrote:
> On 25-May-20 1:37 AM, Dmitry Kozlyuk wrote:
> > Code in Linux EAL that supports dynamic memory allocation (as opposed to
> > static allocation used by FreeBSD) is not OS-dependent and can be reused
> > by Windows EAL. Move such code t
On Sun, May 24, 2020 at 7:43 PM Thomas Monjalon wrote:
>
> When building an ABI reference with meson, some static libraries
> are built and linked in apps. They are useless and take a lot of space.
> Those binaries, and other useless files (examples and doc files)
> in the share/ directory, are re
On 28-May-20 1:39 PM, Burakov, Anatoly wrote:
On 22-May-20 2:23 PM, Louise Kilheeney wrote:
Changed script to explicitly use python3 only.
Signed-off-by: Louise Kilheeney
---
There is a bunch of old cruft in a few scripts, such as python
compatibility checks and reimplementation of check_ou
On 22-May-20 2:23 PM, Louise Kilheeney wrote:
Changed script to explicitly use python3 only.
Signed-off-by: Louise Kilheeney
---
There is a bunch of old cruft in a few scripts, such as python
compatibility checks and reimplementation of check_output. it would be
nice if those were fixed as
On Sun, May 24, 2020 at 7:30 PM Thomas Monjalon wrote:
>
> Some compilers raise an error when declaring a variable
> in the middle of a function. This is a C99 allowance.
> Even if DPDK switches globally to C99 or C11 standard,
> the coding rules are for declarations at the beginning
> of a block:
On 25-May-20 1:37 AM, Dmitry Kozlyuk wrote:
Code in Linux EAL that supports dynamic memory allocation (as opposed to
static allocation used by FreeBSD) is not OS-dependent and can be reused
by Windows EAL. Move such code to a file compiled only for the OS that
require it.
Signed-off-by: Dmitry K
On 25-May-20 1:37 AM, Dmitry Kozlyuk wrote:
All supported OS create memory segment lists (MSL) and reserve VA space
for them in a nearly identical way. Move common code into EAL private
functions to reduce duplication.
Signed-off-by: Dmitry Kozlyuk
---
+void
+eal_memseg_list_populate(struc
>
> Add a simple on/off switch that will enable saving power when no
> packets are arriving. It is based on counting the number of empty
> polls and, when the number reaches a certain threshold, entering an
> architecture-defined optimized power state that will either wait
> until a TSC timestamp
From: Yunjian Wang
We do not need and should not allocate memory for device.name.
The device.name should be set point to the devargs->name.
Fixes: 831dba47bd36 ("bus/vmbus: add Hyper-V virtual bus support")
Cc: sta...@dpdk.org
Signed-off-by: Yunjian Wang
---
drivers/bus/vmbus/linux/vmbus_bus.
https://bugs.dpdk.org/show_bug.cgi?id=486
Bug ID: 486
Summary: i40e driver has very bad performance when VXLAN TSO is
enabled
Product: DPDK
Version: 19.11
Hardware: x86
OS: Linux
Status: UNCONFIR
On 25-May-20 1:37 AM, Dmitry Kozlyuk wrote:
Introduce OS-independent wrappers for memory management operations used
across DPDK and specifically in common code of EAL:
* rte_mem_map()
* rte_mem_unmap()
* rte_get_page_size()
* rte_mem_lock()
Windows uses different APIs for memory mapping and res
On 25-May-20 1:37 AM, Dmitry Kozlyuk wrote:
All supported OS create memory segment lists (MSL) and reserve VA space
for them in a nearly identical way. Move common code into EAL private
functions to reduce duplication.
Signed-off-by: Dmitry Kozlyuk
---
+eal_memseg_list_alloc(struct rte_mem
Hi Anatoly,
>
> Add two new power management intrinsics, and provide an implementation
> in eal/x86 based on UMONITOR/UMWAIT instructions. The instructions
> are implemented as raw byte opcodes because there is not yet widespread
> compiler support for these instructions.
>
> The power managemen
28/05/2020 12:09, Dmitry Kozlyuk:
> On Thu, 28 May 2020 09:59:13 +0200
> Thomas Monjalon wrote:
>
> > 25/05/2020 02:37, Dmitry Kozlyuk:
> > > * eal_file_lock: lock or unlock an open file.
> > > * eal_file_truncate: enforce a given size for an open file.
> > [...]
> > > Implementation for Linux
On 25-May-20 1:37 AM, Dmitry Kozlyuk wrote:
Introduce OS-independent wrappers for memory management operations used
across DPDK and specifically in common code of EAL:
* rte_mem_map()
* rte_mem_unmap()
* rte_get_page_size()
* rte_mem_lock()
Windows uses different APIs for memory mapping and res
On Thu, 28 May 2020 09:59:13 +0200
Thomas Monjalon wrote:
> 25/05/2020 02:37, Dmitry Kozlyuk:
> > * eal_file_lock: lock or unlock an open file.
> > * eal_file_truncate: enforce a given size for an open file.
> [...]
> > Implementation for Linux and FreeBSD is placed in "unix" subdirectory,
> >
On Thu, 2020-05-28 at 11:14 +0200, David Marchand wrote:
> On Wed, May 27, 2020 at 2:17 PM David Marchand
> wrote:
> > > With Doxygen 1.8.18, a warning appears when tagging
> > > the main markdown header with {#index}.
> > > That's why the tag has been removed from the API index in DPDK 20.05.
> >
On Thu, 28 May 2020 09:31:54 +0200
Thomas Monjalon wrote:
> 25/05/2020 02:37, Dmitry Kozlyuk:
> > All supported OS create memory segment lists (MSL) and reserve VA space
> > for them in a nearly identical way. Move common code into EAL private
> > functions to reduce duplication.
> >
> > Signed-
Hi, Harris, Cody
I have reply in other mail for " why imissed doesn't include it ", thanks.
> -Original Message-
> From: Harris, Cody
> Sent: Thursday, May 28, 2020 4:17 PM
> To: Zhao1, Wei ; dev@dpdk.org
> Cc: Ye, Xiaolong ; Guo, Jia
> Subject: Re: [dpdk-dev] [PATCH v3] net/ixgbe: in
Currently, the DevX counter query works asynchronously with Devx
interrupt handler return the query result. When port closes, the
interrupt handler will be uninstalled and the Devx comp obj will
also be destroyed. Meanwhile the query is still not cancelled.
In this case, counter query may use the
On Wed, May 27, 2020 at 2:17 PM David Marchand
wrote:
> > With Doxygen 1.8.18, a warning appears when tagging
> > the main markdown header with {#index}.
> > That's why the tag has been removed from the API index in DPDK 20.05.
> > Unfortunately it makes the index page classified as a standard
> >
In addition to existing modes, add a mode which is very similar to
legacy mode, but does not do frequency scaling, and thus does not
depend on the power library.
Signed-off-by: Anatoly Burakov
---
examples/l3fwd-power/main.c | 215 +---
1 file changed, 202 inserti
Currently, l3fwd-power will attempt to run even if the power env
is set to KVM, which is not supported. Fix this by preventing the
app from initializing unless the env is set to one of the supported
modes.
Signed-off-by: Anatoly Burakov
---
examples/l3fwd-power/main.c | 9 +
1 file chang
Since 20.05, l3fwd-power has become much more stringent about
whether it allows initialization without initializing the
librte_power library with it. This means that while previously
the app could have been used to test RX interrupts functionality
even if the app itself was in a half-working state,
Currently, interrupts are enabled in telemetry and empty poll modes, but
they are not used. Switch to disabling interrupts by default, and only
enable interrupts for modes that require them.
Signed-off-by: Anatoly Burakov
---
examples/l3fwd-power/main.c | 12 +++-
1 file changed, 7 inser
As announced during v20.05 release cycle, this
patch makes reply-ack protocol feature to be enabled
unconditionally.
This protocol feature makes the communication between the
master and the slave more robust, avoiding for example
possible undefined behaviour with VHOST_USER_SET_MEM_TABLE.
Also, r
> From: Konstantin Ananyev [mailto:konstantin.anan...@intel.com]
> Sent: Wednesday, May 27, 2020 4:17 PM
>
> Make x86 JIT to generate native code for
> (BPF_ABS | | BPF_LD) and (BPF_IND | | BPF_LD)
> instructions.
>
> Signed-off-by: Konstantin Ananyev
> ---
[...]
> +/*
> + * helper function,
25/05/2020 02:37, Dmitry Kozlyuk:
> Code in Linux EAL that supports dynamic memory allocation (as opposed to
> static allocation used by FreeBSD) is not OS-dependent and can be reused
> by Windows EAL. Move such code to a file compiled only for the OS that
> require it.
>
> Signed-off-by: Dmitry K
As announced dunring v20.05 release cycle, this
patch makes reply-ack protocol feature to be enabled
unconditionally.
This protocol feature makes the communication between the
master and the slave more robust, avoiding for example
possible undefined behaviour with VHOST_USER_SET_MEM_TABLE.
Also,
On 28/05/2020 09:10, Thomas Monjalon wrote:
> Anyway I think it deserves a comment in the release notes (API section).
agreed
Hi Zhao Wei,
I understand that the QPRDC drop count is available by stats->q_errors. I'm
interested to know why imissed doesn't include it. The name imissed makes it
sound like the counter counts incoming missed (valid) packets regardless of
where the drop occurs during reception.
I think the
28/05/2020 07:46, Ray Kinsella:
> Hi Gage,
>
> Do you have any idea.
> If the change from experimental to stable symbol is likely to break anyone's
> application?
> (are folks actively using the api with shared libraries)
>
> If so, you _may_ consider offering a temporary alias to experimental u
Hi, Cody Harris
More info, you can get the number of dropped packet per queue by
stats->q_errors,
No need to add this into imissed.
> -Original Message-
> From: Zhao1, Wei
> Sent: Thursday, May 28, 2020 11:54 AM
> To: Cody Harris ; dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v3] net
25/05/2020 02:37, Dmitry Kozlyuk:
> * eal_file_lock: lock or unlock an open file.
> * eal_file_truncate: enforce a given size for an open file.
[...]
> Implementation for Linux and FreeBSD is placed in "unix" subdirectory,
> which is intended for common code between the two. Files should be named
>
This patch adds support reply-ack vhost-user protocol
feature, which is for now only used to ensure
VHOST_USER_SET_MEM_TABLE requests are handled by the
slave, but later will be used for VHOST_USER_SET_STATUS.
Signed-off-by: Maxime Coquelin
---
drivers/net/virtio/virtio_user/vhost.h| 6
This patch adds support for VHOST_USER_SET_STATUS
request. It is used to make the backend aware of
Virtio devices status update.
It is useful for the backend to know when the Virtio
driver is done with the Virtio device configuration.
Signed-off-by: Maxime Coquelin
---
drivers/net/virtio/virtio
This series adds Vhost-user protocol features support
to Virtio-user PMD's Vhost-user backend.
The first patch introduces protocol features
negotiation, and the second one reply-ack feature.
The third patch adds support to the SET_STATUS
request, which is not merged upstream yet. Neither
in DPDK
This patch adds support for Vhost-user protocol features.
It is required to support protocol features that were not in
initial Vhost-user specification, such as reply-ack, MTU...
Also, this patch prevents Virtio multiqueue feature negotiation
if the slave does not support MQ protocol feature as st
25/05/2020 02:37, Dmitry Kozlyuk:
> All supported OS create memory segment lists (MSL) and reserve VA space
> for them in a nearly identical way. Move common code into EAL private
> functions to reduce duplication.
>
> Signed-off-by: Dmitry Kozlyuk
> ---
> +void
> +eal_memseg_list_populate(struct
When secondary process starts, it will allocate its own process private
data, and also does remap to UAR register of the Tx queue. Once the
secondary process exits, these resources should be released accordingly.
And the shared resources owned by primary should not be touched.
Currently, once one
68 matches
Mail list logo