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, 2016 6:11 PM
> > To: Thomas Monjalon
> > Cc: Kulasek, TomaszX ; dev at dpdk.org;
> > Ananyev, Ko
On Wed, Jul 27, 2016 at 01:59:01AM -0700, Thomas Monjalon wrote:
> > > Signed-off-by: Tomasz Kulasek
> > > ---
> > > +* In 16.11 ABI changes are plained: the ``rte_eth_dev`` structure will be
> > > + extended with new function pointer ``tx_pkt_prep`` allowing
> > > verification
> > > + and proc
sorry, i make a mistake when set the rte_acl_field_def.
the input_index is not consecutive when define sport/dport like this:
{
.type = RTE_ACL_FIELD_TYPE_RANGE,
.size = sizeof(uint16_t),
.field_index = SRCP_FIELD_IPV4,
.input_index = RTE_ACL_IPV4_SPORT,
On Wed, 20 Jul 2016 18:35:46 +0200
Thomas Monjalon wrote:
> 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
On Fri, 15 Jul 2016 20:28:33 +0800
Yuanhan Liu wrote:
> 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 c
>
> 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, 2016 6:11 PM
> > > To: Thomas Monjalon
> > > Cc: Kulasek, TomaszX ; dev at dpdk.org
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: 53e54bf81700 ("eal: new option --lcores for cpu assignment")
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( ).
Fixes: 53e54bf81700 ("eal: new option --lcores for
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 @ .
Fixes: 53e54bf81700 ("eal: new option --lcores fo
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
---
lib/librte_eal/common/eal_common_options.c | 4
1 file changed, 4 deletions(-)
diff --git a/lib/librte_eal/common/eal_common_options.c
b/lib/librte_eal/com
define a rule as following:
struct acl_ipv4_rule acl_rule[] = {
{
.data = {.userdata = 103, .category_mask = 1, .priority = 1},
/* proto */
On Tue, 26 Jul 2016 18:22:21 +0200
Thomas Monjalon wrote:
> 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 e
On 07/20/2016 06:35 PM, Thomas Monjalon wrote:
> 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
> -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: Re: [dpdk-dev] [PATCH v2] doc: announce ABI change for rte_eth_d
> 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 wrote:
>>>
>>> Hello Mauricio,
>>>
>>> On Sun, Jul 24, 2
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Wednesday, July 27, 2016 7:05 PM
> To: Hemant Agrawal
> Cc: Jerin Jacob ; David Hunt
> ; dev at dpdk.org; olivier.matz at 6wind.com;
> viktorin at rehivetech.com; Shreyansh Jain
> Subject: Re: usag
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 << 40ULL)
#define VFIO_GET_REGION_IDX(x) (x >> 40)
Region offset to index is an
Signed-off-by: Ali Volkan ATLI
---
drivers/net/e1000/igb_rxtx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/e1000/igb_rxtx.c b/drivers/net/e1000/igb_rxtx.c
index 9d80a0b..c5db727 100644
--- a/drivers/net/e1000/igb_rxtx.c
+++ b/drivers/net/e1000/igb_rxtx.c
@@ -1
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 deprecation notices
> > > for rte_mempool_create for v16.11
> >
> > It would have been a lot better to send a
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 existing API to create packet mempool, "rte_pktmbuf_pool_create" does n
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
---
doc/guides/rel_notes/release_16_07.rst | 28
1 file changed, 16 insertions(+), 12 deletions(-)
diff --git a/doc/gui
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> 2016-07-27 15:21, Jerin Jacob:
> > On Tue, Jul 26, 2016 at 10:11:13AM +, Hemant Agrawal wrote:
> > > This is not a user friendly approach to ask for changing 1 API to 6 new
> > > APIs.
> Or, am I miss
Hello all,
While running as a secondary process I received the segmentation fault as
below on FreeBSD 10.3 and dpdk 16.04:
Program received signal SIGSEGV, Segmentation fault -
[Switching to Thread 801c06400 (LWP 100363/test_client)]
0x00416dcf in malloc_elem_alloc (elem=0x838e57000, siz
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Matthew Hall
> Sent: Tuesday, July 26, 2016 5:44 PM
> To: Luca Boccassi
> Cc: dev at dpdk.org; christian.ehrhardt at canonical.com;
> cjcollier at linuxfoundation.org; ricardo.salveti at linaro.org
> Subject:
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 char *" is too
> small to be regarded as ABI br
Signed-off-by: Olga Shern
---
doc/guides/nics/mlx5.rst |7 ++-
doc/guides/rel_notes/release_16_07.rst | 14 ++
2 files changed, 20 insertions(+), 1 deletions(-)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 063c4a5..5c10cd3 100644
---
2016-07-27 15:21, Jerin Jacob:
> On Tue, Jul 26, 2016 at 10:11:13AM +, Hemant Agrawal wrote:
> > This is not a user friendly approach to ask for changing 1 API to 6 new
> > APIs. Or, am I missing something?
>
> I agree, To me, this is very bad. I have raised this concern earlier
> also
>
> S
On Wed, Jul 27, 2016 at 12:27:26PM +0300, Olga Shern wrote:
> Signed-off-by: Olga Shern
> ---
> doc/guides/nics/mlx5.rst |7 ++-
> doc/guides/rel_notes/release_16_07.rst | 14 ++
> 2 files changed, 20 insertions(+), 1 deletions(-)
>
> diff --git a/doc/guides/n
Hi,
>
> define a rule as following:
>
> struct acl_ipv4_rule acl_rule[] = {
> {
> .data = {.userdata = 103, .category_mask = 1, .priority = 1},
> /* proto */
> .field[0] = {.value.u8 = 0, .mask_range.u8 = 0x0,},
> /* source IPv4 */
> .field[1] = {.value.u3
Hi everybody,
There are some announces pending to make some changes in 16.11 which
will break the API or ABI:
http://dpdk.org/dev/patchwork/project/dpdk/list/?q=announce
Some of them are really good but will probably not happen because there
is no visible consensus (or often no discussion
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
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Olga Shern
> Sent: Wednesday, July 27, 2016 10:27 AM
> To: dev at dpdk.org
> Cc: Olga Shern
> Subject: [dpdk-dev] [PATCH v2] doc: update guide and release notes for
> mlx5
>
> Signed-off-by: Olga Shern
Acked-
On Wed, Jul 20, 2016 at 6:35 PM, Thomas Monjalon
wrote:
> 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)
> 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
> > 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, since v2.1, a
2016-07-22 17:13, Adrien Mazarguil:
> > > >> From: De Lara Guarch, Pablo
> > > >>> 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
> > > >>> vi
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 char *" is too small
to be regarded as ABI breakage and we should simply go ahead and do it. My
Hi Bynes
Thanks for your feedback.
> -Original Message-
> From: bynes adam [mailto:adambynes at outlook.com]
> Sent: Friday, July 22, 2016 4:45 AM
> To: Dai, Wei
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] eal: fix parsing of argument of option
> --lcores
>
> On Thu, Jul 21,
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Olivier Matz
> Sent: Thursday, July 21, 2016 4:08 PM
> To: dev at dpdk.org; yuanhan.liu at linux.intel.com; Ananyev, Konstantin
>
> Cc: Chandran, Sugesh ; Richardson, Bruce
> ; Tan, Jianfeng ;
> Zhang,
> Heli
Thanks John
Sent fixed patch including your comments
Best Regards,
Olga
-Original Message-
From: Mcnamara, John [mailto:john.mcnam...@intel.com]
Sent: Wednesday, July 27, 2016 11:18 AM
To: Olga Shern ; dev at dpdk.org
Subject: RE: [dpdk-dev] [PATCH] doc : update guide and release note
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Olivier Matz
> Sent: Wednesday, July 20, 2016 8:16 AM
> To: dev at dpdk.org
> Cc: jerin.jacob at caviumnetworks.com; thomas.monjalon at 6wind.com;
> Richardson, Bruce
> Subject: [dpdk-dev] [PATCH v2] doc: ann
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 wrote:
>>
>> Hello Mauricio,
>>
>> On Sun, Jul 24, 2016 at 12:17 PM, Mauricio Vasquez
>> wrote:
>>>
>>> Hi Sothy,
>>>
>>>
>>>
Hi, Adam & Ananyev
Thanks for your feedback.
> -Original Message-
> From: Adam Bynes [mailto:adambynes at outlook.com]
> Sent: Wednesday, July 27, 2016 1:36 AM
> To: Dai, Wei ; Ananyev, Konstantin
>
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 1/2] eal: remove redundant codes
On Wed, Jul 27, 2016 at 1:31 AM, Thomas Monjalon
wrote:
> > > 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
On Wed, Jul 27, 2016 at 12:58:12PM +, Mcnamara, John wrote:
> Hi Matthew,
>
> Maybe you kick this off and submit something to the new howto section of the
> docs with whatever tuning tips you have so far.
>
> Then we can get people to contribute over time until we have something more
> usef
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Olga Shern
> Sent: Tuesday, July 26, 2016 5:29 PM
> To: dev at dpdk.org
> Cc: Olga Shern
> Subject: [dpdk-dev] [PATCH] doc : update guide and release notes for mlx5
>
> ...
>
> +* **Updated the mlx5 driver.**
> -Original Message-
> From: Pei, Yulong
> Sent: Wednesday, July 27, 2016 4:14 AM
> To: dev at dpdk.org; thomas.monjalon at 6wind.com
> Cc: Mcnamara, John ; Pei, Yulong
>
> Subject: [PATCH v4] doc: add section on tested platforms and nics and OSes
>
> Add new section on tested platforms
> -Original Message-
> From: Guo, Jia
> Sent: Wednesday, July 27, 2016 3:57 AM
> To: Mcnamara, John
> Cc: dev at dpdk.org; Guo, Jia
> Subject: [PATCH v3] doc: add known issue about promiscuous mode for I40e
> VF
>
> When use i40e linux kernel driver as host driver and DPDK handler the i4
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: 93771a569daa ("examples/ip_pipeline: rework flow classif
> > Signed-off-by: Tomasz Kulasek
> > ---
> > +* In 16.11 ABI changes are plained: the ``rte_eth_dev`` structure will be
> > + extended with new function pointer ``tx_pkt_prep`` allowing verification
> > + and processing of packet burst to meet HW specific requirements before
> > + transmit. Al
50 matches
Mail list logo
