Once again, a great release from the impressive DPDK community:
http://fast.dpdk.org/rel/dpdk-16.07.tar.xz
The statistics are awesome:
955 patches from 115 authors
839 files changed, 127162 insertions(+), 24668 deletions(-)
There are 50 new contributors
(including authors,
On Sat, Jul 09, 2016 at 05:56:34PM +0100, Pablo de Lara wrote:
> Driver names for all the supported devices in DPDK do not have
> a naming convention. Some are using a prefix, some are not
> and some have long names. Driver names are used when creating
> virtual devices, so it is useful to have con
On Thu, Jul 28, 2016 at 04:52:45PM +0200, Thomas Monjalon wrote:
> 2016-07-28 19:29, Jerin Jacob:
> > Above things worries me, I wouldn't have cared if the changes are not comes
> > in fastpath and I don't think this sort of issues will never get fixed any
> > time
> > soon in this community.
> >
Hi,
An updated libsso library with SNOW3G support is available to download in:
https://networkbuilders.intel.com/network-technologies/dpdk/dpdkuser-software-access
This update includes bug fixes of the following issues:
- sso_snow3g_f8_n_buffer was not ciphering more than 4 buffers at the same t
On Thu, Jul 28, 2016 at 12:33:18PM +, Mcnamara, John wrote:
> Initial Stable Release
> --
>
> The initial DPDK Stable Release will be 16.07. It will be viewed as a trial of
> the Stable Release/LTS policy to determine what are the best working practices
> for DPDK.
>
> The
2016-07-27 12:42, Thomas Monjalon:
> 2016-07-27 10:08, Dumitrescu, Cristian:
> > As Thomas mentioned, today is probably the last day to discuss ABI changes.
> > This one is pretty small and straightforward, any issues with it?
> >
> > Panu had a concern that the change from "char *" to "const cha
Claim v16.07 as a stable release: only bug fix patches are allowed.
And volunteer to be the maintainer.
Signed-off-by: Yuanhan Liu
---
MAINTAINERS | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d099131..1a5b047 100644
--- a/MAINTAINERS
++
> > > Vhost-cuse was invented before vhost-user exist. The both are actually
> > > doing the same thing: a vhost-net implementation in user space. But they
> > > are not exactly the same thing.
> > >
> > > Firstly, vhost-cuse is harder for use; no one seems to care it, either.
> > > Furthermore, si
> > There was a prior call with an explanation of what needs to be done:
> > http://dpdk.org/ml/archives/dev/2016-June/040844.html
> > - Qemu patch upstreamed
> > - IVSHMEM PCI device managed by a PCI driver
> > - No DPDK objects (ring/mempool) allocated by EAL
> >
> > As nobody seems inter
> > For 16.11, the mbuf structure will be modified implying ABI breakage.
> > Some discussions already took place here:
> > http://www.dpdk.org/dev/patchwork/patch/12878/
> >
> > Signed-off-by: Olivier Matz
>
> Acked-by: Thomas Monjalon
Acked-by: Konstantin Ananyev
Acked-by: John Daley
Acked-
> > Driver names for all the supported devices in DPDK do not have
> > a naming convention. Some are using a prefix, some are not
> > and some have long names. Driver names are used when creating
> > virtual devices, so it is useful to have consistency in the names.
> >
> > Signed-off-by: Pablo de
> > > The right name of ethdev should be dpdk_netdev. However:
> > > 1/ We are using rte_ prefix in the code and library names.
> > > 2/ The API uses rte_ethdev
> > > That's why 16.11 will just have the rte_ prefix prepended to
> > > the library filename as every other libraries.
> > >
> > > Signed
On Thu, Jul 28, 2016 at 01:01:16PM +, Ananyev, Konstantin wrote:
>
>
> > > >
> > > > Not according to proposal. It can't be too as application has no
> > > > idea what PMD driver does with "prep" what is the implication on a
> > > > HW if application does not
> > >
> > > Why application write
On 07/09/2016 06:56 PM, Pablo de Lara wrote:
> Driver names for all the supported devices in DPDK do not have
> a naming convention. Some are using a prefix, some are not
> and some have long names. Driver names are used when creating
> virtual devices, so it is useful to have consistency in the
2016-07-28 21:55, Jerin Jacob:
> On Thu, Jul 28, 2016 at 04:52:45PM +0200, Thomas Monjalon wrote:
> > 2016-07-28 19:29, Jerin Jacob:
> > > Above things worries me, I wouldn't have cared if the changes are not
> > > comes
> > > in fastpath and I don't think this sort of issues will never get fixed
2016-07-28 15:45, Rahul Lakkireddy:
> Remove deprecation notice pertaining to introduction of new flow
> types in favor of a more generic filtering infrastructure proposal.
>
> Signed-off-by: Rahul Lakkireddy
> Signed-off-by: Kumar Sanghvi
Applied, thanks
2016-07-28 16:26, Ferruh Yigit:
> On 7/27/2016 12:27 PM, Wei Dai wrote:
> > With --lcores 'a-b at c-d', eal_parse_cores() fails because
> > eal_parse_set() fails due to the next character after
> > lcore set a-b, which is '@'and not ',' or '\0'.
> > There is also a right check immediately
> > after
> Signed-off-by: Shreyansh Jain
> Acked-by: John McNamara
Applied, thanks
On Thu, Jul 28, 2016 at 5:47 PM, De Lara Guarch, Pablo
wrote:
>> This is a layer violation.
>> EAL does not know a thing about "ports".
>>
>> This information should come from the crypto framework and so an api
>> in crypto framework is the right place, not EAL.
>>
>> This is a NACK for me.
>
> Fa
> Signed-off-by: Tetsuya Mukawa
Applied, thanks
2016-07-27 14:26, John McNamara:
> Improve the wording of some text in the "new features" section of
> the release notes.
>
> Signed-off-by: Bruce Richardson
> Signed-off-by: John McNamara
Applied, thanks
Hello All,
Here in Politecnico di Torino we use the ivshmem technology from a
research point of view.
Our research efforts focus in optimizing the inter-Virtual Network
Function communication, currently we have implemented two versions of
our prototype, they are described in [1] and [2].
Unfo
> > Signed-off-by: Olga Shern
>
> Acked-by: John McNamara
Applied, thanks
> > When use i40e linux kernel driver as host driver and DPDK handler the i40e
> > VF, the promiscuous mode doesn't work in i40e VF. It is not supported by
> > DPDK i40e VF driver right now.
> >
> > Signed-off-by: Jeff Guo
>
> Acked-by: John McNamara
Applied, thanks
On Thu, Jul 28, 2016 at 10:36:07AM +, Ananyev, Konstantin wrote:
> > If it does not cope up then it can skip tx'ing in the actual tx burst
> > itself and move the "skipped" tx packets to end of the list in the tx
> > burst so that application can take the action on "skipped" packet after
> > th
> > Fix documentation for rte_eth_dev_tx/rx_queue_start/stop() functions
> >
> > Fixes: 2de9f8551ff9 ("ethdev: fix documentation for queue start/stop")
> >
> > Signed-off-by: Nikhil Rao
>
> Acked-by: John McNamara
Applied, thanks
2016-07-27 02:35, Sankar Chokkalingam:
> This configuration is example configuration for flow classification.
> This fix changes the offset and mask value to compute the hash correctly.
> This fix does not involve code change and do not impact compilation,
> build and performance.
>
> Fixes: 93771
2016-07-28 19:29, Jerin Jacob:
> Above things worries me, I wouldn't have cared if the changes are not comes
> in fastpath and I don't think this sort of issues will never get fixed any
> time
> soon in this community.
>
> So I given up.
I feel something goes wrong here but I cannot understand y
Hi all
As part of our ongoing efforts to improve DPDK, we'd like to hear your feedback!
We have created a number of DPDK-related questions here
https://www.surveymonkey.com/r/DPDK_Community_Survey and want to hear your
views!!
The survey will close at midnight GMT on Thursday August 4th
Thank
On 7/27/2016 12:27 PM, Wei Dai wrote:
> With --lcores 'a-b at c-d', eal_parse_cores() fails because
> eal_parse_set() fails due to the next character after
> lcore set a-b, which is '@'and not ',' or '\0'.
> There is also a right check immediately
> after this incorrect check.
>
> Fixes: 53e54bf81
On 7/27/2016 12:25 PM, Wei Dai wrote:
> the tail blank after a group of lcore or cpu set
> will make check of its end character fail.
> for example: --lcores '(0-3)@(0-3) ,(4-5)@(4-5)',
> the next character after cpu set (0-3) is not ','
> or '\0', which fail the check in eal_parse_lcores( ).
>
On 7/27/2016 12:23 PM, Wei Dai wrote:
> The '-' in lcore set overrides cpu set of following
> lcore set in the argument of EAL option --lcores.
> for example --locres '0-2,(3-5)@(3,4),6@(5,6),7@(5-7)',
> 0-2 make lflags=1 which indeed suppress following
> cpu set (3,4), (5,6) and (5-7) after @ .
>
On 7/27/2016 12:22 PM, Wei Dai wrote:
> local variable i is not referred by other codes in
> the function eal_parse_lcores( ), so it can be removed.
>
> Signed-off-by: Wei Dai
Acked-by: Ferruh Yigit
Hi,
Jumping into this thread, it looks it's the last pending patch remaining
for the release.
For reference, the idea of tx_prep() was mentionned some time ago in
http://dpdk.org/ml/archives/dev/2014-May/002504.html
Few comments below.
On 07/28/2016 03:01 PM, Ananyev, Konstantin wrote:
> Right
On Thu, Jul 28, 2016 at 10:32:44AM +0200, Olivier MATZ wrote:
Hi Olivier,
> Hi Hemant, Jerin,
>
> On 07/27/2016 11:51 AM, Jerin Jacob wrote:
> > On Tue, Jul 26, 2016 at 10:11:13AM +, Hemant Agrawal wrote:
>
> >
> > I agree, To me, this is very bad. I have raised this concern earlier
> > al
> > From: Dumitru Ceara
> >
> > The driver is incorrectly setting the RSS field in the last mbuf in the
> > packet chain instead of the first. Moreover, the last mbuf might have
> > already been freed if it only contained the Ethernet CRC.
> >
> > Also, fix the call to i40e_rxd_build_fdir to st
> -Original Message-
> From: David Marchand [mailto:david.marchand at 6wind.com]
> Sent: Thursday, July 28, 2016 5:18 AM
> To: De Lara Guarch, Pablo
> Cc: dev at dpdk.org; Mcnamara, John
> Subject: Re: [dpdk-dev] [PATCH] doc: announce API change for virtual device
> initialization
>
> He
Remove deprecation notice pertaining to introduction of new flow
types in favor of a more generic filtering infrastructure proposal.
Signed-off-by: Rahul Lakkireddy
Signed-off-by: Kumar Sanghvi
---
doc/guides/rel_notes/deprecation.rst | 4
1 file changed, 4 deletions(-)
diff --git a/doc/g
Hi Thomas,
On Thursday, July 07/28/16, 2016 at 01:29:20 -0700, Thomas Monjalon wrote:
> Hi Rahul,
>
> We still have this deprecation notice:
>
> * ABI changes are planned for adding four new flow types. This impacts
> RTE_ETH_FLOW_MAX. The release 2.2 does not contain these ABI changes,
> bu
On 07/28/2016 02:38 PM, Jerin Jacob wrote:
> On Thu, Jul 28, 2016 at 10:36:07AM +, Ananyev, Konstantin wrote:
>>> If it does not cope up then it can skip tx'ing in the actual tx burst
>>> itself and move the "skipped" tx packets to end of the list in the tx
>>> burst so that application can t
Hi Jan,
On Friday 15 July 2016 04:18 PM, Shreyansh jain wrote:
> On Thursday 14 July 2016 09:27 PM, Jan Viktorin wrote:
>> On Thu, 14 Jul 2016 10:57:55 +0530
>> Shreyansh jain wrote:
>>
>>> Hi Jan,
>>>
>>> On Wednesday 13 July 2016 11:04 PM, Jan Viktorin wrote:
On Wed, 13 Jul 2016 11:20:43 +
On 07/21/2016 06:24 PM, Tomasz Kulasek wrote:
> This is an ABI deprecation notice for DPDK 16.11 in librte_ether about
> changes in rte_eth_dev and rte_eth_desc_lim structures.
>
> As discussed in that thread:
>
> http://dpdk.org/ml/archives/dev/2015-September/023603.html
>
> Different NIC models d
Signed-off-by: Tetsuya Mukawa
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d099131..6536c6b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -373,7 +373,7 @@ F: drivers/net/vmxnet3/
F: doc/guides/nics/vmxnet3.rst
Vhost PMD
Hi Yuanhan,
Okay, thanks.
I will submit again.
Thanks,
Tetsuya
On 2016/07/28 14:43, Yuanhan Liu wrote:
> You are already the maintainer of the both :)
>
> I think a title like "update email address" would be more appropriate.
>
> -yliu
>
> On Thu, Jul 28, 2016 at 02:27:00PM +0900, Tetsu
I left my current company soon. Until my next email address is assigned,
here is my email address.
Regards,
Tetsuya
On 2016/07/28 14:27, Tetsuya Mukawa wrote:
> Signed-off-by: Tetsuya Mukawa
> ---
> MAINTAINERS | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTA
Signed-off-by: Tetsuya Mukawa
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d099131..6536c6b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -373,7 +373,7 @@ F: drivers/net/vmxnet3/
F: doc/guides/nics/vmxnet3.rst
Vhost PMD
Hi Olivier,
>
> Hi,
>
> Jumping into this thread, it looks it's the last pending patch remaining for
> the release.
>
> For reference, the idea of tx_prep() was mentionned some time ago in
> http://dpdk.org/ml/archives/dev/2014-May/002504.html
>
> Few comments below.
>
> On 07/28/2016 03:01
Add new section on tested platforms and nics and OSes to the release notes.
Signed-off-by: Yulong Pei
---
doc/guides/rel_notes/release_16_07.rst | 117 +
1 file changed, 117 insertions(+)
diff --git a/doc/guides/rel_notes/release_16_07.rst
b/doc/guides/rel_notes
Hello Pablo,
On Mon, Jul 4, 2016 at 4:50 PM, Pablo de Lara
wrote:
> In order to create a virtual device, user needs to call
> rte_eal_vdev_init generally, but this function returns 0
> on success or negative number if error. Instead, something
> more useful would be to return the port or device i
On Thu, Jul 28, 2016 at 10:20 AM, Thomas Monjalon
wrote:
> There were some efforts to fix Xen Dom0 support in 16.07:
> http://dpdk.org/ml/archives/dev/2016-July/043823.html
> But there is still at least one bug:
> http://dpdk.org/ml/archives/dev/2016-July/044207.html
> And nobody c
You are already the maintainer of the both :)
I think a title like "update email address" would be more appropriate.
-yliu
On Thu, Jul 28, 2016 at 02:27:00PM +0900, Tetsuya Mukawa wrote:
> Signed-off-by: Tetsuya Mukawa
> ---
> MAINTAINERS | 4 ++--
> 1 file changed, 2 insertions(+), 2
On Thu, Jul 28, 2016 at 03:44:57AM +0530, Alex Williamson wrote:
> Hi,
>
> I took a quick look at the dpdk vfio code and spotted an invalid
> assumption that should probably be corrected ASAP. That is:
>
> lib/librte_eal/linuxapp/eal/eal_vfio.h:
> #define VFIO_GET_REGION_ADDR(x) ((uint64_t) x <<
> -Original Message-
> From: Jerin Jacob [mailto:jerin.jacob at caviumnetworks.com]
> Sent: Thursday, July 28, 2016 12:39 PM
> To: Ananyev, Konstantin
> Cc: Thomas Monjalon ; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] doc: announce ABI change for rte_eth_dev
> structure
>
> O
This document sets out the guidelines for DPDK Stable Releases and Long Term
Support releases (LTS) based on the initial RFC and comments:
http://dpdk.org/ml/archives/dev/2016-June/040256.html.
In particular it incorporates suggestions for a Stable Release structure as
well as a Long Term Support
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, July 28, 2016 9:20 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: announce removal of Xen Dom0 support
>
> There were some efforts to fix Xen Dom0 support in 16.07:
2016-07-28 11:29, Christian Ehrhardt:
> Just curious, do we already know by looking ahead if ethdev will get an ABI
> bump anyway?
> So will the transition be:
> a) libethdev4 -> librte_ethdev5
> b)libethdev4 -> librte_ethdev4
> If it is b) would/should one provide a compat symlink then in your Opi
Hi Thomas,
just my two cents as Ubuntu DPDK maintainer (and part of the Debian Team
that does the same).
(Yeah I really could reuse it three times :-) )
It will be a bit of effort to adapt, but should be no rocket-science.
I like that eventually the namespace will be cleaner.
Just curious, do we
>
> The right name of ethdev should be dpdk_netdev. However:
> 1/ We are using rte_ prefix in the code and library names.
> 2/ The API uses rte_ethdev
> That's why 16.11 will just have the rte_ prefix prepended to the
> library filename as every other libraries.
>
> Signed-off-by: Thomas Monjalo
Hi Thomas,
just my two cents as Ubuntu DPDK maintainer (and part of the Debian Team
that does the same).
(It seems I can reuse that line for all posts about the deprecation notices
:-) )
While IVSHMEM was enabled (as it was the default) I never heard of any
users of what we provided so far.
But th
Hi Thomas,
just my two cents as Ubuntu DPDK maintainer (and part of the Debian Team
that does the same).
We never used vhost-cuse in any of our exampled, documentations or tests
(It seems we started "late enough").
So again I think it is a good change to drop rather unmaintained parts to
make the
Hi Thomas,
just my two cents as Ubuntu DPDK maintainer (and part of the Debian Team
that does the same).
We never enabled CONFIG_RTE_LIBRTE_XEN_DOM0, we only did LIBRTE_PMD_XENVIRT
based on a user request we had.
That said we won't "take away" anything from anybody and so far had no
request to pro
> > > >
> > > > > -Original Message-
> > > > > From: Jerin Jacob [mailto:jerin.jacob at caviumnetworks.com]
> > > > > Sent: Wednesday, July 27, 2016 6:11 PM
> > > > > To: Thomas Monjalon
> > > > > Cc: Kulasek, TomaszX ; dev at dpdk.org;
> > > > > Ananyev, Konstantin
> > > > > Subject: R
Hi Hemant, Jerin,
On 07/27/2016 11:51 AM, Jerin Jacob wrote:
> On Tue, Jul 26, 2016 at 10:11:13AM +, Hemant Agrawal wrote:
>> Hi,
>> There was lengthy discussions w.r.t external mempool
>> patches. However, I am still finding usages issue with the agreed approach.
>>
>> The ex
Hi Rahul,
We still have this deprecation notice:
* ABI changes are planned for adding four new flow types. This impacts
RTE_ETH_FLOW_MAX. The release 2.2 does not contain these ABI changes,
but release 2.3 will. [postponed]
Do you agree that we can remove it now we have a better generic filt
There were some efforts to fix Xen Dom0 support in 16.07:
http://dpdk.org/ml/archives/dev/2016-July/043823.html
But there is still at least one bug:
http://dpdk.org/ml/archives/dev/2016-July/044207.html
And nobody cares:
http://dpdk.org/ml/archives/dev/2016-July/044376.html
On Thu, Jul 28, 2016 at 2:29 AM, Yong Wang wrote:
>
>> On Jul 27, 2016, at 12:25 AM, sothy shan wrote:
>>
>> On Tue, Jul 26, 2016 at 6:32 PM, Mauricio Vasquez
>> wrote:
>>> Hello Sothy,
>>>
>>> Sorry for the delay in answering, some busy days here.
>>>
>>>
>>> On 07/25/2016 12:03 PM, sothy shan
> Hi,
>
> 2016-07-27 16:14, Alex Williamson:
> > I took a quick look at the dpdk vfio code and spotted an invalid
> > assumption that should probably be corrected ASAP.
>
> It can theoretically be a bug but the value may never change in the kernel,
> right?
> So when you say ASAP, I feel it can w
2016-07-27 16:52, Hemant Agrawal:
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > 2016-07-27 13:23, Hemant Agrawal:
> > > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > > > 2016-07-27 15:21, Jerin Jacob:
> > > > > If we agree on this then may be I can send the API
On Thu, 28 Jul 2016 09:42:13 +
"Burakov, Anatoly" wrote:
> > Hi,
> >
> > 2016-07-27 16:14, Alex Williamson:
> > > I took a quick look at the dpdk vfio code and spotted an invalid
> > > assumption that should probably be corrected ASAP.
> >
> > It can theoretically be a bug but the value
Hi,
2016-07-27 16:14, Alex Williamson:
> I took a quick look at the dpdk vfio code and spotted an invalid
> assumption that should probably be corrected ASAP.
It can theoretically be a bug but the value may never change in the kernel,
right?
So when you say ASAP, I feel it can wait the next DPDK
> > Add new section on tested platforms and nics and OSes to the release
> > notes.
> >
> > Signed-off-by: Yulong Pei
>
> Acked-by: John McNamara
Applied, thanks
> -Original Message-
> From: Pei, Yulong
> Sent: Thursday, July 28, 2016 7:19 AM
> To: dev at dpdk.org; thomas.monjalon at 6wind.com; Mcnamara, John
>
> Cc: Pei, Yulong
> Subject: [PATCH v5] doc: add section on tested platforms and nics and OSes
>
> Add new section on tested platforms
On Wed, Jul 20, 2016 at 09:16:14AM +0200, Olivier Matz wrote:
> For 16.11, the mbuf structure will be modified implying ABI breakage.
> Some discussions already took place here:
> http://www.dpdk.org/dev/patchwork/patch/12878/
>
> Signed-off-by: Olivier Matz
Acked-by: Jerin Jacob
On Wed, Jul 27, 2016 at 08:51:09PM +, Ananyev, Konstantin wrote:
>
> >
> > On Wed, Jul 27, 2016 at 05:33:01PM +, Ananyev, Konstantin wrote:
> > >
> > >
> > > > -Original Message-
> > > > From: Jerin Jacob [mailto:jerin.jacob at caviumnetworks.com]
> > > > Sent: Wednesday, July 27,
>
> For 16.11, the mbuf structure will be modified implying ABI breakage.
> Some discussions already took place here:
> http://www.dpdk.org/dev/patchwork/patch/12878/
>
> Signed-off-by: Olivier Matz
> ---
Acked-by: John Daley
Also, definitely +1 on trying to get m->next into the first cache l
75 matches
Mail list logo
