From: Pavan Nikhilesh
Add 64 byte padding at the end of event device public structure to allow
future extensions.
Signed-off-by: Pavan Nikhilesh
Acked-by: Jerin Jacob
---
v2 Changes:
- Modify commit title.
- Add patch reference to doc.
doc/guides/rel_notes/deprecation.rst | 11 +++
On Mon, Aug 03, 2020 at 09:26:40AM +0800, yang_y_yi wrote:
> At 2020-08-03 04:29:07, "Olivier Matz" wrote:
> >Hi,
> >
> >On Sun, Aug 02, 2020 at 07:12:36AM +0800, yang_y_yi wrote:
> >>
> >>
> >> At 2020-07-31 23:15:43, "Olivier Matz" wrote:
> >> >Hi,
> >> >
> >> >On Thu, Jul 30, 2020 at 08:08:5
When a virtq is destroyed, the SW should be able to continue the virtq
processing from where the HW stopped.
The current destroy behavior in the driver saves the virtq state (used
and available indexes) only when LM is requested.
So, when LM is not requested the queue state is not saved and the SW
Hi Nicolas,
On 7/31/20 5:17 PM, Chautru, Nicolas wrote:
> Hi Maxime,
>
>>
>> Hi Nicolas,
>>
>> On 7/16/20 10:20 PM, Nicolas Chautru wrote:
>>> Adding companion application to configure HW Device from the PF.
>>> Then the device can be accessed through BBDEV from VF (or PF).
>>>
>>> Signed-off-by
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Olivier Matz
> Sent: Friday, July 31, 2020 5:25 PM
>
> Hi Morten,
>
> Thanks for the feedback.
>
> On Mon, Jul 13, 2020 at 11:57:38AM +0200, Morten Brørup wrote:
>
> > The MBUF library exposes some macros and constants without the RTE_
> pr
Previous patch added definition of number of retries for UAR allocation.
This value is adequate for x86 systems with 4K pages.
On power9 system with 64K pages the required value is 32.
This patch updates the defined value from 2 to 32.
Fixes: a0bfe9d56f74 ("net/mlx5: fix UAR memory mapping type")
At 2020-08-03 16:11:39, "Olivier Matz" wrote:
>On Mon, Aug 03, 2020 at 09:26:40AM +0800, yang_y_yi wrote:
>> At 2020-08-03 04:29:07, "Olivier Matz" wrote:
>> >Hi,
>> >
>> >On Sun, Aug 02, 2020 at 07:12:36AM +0800, yang_y_yi wrote:
>> >>
>> >>
>> >> At 2020-07-31 23:15:43, "Olivier Matz" wrote:
On 8/2/20 11:21 AM, Xueming Li wrote:
> The driver CQ event management is done by non vhost library thread,
> either the dpdk host thread or the internal vDPA driver thread.
>
> When a queue is updated the CQ may be destroyed and created by the vhost
> library thread via the queue state operati
Added eal functions used by ethdev lib to the export list under Windows.
Signed-off-by: Fady Bader
---
lib/librte_eal/rte_eal_exports.def | 11 +++
1 file changed, 11 insertions(+)
diff --git a/lib/librte_eal/rte_eal_exports.def
b/lib/librte_eal/rte_eal_exports.def
index 69204a92c6..78
Telemetry didn't compile under Windows.
Empty stubs implementation was added for Windows.
Signed-off-by: Fady Bader
---
lib/librte_telemetry/rte_telemetry.h| 4 +++
lib/librte_telemetry/telemetry.c| 52 -
lib/librte_telemetry/telemetry_legacy.c | 26 +
Some ethdev structs were present in ethdev export list.
There structs were removed from the export list.
Signed-off-by: Fady Bader
---
lib/librte_ethdev/rte_ethdev_version.map | 2 --
1 file changed, 2 deletions(-)
diff --git a/lib/librte_ethdev/rte_ethdev_version.map
b/lib/librte_ethdev/rte_e
The ethdev lib uses interrupts. Interrupts are not implemented for Windows.
To solve this, empty interrupt stubs were added under Windows.
Signed-off-by: Fady Bader
---
lib/librte_eal/windows/eal_interrupts.c | 17 +
lib/librte_eal/windows/meson.build | 1 +
2 files changed
Compiling needed libraries for ethdev under Windows.
Signed-off-by: Fady Bader
---
lib/meson.build | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/meson.build b/lib/meson.build
index 6bbaf242a9..c145240eb9 100644
--- a/lib/meson.build
+++ b/lib/meson.build
@@ -38,9 +38,
Added needed changes in order to get ethdev compiling under windows.
Depends-on: series-10382 ("compile librte_net for windows")
v3: rebased on current master, added more exports to export list
v2: fixed logging issue in telemetry lib.
Fady Bader (5):
eal: added interrupts empty stubs
eal:
03/08/2020 10:42, Morten Brørup:
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Olivier Matz
> > Sent: Friday, July 31, 2020 5:25 PM
> >
> > Hi Morten,
> >
> > Thanks for the feedback.
> >
> > On Mon, Jul 13, 2020 at 11:57:38AM +0200, Morten Brørup wrote:
> >
> > > The MBUF library ex
From: Shahaji Bhosle
Adjusted resource allocations for the hardware resources
like TCAM entries, action records, stat counters, exact match records to
scale up offload flows.
Also increased ipv4 nat entries to 1023.
This patch is a critical fix to enable driver load on current and all
FW versions
The DPDK datapath in the transmit direction is very flexible.
The applications can build multisegment packets and manages
almost all data aspects - the memory pools where segments
are allocated from, the segment lengths, the memory attributes
like external, registered, etc.
In the receiving direct
https://bugs.dpdk.org/show_bug.cgi?id=520
Bug ID: 520
Summary: i40e: UDP PTPv2 packets sent to port 320 not
timestamped
Product: DPDK
Version: 20.05
Hardware: All
OS: All
Status: UNCONFIRMED
Hi Maxime,
> -Original Message-
> From: Maxime Coquelin
> Sent: Monday, August 3, 2020 5:51 PM
> To: Xueming(Steven) Li
> Cc: dev@dpdk.org; a...@dpdk.org; "Penso Subject: Re: [dpdk-dev] [v2] vdpa/mlx5: fix queue update synchronization
>
>
>
> On 8/2/20 11:21 AM, Xueming Li wrote:
> >
If the user tries to reset/stop some other timer in it's callback
function, which is also about to expire, using
rte_timer_reset_sync/rte_timer_stop_sync the application goes into
an infinite loop. This happens because
rte_timer_reset_sync/rte_timer_stop_sync loop until the timer
resets/stops an
Deprecation of rte_eth_dev_filter_ctrl() was announced in 2016,
and confirmed last year by avoiding include of rte_eth_ctrl.h.
After 4 years, it is time to complete the removal of the API
which is replaced with rte_flow.
Signed-off-by: Thomas Monjalon
---
doc/guides/rel_notes/deprecation.rst | 3
On 8/3/20 2:49 PM, Thomas Monjalon wrote:
> Deprecation of rte_eth_dev_filter_ctrl() was announced in 2016,
> and confirmed last year by avoiding include of rte_eth_ctrl.h.
> After 4 years, it is time to complete the removal of the API
> which is replaced with rte_flow.
>
> Signed-off-by: Thomas Mo
On Mon, Aug 3, 2020 at 5:24 PM Andrew Rybchenko
wrote:
>
> On 8/3/20 2:49 PM, Thomas Monjalon wrote:
> > Deprecation of rte_eth_dev_filter_ctrl() was announced in 2016,
> > and confirmed last year by avoiding include of rte_eth_ctrl.h.
> > After 4 years, it is time to complete the removal of the A
On Mon, Aug 3, 2020 at 4:28 PM Viacheslav Ovsiienko
wrote:
>
> The DPDK datapath in the transmit direction is very flexible.
> The applications can build multisegment packets and manages
> almost all data aspects - the memory pools where segments
> are allocated from, the segment lengths, the memo
On Mon, Aug 03, 2020 at 05:42:13PM +0800, yang_y_yi wrote:
> At 2020-08-03 16:11:39, "Olivier Matz" wrote:
> >On Mon, Aug 03, 2020 at 09:26:40AM +0800, yang_y_yi wrote:
> >> At 2020-08-03 04:29:07, "Olivier Matz" wrote:
> >> >Hi,
> >> >
> >> >On Sun, Aug 02, 2020 at 07:12:36AM +0800, yang_y_yi wr
On 8/2/20 10:28 PM, Olivier Matz wrote:
> On Fri, Jul 31, 2020 at 06:03:49PM +0200, Thomas Monjalon wrote:
>> In order to prepare for adding more features requiring more space in mbuf,
>> some static fields must become dynamic.
>> Some small layout changes may have performance benefits as well.
>>
In order to add support of the GENEVE header variable length
options the rte_flow_item_geneve_option item will be introduced:
struct rte_flow_item_geneve_option {
rte_be16_t option_class;
uint8_t option_type:7;
uint8_t critical:1;
uint8_t length:5;
uint8_t rsvd0:3;
uint8_t
Hi, Jerin,
Thanks for the comment, please, see below.
> -Original Message-
> From: Jerin Jacob
> Sent: Monday, August 3, 2020 14:57
> To: Slava Ovsiienko
> Cc: dpdk-dev ; Matan Azrad ;
> Raslan Darawsheh ; Thomas Monjalon
> ; Ferruh Yigit ; Stephen
> Hemminger ; Andrew Rybchenko
> ; Aj
On Fri, Jul 31, 2020 at 6:04 PM Thomas Monjalon wrote:
>
> In order to prepare for adding more features requiring more space in mbuf,
> some static fields must become dynamic.
> Some small layout changes may have performance benefits as well.
>
> The deprecation notice for atomic refcount is moved
Using the rte_flow action RSS types field,
may result in an undefined outcome.
For example selecting both UDP and TCP,
selecting TCP RSS type but the pattern is targeting UDP traffic.
another option is that the PMD doesn't support all requested types.
Until now, it wasn't clear what will happen i
On 8/3/20 1:58 PM, Viacheslav Ovsiienko wrote:
> The DPDK datapath in the transmit direction is very flexible.
> The applications can build multisegment packets and manages
> almost all data aspects - the memory pools where segments
> are allocated from, the segment lengths, the memory attributes
>
On Fri, Jul 31, 2020 at 5:12 AM Burakov, Anatoly
wrote:
> On 30-Jul-20 5:54 PM, Owen Hilyard wrote:
> > Thanks for the advice.
> >
> > I was wondering about the state of the "Setup VFIO permissions" option
> > in the setup script. It seems to just modify the character device's
> > permissions and
On 8/3/20 5:28 PM, Ori Kam wrote:
> Using the rte_flow action RSS types field,
> may result in an undefined outcome.
>
> For example selecting both UDP and TCP,
> selecting TCP RSS type but the pattern is targeting UDP traffic.
> another option is that the PMD doesn't support all requested types.
On 8/3/20 1:12 PM, Xueming(Steven) Li wrote:
> Hi Maxime,
>
>> -Original Message-
>> From: Maxime Coquelin
>> Sent: Monday, August 3, 2020 5:51 PM
>> To: Xueming(Steven) Li
>> Cc: dev@dpdk.org; a...@dpdk.org; "Penso > Subject: Re: [dpdk-dev] [v2] vdpa/mlx5: fix queue update synchroniz
On 8/3/20 10:25 AM, Matan Azrad wrote:
> When a virtq is destroyed, the SW should be able to continue the virtq
> processing from where the HW stopped.
>
> The current destroy behavior in the driver saves the virtq state (used
> and available indexes) only when LM is requested.
> So, when LM is
Vhost-user dequeue zero-copy support will be removed in
20.11. The only known user is OVS where the feature is
still experimental, and has not received any update for
several years. This feature faces reliability issues and
is often conflicting with new features being implemented.
Signed-off-by: M
Hi, Andrew
Thanks for the comment, please, see below.
> -Original Message-
> From: Andrew Rybchenko
> Sent: Monday, August 3, 2020 17:31
> To: Slava Ovsiienko ; dev@dpdk.org
> Cc: Matan Azrad ; Raslan Darawsheh
> ; Thomas Monjalon ;
> ferruh.yi...@intel.com; jerinjac...@gmail.com;
> step
Hi Andrew,
> -Original Message-
> From: Andrew Rybchenko
>
> On 8/3/20 5:28 PM, Ori Kam wrote:
> > Using the rte_flow action RSS types field,
> > may result in an undefined outcome.
> >
> > For example selecting both UDP and TCP,
> > selecting TCP RSS type but the pattern is targeting UD
Hi Slava,
On 8/3/20 6:18 PM, Slava Ovsiienko wrote:
> Hi, Andrew
>
> Thanks for the comment, please, see below.
>
>> -Original Message-
>> From: Andrew Rybchenko
>> Sent: Monday, August 3, 2020 17:31
>> To: Slava Ovsiienko ; dev@dpdk.org
>> Cc: Matan Azrad ; Raslan Darawsheh
>> ; Thomas
A new API is planned to be introduced for sampling and mirroring
with rte_flow. It should be more generic and allow more use cases.
This deprecation is to show the direction, avoiding overlapping APIs.
Signed-off-by: Thomas Monjalon
---
doc/guides/rel_notes/deprecation.rst | 6 ++
1 file ch
On 8/3/20 6:22 PM, Ori Kam wrote:
> Hi Andrew,
>
>> -Original Message-
>> From: Andrew Rybchenko
>>
>> On 8/3/20 5:28 PM, Ori Kam wrote:
>>> Using the rte_flow action RSS types field,
>>> may result in an undefined outcome.
>>>
>>> For example selecting both UDP and TCP,
>>> selecting TCP
On Mon, Aug 3, 2020 at 9:03 PM Thomas Monjalon wrote:
>
> A new API is planned to be introduced for sampling and mirroring
> with rte_flow. It should be more generic and allow more use cases.
>
> This deprecation is to show the direction, avoiding overlapping APIs.
>
> Signed-off-by: Thomas Monjal
On 8/3/20 6:33 PM, Thomas Monjalon wrote:
> A new API is planned to be introduced for sampling and mirroring
> with rte_flow. It should be more generic and allow more use cases.
>
> This deprecation is to show the direction, avoiding overlapping APIs.
>
> Signed-off-by: Thomas Monjalon
I like the
On Mon, Aug 3, 2020 at 5:23 PM Ori Kam wrote:
> > > +
> > > +- Hashing on types that are not supported by the PMD.
> >
> > Shouldn't it return error to the caller?
> >
> That’s depends, if for example the application requested eth and IPv4,
> and the PMD can do only IPv4 so according to this, the
> -Original Message-
> From: Andrew Rybchenko
>
> On 8/3/20 6:22 PM, Ori Kam wrote:
> > Hi Andrew,
> >
> >> -Original Message-
> >> From: Andrew Rybchenko
> >>
> >> On 8/3/20 5:28 PM, Ori Kam wrote:
> >>> Using the rte_flow action RSS types field,
> >>> may result in an undefin
Hi David,
> -Original Message-
> From: David Marchand
>
> On Mon, Aug 3, 2020 at 5:23 PM Ori Kam wrote:
> > > > +
> > > > +- Hashing on types that are not supported by the PMD.
> > >
> > > Shouldn't it return error to the caller?
> > >
> > That’s depends, if for example the application
On 8/2/20 11:21 AM, Xueming Li wrote:
> The driver CQ event management is done by non vhost library thread,
> either the dpdk host thread or the internal vDPA driver thread.
>
> When a queue is updated the CQ may be destroyed and created by the vhost
> library thread via the queue state operati
On 8/3/20 6:49 PM, Ori Kam wrote:
> Hi David,
>
>> -Original Message-
>> From: David Marchand
>>
>> On Mon, Aug 3, 2020 at 5:23 PM Ori Kam wrote:
> +
> +- Hashing on types that are not supported by the PMD.
Shouldn't it return error to the caller?
>>> That’s depends, if
On 8/3/20 10:25 AM, Matan Azrad wrote:
> When a virtq is destroyed, the SW should be able to continue the virtq
> processing from where the HW stopped.
>
> The current destroy behavior in the driver saves the virtq state (used
> and available indexes) only when LM is requested.
> So, when LM is
On 8/3/20 6:47 PM, Ori Kam wrote:
>
>
>> -Original Message-
>> From: Andrew Rybchenko
>>
>> On 8/3/20 6:22 PM, Ori Kam wrote:
>>> Hi Andrew,
>>>
-Original Message-
From: Andrew Rybchenko
On 8/3/20 5:28 PM, Ori Kam wrote:
> Using the rte_flow action RSS ty
03/08/2020 17:55, Andrew Rybchenko:
> On 8/3/20 6:49 PM, Ori Kam wrote:
> > From: David Marchand
> >> On Mon, Aug 3, 2020 at 5:23 PM Ori Kam wrote:
> > +
> > +- Hashing on types that are not supported by the PMD.
> Shouldn't it return error to the caller?
>
> >>> That’s depends,
Hi Maxime, Thomas,
> From: Maxime Coquelin
> Hi Nicolas,
>
> On 7/31/20 5:17 PM, Chautru, Nicolas wrote:
> > Hi Maxime,
> >
> >>
> >> Hi Nicolas,
> >>
> >> On 7/16/20 10:20 PM, Nicolas Chautru wrote:
> >>> Adding companion application to configure HW Device from the PF.
> >>> Then the device ca
> -Original Message-
> From: Sarosh Arif
> Sent: Monday, August 3, 2020 6:21 AM
> To: Carrillo, Erik G ; rsanf...@akamai.com
> Cc: dev@dpdk.org; Sarosh Arif
> Subject: [PATCH] doc: announce API change in timer
>
> If the user tries to reset/stop some other timer in it's callback function
> -Original Message-
> From: Andrew Rybchenko
> Sent: Monday, August 3, 2020 18:31
> To: Slava Ovsiienko ; dev@dpdk.org
> Cc: Matan Azrad ; Raslan Darawsheh
> ; Thomas Monjalon ;
> ferruh.yi...@intel.com; jerinjac...@gmail.com;
> step...@networkplumber.org; ajit.khapa...@broadcom.com;
> ma
Hi Andrew,
> -Original Message-
> From: Andrew Rybchenko
>
> On 8/3/20 6:47 PM, Ori Kam wrote:
> >
> >
> >> -Original Message-
> >> From: Andrew Rybchenko
> >>
> >> On 8/3/20 6:22 PM, Ori Kam wrote:
> >>> Hi Andrew,
> >>>
> -Original Message-
> From: Andrew Ryb
Using the current implementation of DPDK, an application cannot match on
IPv6 packets, based on the existing extension headers, in a simple way.
Field 'Next Header' in IPv6 header indicates type of the first extension
header only. Following extension headers can't be identified by
inspecting the I
Using the current implementation of DPDK, an application cannot match on
IPv6 packets, based on the existing extension headers, in a simple way.
Field 'Next Header' in IPv6 header indicates type of the first extension
header only. Following extension headers can't be identified by
inspecting the I
Hi all,
I wanted to send a follow up question regarding the development of the Idem
for Multicast Packets feature. Based on the plan we have so far, it
involves having one port be designated to send the packet, and two ports be
designated to receive the packet. In order to send out one packet for
The flow director config, part of the legacy filtering API,
was marked as deprecated last year.
A separate notice is added to make clear that these specific structs
will be removed as well in DPDK 20.11, as the rest of the legacy
filtering API.
Signed-off-by: Thomas Monjalon
---
doc/guides/rel_n
From: "McDaniel, Timothy"
The ABI changes associated with this notification will better support
devices that:
1. Have limits on the number or queues that may be linked to a port
2. Have ports that are limited to exactly one linked queue
3. Are not able to transparently transfer the event flow_id
The functions for L2 tunnel were missed when marking the legacy
filtering API as deprecated. That's why a separate notice is done
to make clear that it will be removed as well in DPDK 20.11.
Signed-off-by: Thomas Monjalon
---
doc/guides/rel_notes/deprecation.rst | 6 ++
1 file changed, 6 ins
OVS-DPDK seems to set the reset bit for every flow query. Honor
the bit by resetting the SW counter values after assigning them.
Also set the 'hit' bit only if the counter value retrieved by HW
is non-zero.
While querying flow stats, use max possible entries in the fc table scan
for valid entries i
On Sun, Aug 2, 2020 at 11:51 PM Somnath Kotur
wrote:
> From: Shahaji Bhosle
>
> Adjusted resource allocations for the hardware resources
> like TCAM entries, action records, stat counters, exact match records to
> scale up offload flows.
> Also increased ipv4 nat entries to 1023.
> This patch is
On Mon, Aug 3, 2020 at 4:57 AM Jerin Jacob wrote:
> On Mon, Aug 3, 2020 at 5:24 PM Andrew Rybchenko
> wrote:
> >
> > On 8/3/20 2:49 PM, Thomas Monjalon wrote:
> > > Deprecation of rte_eth_dev_filter_ctrl() was announced in 2016,
> > > and confirmed last year by avoiding include of rte_eth_ctrl.h
18/04/2019 12:59, Thomas Monjalon:
> Hi all,
>
> Since DPDK 18.11, the behaviour of the close operation is changed
> if RTE_ETH_DEV_CLOSE_REMOVE is enabled in the driver:
> port is released (i.e. totally freed and data erased) on close.
> This new behaviour is enabled per driver for a migration pe
Hello.
We've posted about this before, but I'm hoping to find someone willing to
commit a patched version of lib/librte_eal/bsdapp/eal/eal_interrupts.c that
corrects a memory leak and 100% CPU hog that is immediately noticeable with the
i40e driver, at a minimum. We have modified this file to
Struct rte_flow_item_ipv6 will be modified to include additional
values, indicating existence or absence of IPv6 extension headers
following the IPv6 header, as proposed in RFC
https://mails.dpdk.org/archives/dev/2020-August/177257.html.
Because of ABI break this change is proposed for 20.11.
Sign
On Mon, Aug 3, 2020 at 10:49 AM Thomas Monjalon wrote:
> The flow director config, part of the legacy filtering API,
> was marked as deprecated last year.
> A separate notice is added to make clear that these specific structs
> will be removed as well in DPDK 20.11, as the rest of the legacy
> fi
On Mon, Aug 3, 2020 at 8:36 AM Andrew Rybchenko
wrote:
> On 8/3/20 6:33 PM, Thomas Monjalon wrote:
> > A new API is planned to be introduced for sampling and mirroring
> > with rte_flow. It should be more generic and allow more use cases.
> >
> > This deprecation is to show the direction, avoidin
>
> If the user tries to reset/stop some other timer in it's callback function,
> which
Is there any use case for this? Why not just say document that the user is not
allowed to reset some other timer in the call back function? How does the user
get access to some other timer in the call back
Hello,
I can take a look if you can post the patch.
> -Original Message-
> From: dev On Behalf Of Lewis Donzis
> Sent: Monday, August 3, 2020 2:43 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] CPU hog & memory leak on FreeBSD
>
> Hello.
>
> We've posted about this before, but I'm
Sure, that would be great. This is from 18.11.9.
Also, the entire modified file is attached.
Thanks very much!
lew
84,86c84,86
< struct rte_intr_callback *callback = NULL;
< struct rte_intr_source *src = NULL;
< int ret, add_event;
---
> struct rte_intr_callback *callba
On Mon, Aug 03, 2020 at 01:38:42PM +0300, Fady Bader wrote:
> Telemetry didn't compile under Windows.
> Empty stubs implementation was added for Windows.
>
> Signed-off-by: Fady Bader
> ---
> lib/librte_telemetry/rte_telemetry.h| 4 +++
> lib/librte_telemetry/telemetry.c| 52
>
在 2020/7/17 15:29, Phil Yang 写道:
Subject: [dpdk-dev] [PATCH] app/testpmd: fix the default RSS key
configuration
When an user runs a flow create cmd to configure an RSS rule
without specifying the empty rss actions in testpmd, this mean
that the flow gets the default RSS functions. However,
At 2020-08-03 20:34:25, "Olivier Matz" wrote:
>On Mon, Aug 03, 2020 at 05:42:13PM +0800, yang_y_yi wrote:
>> At 2020-08-03 16:11:39, "Olivier Matz" wrote:
>> >On Mon, Aug 03, 2020 at 09:26:40AM +0800, yang_y_yi wrote:
>> >> At 2020-08-03 04:29:07, "Olivier Matz" wrote:
>> >> >Hi,
>> >> >
>> >> >
> -Original Message-
> From: Maxime Coquelin
> Sent: Monday, August 3, 2020 10:56 PM
> To: dev@dpdk.org; ktray...@redhat.com; Stokes, Ian ;
> Xia, Chenbo ; Wang, Zhihong
>
> Cc: Loftus, Ciara ; Maxime Coquelin
>
> Subject: [PATCH] doc: announce Vhost dequeue zero-copy removal
>
> Vhos
Different device has different hash capability, it should not be
expected that all hash set would be successful to set into all
devices by default. So remove the return checking when hash default
set. And remove gtpu hash default set, iavf only enable hash for
general protocols.
Fixes: c94366cfc64
Thank you Eric, I will fix the mistakes in v2
On Tue, Aug 4, 2020 at 4:16 AM Honnappa Nagarahalli
wrote:
>
>
>
> >
> > If the user tries to reset/stop some other timer in it's callback function,
> > which
> Is there any use case for this? Why not just say document that the user is
> not allowe
If the user tries to reset/stop some other timer in it's callback
function, which is also about to expire, using
rte_timer_reset_sync/rte_timer_stop_sync the application goes into
an infinite loop. This happens because
rte_timer_reset_sync/rte_timer_stop_sync loop until the timer
resets/stops and t
On Mon, Aug 3, 2020 at 11:28 PM Ajit Khaparde
wrote:
>
> On Mon, Aug 3, 2020 at 10:49 AM Thomas Monjalon wrote:
>
> > The flow director config, part of the legacy filtering API,
> > was marked as deprecated last year.
> > A separate notice is added to make clear that these specific structs
> > wi
> -Original Message-
> From: Guo, Jia
> Sent: Tuesday, August 4, 2020 10:59 AM
> To: Zhang, Qi Z ; Wu, Jingjing ;
> Xing, Beilei
> Cc: dev@dpdk.org; Guo, Junfeng ; Su, Simei
> ; Guo, Jia
> Subject: [PATCH v1] net/iavf: fix hash default set
>
> Different device has different hash capa
RSS for IPv6 prefix fields are supported in this patchset, so that we
can use prefixes instead of full IPv6 address for AVF RSS. The prefix
here includes the first 64 bits of both SRC and DST IPv6 address.
v2:
* add support RSS for GTPU IPv6 prefix 64bit.
[PATCH v2 1/3] common/iavf: support virtu
Some IPv6 prefix related protocol header fields are defined in this
patch, so that we can use prefix instead of full IPv6 address for RSS.
Ref https://tools.ietf.org/html/rfc6052.
Signed-off-by: Junfeng Guo
---
drivers/common/iavf/virtchnl.h | 13 +
1 file changed, 13 insertions(+)
RSS for IPv6 prefix 64bit fields are supported in this patch, so that
we can use prefix instead of full IPv6 address for RSS. The prefix
here only includes the first 64 bits of both SRC and DST IPv6 address.
Signed-off-by: Junfeng Guo
---
drivers/net/iavf/iavf_hash.c | 232 ++
RSS for GTP-U IPv6 prefix 64bit fields are supported in this patch.
The prefix here includes the first 64 bits of both SRC and DST inner
IPv6 address for GTP-U.
Signed-off-by: Junfeng Guo
---
drivers/net/iavf/iavf_hash.c | 1119 +-
1 file changed, 1112 insertions(
> -Original Message-
> From: Narcisa Ana Maria Vasile
> Sent: Tuesday, August 4, 2020 4:27 AM
> To: Fady Bader
> Cc: dev@dpdk.org; Thomas Monjalon ; Tasnim Bashar
> ; Tal Shnaiderman ; Yohad Tor
> ; dmitry.kozl...@gmail.com;
> harini.ramakrish...@microsoft.com; ocard...@microsoft.com;
The ethdev lib uses interrupts. Interrupts are not implemented for Windows.
To solve this, empty interrupt stubs were added under Windows.
Signed-off-by: Fady Bader
---
lib/librte_eal/windows/eal_interrupts.c | 17 +
lib/librte_eal/windows/meson.build | 1 +
2 files changed
Compiling needed libraries for ethdev under Windows.
Signed-off-by: Fady Bader
---
lib/meson.build | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/meson.build b/lib/meson.build
index 6bbaf242a9..c145240eb9 100644
--- a/lib/meson.build
+++ b/lib/meson.build
@@ -38,9 +38,
Added eal functions used by ethdev lib to the export list under Windows.
Signed-off-by: Fady Bader
---
lib/librte_eal/rte_eal_exports.def | 11 +++
1 file changed, 11 insertions(+)
diff --git a/lib/librte_eal/rte_eal_exports.def
b/lib/librte_eal/rte_eal_exports.def
index 69204a92c6..78
Some ethdev structs were present in ethdev export list.
There structs were removed from the export list.
Signed-off-by: Fady Bader
---
lib/librte_ethdev/rte_ethdev_version.map | 2 --
1 file changed, 2 deletions(-)
diff --git a/lib/librte_ethdev/rte_ethdev_version.map
b/lib/librte_ethdev/rte_e
Added needed changes in order to get ethdev compiling under windows.
Depends-on: series-10382 ("compile librte_net for windows")
v4: added comments to #else and fixed code issue.
v3: rebased on current master, added more exports to export list
v2: fixed logging issue in telemetry lib.
Fady Bad
Telemetry didn't compile under Windows.
Empty stubs implementation was added for Windows.
Signed-off-by: Fady Bader
---
lib/librte_telemetry/rte_telemetry.h| 4 +++
lib/librte_telemetry/telemetry.c| 51 -
lib/librte_telemetry/telemetry_legacy.c | 26 +
92 matches
Mail list logo
