From: Nicolas Chautru
Signed-off-by: Nic Chautru
---
doc/guides/prog_guide/bbdev.rst | 509 ++--
drivers/baseband/fpga_lte_fec/fpga_lte_fec.c | 24 +-
drivers/baseband/turbo_sw/bbdev_turbo_software.c | 36 +-
lib/librte_bbdev/rte_bbdev.c
From: Nicolas Chautru
Signed-off-by: Nic Chautru
---
app/test-bbdev/test_bbdev_vector.c | 4 +-
app/test-bbdev/test_bbdev_vector.h | 2 +-
config/common_base | 3 +-
doc/guides/bbdevs/turbo_sw.rst | 57 +-
driver
From: Nicolas Chautru
Signed-off-by: Nic Chautru
---
usertools/dpdk-devbind.py | 10 +-
usertools/dpdk-setup.sh | 6 +++---
2 files changed, 12 insertions(+), 4 deletions(-)
mode change 100755 => 100644 usertools/dpdk-devbind.py
mode change 100755 => 100644 usertools/dpdk-setup.sh
From: Nicolas Chautru
---
config/common_base |6 +
doc/guides/bbdevs/fpga_lte_fec.rst | 318 +++
doc/guides/bbdevs/index.rst|1 +
drivers/baseband/Makefile |2 +
drivers/baseband/fpga_lt
This was deferred from 19.05 due to time running out.
Addition of a PMD for 4G FEC encoding and decoding functions for Intel PAC N300
FPGA.
Extension of PMD based on Intel optimised SW libraries for 5G FEC.
The HW dependency is available now.
Nicolas Chautru (5):
baseband/fpga_lte_fec: addit
> On May 10, 2019, at 7:36 AM, Viacheslav Ovsiienko
> wrote:
>
> IBV_EVENT_DEVICE_FATAL event is generated by the driver once for
> the entire multiport Infiniband device, not for each existing ports.
> The port index is zero and it causes dropping the device removal
> event. We should invoke
10/05/2019 15:43, Bruce Richardson:
> On Fri, May 10, 2019 at 02:01:54PM +0100, Ray Kinsella wrote:
> > ( from the undersigned )
> >
> > Hi folks,
> >
> > In light of the renewed community discussion on API Stability
> > (https://mails.dpdk.org/archives/dev/2019-April/128969.html), now is
> > rig
re-send with fixed Cc
10/05/2019 20:17, Thomas Monjalon:
> 10/05/2019 19:14, Smoczynski, MarcinX:
> > To summarize we have different visibility sets for Linux and BSD when using
> > XOPEN_SOURCE or POSIX_C_SOURCE explicitly. To overcome this situation we can
> > either remove problematic XOPEN mac
10/05/2019 19:14, Smoczynski, MarcinX:
> To summarize we have different visibility sets for Linux and BSD when using
> XOPEN_SOURCE or POSIX_C_SOURCE explicitly. To overcome this situation we can
> either remove problematic XOPEN macros from mk/meson rules
> (drivers/net/failsafe,
> drivers/net/ml
+* Power 9 platforms with Mellanox(R) NICs combinations
+
+ * CPU:
+
+ * POWER9 2.2 (pvr 004e 1202) 2300MHz
+
+ * OS:
+
+ * Ubuntu 18.04.1 LTS (Bionic Beaver)
+
+ * NICs:
+
+ * Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G)
+
+ * Host interface: PCI Express 3.0 x16
TCP flags were moved to the TCP header file from the Ethernet control
header file, keeping their names intact.
Missing TCP ECN flags were added.
The ALL mask did not include TCP ECN flags, so it was renamed to reflect
that it applies to N-tuple filtering only.
A driver using the ALL mask was upda
TCP flags were moved to the TCP header file from the Ethernet control header
file, keeping their names intact.
Missing TCP ECN flags were added.
The ALL mask did not include TCP ECN flags, so it was renamed to reflect that
it applies to N-tuple filtering only.
A driver using the ALL mask was upda
Hi.
One of my patches submitted this week is breaking build on BSD systems. I dug
deeper and found out that it's because I'm using IPPROTO_* macros from
in a header (rte_ip.h) which is included in the driver which uses
_XOPEN_SOURCE definition in its Makefile/meson.build.
On Linux and glibc this
> The scheduling type parameter is not applicable for single link
> queues. DSW would, at the time of rte_event_queue_setup(), erroneously
> verify that scheduling type was one of the supported types, and
> returned -ENOTSUP in case of RTE_SCHED_TYPE_ORDERED.
>
> Fixes: 4540ee9c68 ("event/dsw:
Now that some of the symbols in the timer lib are versioned, the
Doxygen documentation that is generated is incorrect. Group all
versioned symbols, listing the generic name first, and remove comments
for older versions of symbols.
Signed-off-by: Erik Gabriel Carrillo
---
lib/librte_timer/rte_ti
> -Original Message-
> From: Ola Liljedahl [mailto:ola.liljed...@arm.com]
> Sent: Friday, May 10, 2019 10:19 AM
> To: step...@networkplumber.org; Eads, Gage
> Cc: arybche...@solarflare.com; nd ; Ananyev, Konstantin
> ; tho...@monjalon.net; Richardson,
> Bruce ; dev@dpdk.org;
> olivier.m...
TCP flags were moved to the TCP header file from the Ethernet control
header file, keeping their names intact.
Missing TCP ECN flags were added.
The ALL mask did not include TCP ECN flags, so it was renamed to
reflect that it applies to N-tuple filtering only.
A driver using the ALL mask was upd
On 2019-05-10 15:30, Thomas Monjalon wrote:
Any review please?
Reviewed-by: Mattias Rönnblom
Mattias Elo reported "Thanks, I’ve tested this patch and can confirm
that it fixes the problem." for the (nearly identical) v2 of this patch.
On 10-May-19 3:53 PM, Michael Santana wrote:
snprintf guarantees to always correctly place a null terminator in the buffer
string. So manually placing a null terminator in a buffer right after a call
to snprintf is redundant code.
Additionally, there is no need to use 'sizeof(buffer) - 1' in snp
On Fri, 2019-05-10 at 07:58 -0700, Stephen Hemminger wrote:
> On Fri, 10 May 2019 14:53:56 +
> "Eads, Gage" wrote:
>
> 01/02/2019 15:36, Gage Eads:
> In order to support the non-blocking ring[1], an API change
> (additional argument to rte_ring_get_memsize()) is required in
> librte_ring. T
On Fri, 10 May 2019 14:53:56 +
"Eads, Gage" wrote:
> > 01/02/2019 15:36, Gage Eads:
> > > In order to support the non-blocking ring[1], an API change
> > > (additional argument to rte_ring_get_memsize()) is required in
> > > librte_ring. This commit updates the deprecation notice to pave th
On Fri, May 10, 2019 at 10:53:12AM -0400, Michael Santana wrote:
> snprintf guarantees to always correctly place a null terminator in the buffer
> string. So manually placing a null terminator in a buffer right after a call
> to snprintf is redundant code.
>
> Additionally, there is no need to use
> 01/02/2019 15:36, Gage Eads:
> > In order to support the non-blocking ring[1], an API change
> > (additional argument to rte_ring_get_memsize()) is required in
> > librte_ring. This commit updates the deprecation notice to pave the
> > way for its inclusion in 19.08.
> >
> > [1] http://mails.dpdk
snprintf guarantees to always correctly place a null terminator in the buffer
string. So manually placing a null terminator in a buffer right after a call
to snprintf is redundant code.
Additionally, there is no need to use 'sizeof(buffer) - 1' in snprintf as this
means we are not using the last c
On Thu, 9 May 2019 11:08:30 +0100
"Burakov, Anatoly" wrote:
> On 09-May-19 10:50 AM, Ray Kinsella wrote:
> >
> >
> > On 09/05/2019 10:38, Thomas Monjalon wrote:
> >> 09/05/2019 11:37, Burakov, Anatoly:
> >>> On 09-May-19 10:06 AM, Bruce Richardson wrote:
> On Thu, May 09, 2019 at 09:
IBV_EVENT_DEVICE_FATAL event is generated by the driver once for
the entire multiport Infiniband device, not for each existing ports.
The port index is zero and it causes dropping the device removal
event. We should invoke the removal event processing routine
for each port we have installed handler
On 5/10/19 5:18 PM, John McNamara wrote:
Fix grammar, spelling and formatting of DPDK 19.05 release notes.
Signed-off-by: John McNamara
[snip]
* **Updated Solarflare network PMD.**
- Updated the sfc_efx driver including the following changes:
+ Updated the Solarflare ``sfc_efx`` dri
Signed-off-by: Morten Brørup
---
app/test-pmd/cmdline.c |4 ++--
drivers/net/e1000/igb_ethdev.c |8
lib/librte_ethdev/rte_eth_ctrl.h |8 +---
lib/librte_net/rte_tcp.h | 13 +
4 files changed, 20 insertions(+), 13 deletions(-)
diff --git
Fix grammar, spelling and formatting of DPDK 19.05 release notes.
Signed-off-by: John McNamara
---
doc/guides/rel_notes/release_19_05.rst | 147 -
1 file changed, 70 insertions(+), 77 deletions(-)
diff --git a/doc/guides/rel_notes/release_19_05.rst
b/doc/guides/
Hi Ferruh,
Thanks for the detailed feedback. There seems to be a problem with my mail
configuration on our development server. I will fix and send again.
Sorry about the inconvenience.
Med venlig hilsen / kind regards
- Morten Brørup
> -Original Message-
> From: dev [mailto:dev-boun..
10/05/2019 09:49, David Marchand:
> Rather than default to origin/master.., it can be handy to choose the
> range you want to check.
>
> Example on a branch rebased on next-net:
>
> Before:
> [dmarchan@dmarchan dpdk]$ ./devtools/checkpatches.sh
> ...
> ...
> 67/69 valid patches
>
> After:
> [dma
On Thu, May 9, 2019 at 8:53 PM Erik Gabriel Carrillo <
erik.g.carri...@intel.com> wrote:
> It is planned to make the rte_mem_config struct of the EAL private to
> remove it from the visible ABI. Add a notice to announce the intention.
>
> Signed-off-by: Erik Gabriel Carrillo
> ---
> changes in v
On Fri, May 10, 2019 at 02:01:54PM +0100, Ray Kinsella wrote:
> ( from the undersigned )
>
> Hi folks,
>
> In light of the renewed community discussion on API Stability
> (https://mails.dpdk.org/archives/dev/2019-April/128969.html), now is
> right time to open a discussion on how DPDK is distribu
Any review please?
10/05/2019 10:08, Nikhil Rao:
> The Rx adapter flushes events only if it has BATCH_SIZE
> events buffered where BATCH_SIZE is set to 32, e.g., if a
> single packet is sent, it is never passed to
> eventdev. Fix this issue by adding an event buffer flush
> either when a Rx queue
( from the undersigned )
Hi folks,
In light of the renewed community discussion on API Stability
(https://mails.dpdk.org/archives/dev/2019-April/128969.html), now is
right time to open a discussion on how DPDK is distributed and updated.
To this point in time, DPDK's primary distribution method
The scheduling type parameter is not applicable for single link
queues. DSW would, at the time of rte_event_queue_setup(), erroneously
verify that scheduling type was one of the supported types, and
returned -ENOTSUP in case of RTE_SCHED_TYPE_ORDERED.
Fixes: 4540ee9c68 ("event/dsw: add device and
> -Original Message-
> From: Zhao1, Wei [mailto:wei.zh...@intel.com]
> Sent: Friday, May 10, 2019 11:14 AM
> To: wangyunjian ; dev@dpdk.org
> Cc: i.maxim...@samsung.com; xudingke ;
> sta...@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] net/ixgbe: fix cancel link handler when port
> is being
On 09-May-19 7:16 PM, Kevin Traynor wrote:
On 09/05/2019 18:50, Ferruh Yigit wrote:
On 5/9/2019 6:50 PM, Ferruh Yigit wrote:
On 4/24/2019 4:26 PM, Anatoly Burakov wrote:
In no-shconf mode, there is no need to clean runtime directory
because it's not created in the first place.
Fixes: 0a529578
On 10/05/2019 10:53, Mattias Rönnblom wrote:
> On 2019-05-10 11:47, Mattias Rönnblom wrote:
>> The scheduling type parameter is not applicable for single link
>> queues. DSW would, at the time of rte_event_queue_setup(), erroneously
>> verify that scheduling type was one of the supported types, and
The scheduling type parameter is not applicable for single link
queues. DSW would, at the time of rte_event_queue_setup(), erroneously
verify that scheduling type was one of the supported types, and
returned -ENOTSUP in case of RTE_SCHED_TYPE_ORDERED.
Signed-off-by: Mattias Rönnblom
---
drivers/
On 2019-05-10 11:47, Mattias Rönnblom wrote:
The scheduling type parameter is not applicable for single link
queues. DSW would, at the time of rte_event_queue_setup(), erroneously
verify that scheduling type was one of the supported types, and
returned -ENOTSUP in case of RTE_SCHED_TYPE_ORDERED.
On 5/10/2019 8:01 AM, Morten Brørup wrote:
> Hi Olivier,
>
> I submitted the below patch about a month ago, and nothing happened. The
> patch is simple and obvious. Is something wrong with it, or did I not follow
> the submission process correctly?
Hi Morten,
I don't see this mail in mail list
On Fri, May 10, 2019 at 10:31:21AM +0100, Burakov, Anatoly wrote:
> On 09-May-19 7:51 PM, Erik Gabriel Carrillo wrote:
> > It is planned to make the rte_mem_config struct of the EAL private to
> > remove it from the visible ABI. Add a notice to announce the intention.
> >
> > Signed-off-by: Erik
On Fri, May 10, 2019 at 10:28:14AM +0100, Bruce Richardson wrote:
> On Fri, May 10, 2019 at 01:28:09AM +0200, Thomas Monjalon wrote:
> > > > From: Marcin Hajkowski
> > > >
> > > > Function rte_power_set_env will no longer return
> > > > success on attempt to set env in initialized state.
> > > >
>
On 09-May-19 7:51 PM, Erik Gabriel Carrillo wrote:
It is planned to make the rte_mem_config struct of the EAL private to
remove it from the visible ABI. Add a notice to announce the intention.
Signed-off-by: Erik Gabriel Carrillo
---
changes in v2:
- Original deprecation notice announced a c
On Fri, May 10, 2019 at 01:28:09AM +0200, Thomas Monjalon wrote:
> > > From: Marcin Hajkowski
> > >
> > > Function rte_power_set_env will no longer return
> > > success on attempt to set env in initialized state.
> > >
> > > Signed-off-by: Marcin Hajkowski
> >
> > Acked-by: David Hunt
>
> Any
On 13-Mar-19 7:21 PM, Hajkowski wrote:
From: Marcin Hajkowski
Function rte_power_set_env will no longer return
success on attempt to set env in initialized state.
Signed-off-by: Marcin Hajkowski
---
Acked-by: Anatoly Burakov
--
Thanks,
Anatoly
There is no need to do such a check when set macsec for ixgbe,
reconfig_device_queueand is also useless. If we do not delete this
unnessary code, users have to sotp port before enable or disable
macsec, then restart this port after make configuration. All these
process is useless. As this cmdline i
> -Original Message-
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Friday, May 10, 2019 12:48 AM
> To: Rao, Nikhil
> Cc: dev@dpdk.org; jer...@marvell.com; matias@nokia.com
> Subject: Re: [dpdk-dev] [PATCH v2] eventdev: fix Rx adapter event flush logic
>
> 09/05/2019
> -Original Message-
> From: Mattias Rönnblom [mailto:mattias.ronnb...@ericsson.com]
> Sent: Friday, May 10, 2019 12:52 AM
> To: Rao, Nikhil ; jer...@marvell.com
> Cc: dev@dpdk.org; matias@nokia.com
> Subject: Re: [dpdk-dev] [PATCH v2] eventdev: fix Rx adapter event flush logic
>
> O
The Rx adapter flushes events only if it has BATCH_SIZE
events buffered where BATCH_SIZE is set to 32, e.g., if a
single packet is sent, it is never passed to
eventdev. Fix this issue by adding an event buffer flush
either when a Rx queue is found to be empty or the adapter service
function has pro
Rather than default to origin/master.., it can be handy to choose the
range you want to check.
Example on a branch rebased on next-net:
Before:
[dmarchan@dmarchan dpdk]$ ./devtools/checkpatches.sh
...
...
67/69 valid patches
After:
[dmarchan@dmarchan dpdk]$ ./devtools/checkpatches.sh -r next-net
Hi Olivier,
I submitted the below patch about a month ago, and nothing happened. The patch
is simple and obvious. Is something wrong with it, or did I not follow the
submission process correctly?
Med venlig hilsen / kind regards
Morten Brørup
CTO
SmartShare Systems A/S
Tonsbakken 16-18
DK-2
53 matches
Mail list logo
