[vpp-dev] recipe for target 'vlib-find-source' failed

2017-07-20 Thread Divya Vyas 
Hi,

I am getting below error while cross-compiling VPP for thunder

make pkg-deb PLATFORM=thunder

 Package vlib not found with path /home/cavium/Downloads/vpp 
Makefile:779: recipe for target 'vlib-find-source' failed
make[2]: *** [vlib-find-source] Error 1
make[2]: Leaving directory '/home/cavium/Downloads/vpp/build-root'
/home/cavium/Downloads/vpp/build-data/platforms.mk:20: recipe for target
'install-deb' failed
make[1]: *** [install-deb] Error 1
make[1]: Leaving directory '/home/cavium/Downloads/vpp/build-root'
Makefile:419: recipe for target 'pkg-deb' failed
make: *** [pkg-deb] Error 2

Any hint I can get to debug this issue ?

Thanks,
Divya
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] stop handoff in SNAT

2017-07-20 Thread Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) 
right and handoff is faster than locking

Matus


From: Yuliang Li [mailto:yuliang...@yale.edu]
Sent: Friday, July 21, 2017 12:48 AM
To: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco) 

Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] stop handoff in SNAT

I think I get the reason. If the flow space split is dynamic, each thread has 
to propagate the state across all threads when new flows come, which requires 
locking. Using static flow space split can avoid this, at the cost of handoff 
for both directions.

On Thu, Jul 20, 2017 at 9:44 AM, Yuliang Li 
> wrote:
Thanks. That's a good point. But can I just use handoff on out2in? Because the 
in2out traffic is already split by RSS.

On Wed, Jul 19, 2017 at 10:15 PM, Matus Fabian -X (matfabia - PANTHEON 
TECHNOLOGIES at Cisco) > wrote:
Hi,

You need handoff when running multithread because traffic for specific inside 
network user must be processed always on same thread in both directions.

Regards,
Matus

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Yuliang Li
Sent: Thursday, July 20, 2017 5:58 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] stop handoff in SNAT

Hi,

Is there a way to stop handoff (move packet from one thread to another) in 
SNAT? I already use RSS to split packets across threads at the input, so I do 
not need it to spread traffic across threads again.

Thanks,
--
Yuliang Li
PhD student
Department of Computer Science
Yale University



--
Yuliang Li
PhD student
Department of Computer Science
Yale University



--
Yuliang Li
PhD student
Department of Computer Science
Yale University
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] build 17.07 Release not successful

2017-07-20 Thread ted.y.liang 
Dear all,

I downloaded recently vpp 17.07 rc2 and tried to build it, but there are a lot 
of errors. I tried both “make build” and “make build-release”; Please see below:


/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4642:6: error: unknown 
type name ‘vl_api_lldp_config_reply_t’
 (vl_api_##n##_t * mp)   \
  ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4637:1: note: in 
expansion of macro ‘_’
 _(lldp_config_reply)\
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4653:1: note: in 
expansion of macro ‘foreach_standard_reply_retval_handler’
 foreach_standard_reply_retval_handler;
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4642:6: error: unknown 
type name ‘vl_api_sw_interface_set_lldp_reply_t’
 (vl_api_##n##_t * mp)   \
  ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4638:1: note: in 
expansion of macro ‘_’
 _(sw_interface_set_lldp_reply)
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4653:1: note: in 
expansion of macro ‘foreach_standard_reply_retval_handler’
 foreach_standard_reply_retval_handler;
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4658:6: error: unknown 
type name ‘vl_api_lldp_config_reply_t’
 (vl_api_##n##_t * mp)   \
  ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4637:1: note: in 
expansion of macro ‘_’
 _(lldp_config_reply)\
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4668:1: note: in 
expansion of macro ‘foreach_standard_reply_retval_handler’
 foreach_standard_reply_retval_handler;
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4658:6: error: unknown 
type name ‘vl_api_sw_interface_set_lldp_reply_t’
 (vl_api_##n##_t * mp)   \
  ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4638:1: note: in 
expansion of macro ‘_’
 _(sw_interface_set_lldp_reply)
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:4668:1: note: in 
expansion of macro ‘foreach_standard_reply_retval_handler’
 foreach_standard_reply_retval_handler;
 ^
  CCLD libvlib.la
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c: In function 
‘api_lldp_config’:
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:19243:3: error: unknown 
type name ‘vl_api_lldp_config_t’
   vl_api_lldp_config_t *mp;
   ^
In file included from 
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:74:0:
/root/vpp-17.07/build-data/../src/vlibapi/vat_helper_macros.h:28:7: error: 
request for member ‘_vl_msg_id’ in something not a structure or union
 mp->_vl_msg_id = ntohs (VL_API_##T+__plugin_msg_base);  \
   ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:19266:3: note: in 
expansion of macro ‘M’
   M (LLDP_CONFIG, mp);
   ^
In file included from /usr/include/bits/byteswap.h:35:0,
 from /usr/include/endian.h:60,
 from /usr/include/bits/waitstatus.h:64,
 from /usr/include/stdlib.h:42,
 from 
/usr/lib/gcc/x86_64-redhat-linux/4.8.5/include/mm_malloc.h:27,
 from 
/usr/lib/gcc/x86_64-redhat-linux/4.8.5/include/xmmintrin.h:38,
 from 
/usr/lib/gcc/x86_64-redhat-linux/4.8.5/include/x86intrin.h:34,
 from 
/root/vpp-17.07/build-data/../src/vppinfra/vector_sse2.h:42,
 from /root/vpp-17.07/build-data/../src/vppinfra/vector.h:241,
 from 
/root/vpp-17.07/build-data/../src/vppinfra/mheap_bootstrap.h:47,
 from /root/vpp-17.07/build-data/../src/vppinfra/mem.h:44,
 from /root/vpp-17.07/build-data/../src/vppinfra/vec.h:42,
 from /root/vpp-17.07/build-data/../src/vppinfra/format.h:44,
 from /root/vpp-17.07/build-data/../src/vat/vat.h:21,
 from /root/vpp-17.07/build-data/../src/vpp/api/api_format.c:20:
/root/vpp-17.07/build-data/../src/vlibapi/vat_helper_macros.h:28:29: error: 
‘VL_API_LLDP_CONFIG’ undeclared (first use in this function)
 mp->_vl_msg_id = ntohs (VL_API_##T+__plugin_msg_base);  \
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:19266:3: note: in 
expansion of macro ‘M’
   M (LLDP_CONFIG, mp);
   ^
/root/vpp-17.07/build-data/../src/vlibapi/vat_helper_macros.h:28:29: note: each 
undeclared identifier is reported only once for each function it appears in
 mp->_vl_msg_id = ntohs (VL_API_##T+__plugin_msg_base);  \
 ^
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:19266:3: note: in 
expansion of macro ‘M’
   M (LLDP_CONFIG, mp);
   ^
In file included from 
/root/vpp-17.07/build-data/../src/vpp/api/api_format.c:74:0:
/root/vpp-17.07/build-data/../src/vlibapi/vat_helper_macros.h:29:7: error: 
request for member ‘client_index’ in something

Re: [vpp-dev] [csit-dev] 17.07 Release

2017-07-20 Thread George Zhao 
Bravo!!!

-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Dave Wallace
Sent: Thursday, July 20, 2017 7:25 PM
To: Neale Ranns (nranns); vpp-dev@lists.fd.io; csit-...@lists.fd.io
Subject: Re: [vpp-dev] [csit-dev] 17.07 Release

Most Excellent!

Thanks Neale and everyone who contributed to the VPP 17.07 release.
-daw-

On 07/20/2017 07:56 PM, Neale Ranns (nranns) wrote:
> Dear VPP community,
>
> The VPP 17.07 release is complete. The release artefacts are now available on 
> the nexus server.
>
> I’d like to take this opportunity to thank you all for your continued support 
> for VPP.
>
> Best regards,
> Neale
>
>
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] 17.07 Release

2017-07-20 Thread Dave Wallace 

Most Excellent!

Thanks Neale and everyone who contributed to the VPP 17.07 release.
-daw-

On 07/20/2017 07:56 PM, Neale Ranns (nranns) wrote:

Dear VPP community,

The VPP 17.07 release is complete. The release artefacts are now available on 
the nexus server.

I’d like to take this opportunity to thank you all for your continued support 
for VPP.

Best regards,
Neale


___
csit-dev mailing list
csit-...@lists.fd.io
https://lists.fd.io/mailman/listinfo/csit-dev


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 17.07 Release

2017-07-20 Thread Luke, Chris 
Woohoo!

> -Original Message-
> From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On
> Behalf Of Neale Ranns (nranns)
> Sent: Thursday, July 20, 2017 19:57
> To: vpp-dev@lists.fd.io; csit-...@lists.fd.io
> Subject: [csit-dev] 17.07 Release
> 
> 
> Dear VPP community,
> 
> The VPP 17.07 release is complete. The release artefacts are now available on
> the nexus server.
> 
> I’d like to take this opportunity to thank you all for your continued support
> for VPP.
> 
> Best regards,
> Neale
> 
> 
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] 17.07 Release

2017-07-20 Thread Florin Coras 
Awesome! 

Congrats to you and the whole community for all the hard work!

Cheers, 
Florin


> On Jul 20, 2017, at 4:56 PM, Neale Ranns (nranns)  wrote:
> 
> 
> Dear VPP community,
> 
> The VPP 17.07 release is complete. The release artefacts are now available on 
> the nexus server.
> 
> I’d like to take this opportunity to thank you all for your continued support 
> for VPP.
> 
> Best regards,
> Neale
> 
> 
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] 17.07 Release

2017-07-20 Thread Ed Warnicke 
Many thanks to Neale for his hard work here :)

Ed

On Thu, Jul 20, 2017 at 4:56 PM, Neale Ranns (nranns) 
wrote:

>
> Dear VPP community,
>
> The VPP 17.07 release is complete. The release artefacts are now available
> on the nexus server.
>
> I’d like to take this opportunity to thank you all for your continued
> support for VPP.
>
> Best regards,
> Neale
>
>
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] 17.07 Release

2017-07-20 Thread Neale Ranns (nranns) 

Dear VPP community,

The VPP 17.07 release is complete. The release artefacts are now available on 
the nexus server.

I’d like to take this opportunity to thank you all for your continued support 
for VPP.

Best regards,
Neale


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] stop handoff in SNAT

2017-07-20 Thread Yuliang Li 
I think I get the reason. If the flow space split is dynamic, each thread
has to propagate the state across all threads when new flows come, which
requires locking. Using static flow space split can avoid this, at the cost
of handoff for both directions.

On Thu, Jul 20, 2017 at 9:44 AM, Yuliang Li  wrote:

> Thanks. That's a good point. But can I just use handoff on out2in? Because
> the in2out traffic is already split by RSS.
>
> On Wed, Jul 19, 2017 at 10:15 PM, Matus Fabian -X (matfabia - PANTHEON
> TECHNOLOGIES at Cisco)  wrote:
>
>> Hi,
>>
>>
>>
>> You need handoff when running multithread because traffic for specific
>> inside network user must be processed always on same thread in both
>> directions.
>>
>>
>>
>> Regards,
>>
>> Matus
>>
>>
>>
>> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
>> Behalf Of *Yuliang Li
>> *Sent:* Thursday, July 20, 2017 5:58 AM
>> *To:* vpp-dev@lists.fd.io
>> *Subject:* [vpp-dev] stop handoff in SNAT
>>
>>
>>
>> Hi,
>>
>>
>>
>> Is there a way to stop handoff (move packet from one thread to another)
>> in SNAT? I already use RSS to split packets across threads at the input, so
>> I do not need it to spread traffic across threads again.
>>
>>
>>
>> Thanks,
>> --
>>
>> Yuliang Li
>>
>> PhD student
>>
>> Department of Computer Science
>>
>> Yale University
>>
>
>
>
> --
> Yuliang Li
> PhD student
> Department of Computer Science
> Yale University
>



-- 
Yuliang Li
PhD student
Department of Computer Science
Yale University
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] stop handoff in SNAT

2017-07-20 Thread Yuliang Li 
Thanks. That's a good point. But can I just use handoff on out2in? Because
the in2out traffic is already split by RSS.

On Wed, Jul 19, 2017 at 10:15 PM, Matus Fabian -X (matfabia - PANTHEON
TECHNOLOGIES at Cisco)  wrote:

> Hi,
>
>
>
> You need handoff when running multithread because traffic for specific
> inside network user must be processed always on same thread in both
> directions.
>
>
>
> Regards,
>
> Matus
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Yuliang Li
> *Sent:* Thursday, July 20, 2017 5:58 AM
> *To:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] stop handoff in SNAT
>
>
>
> Hi,
>
>
>
> Is there a way to stop handoff (move packet from one thread to another) in
> SNAT? I already use RSS to split packets across threads at the input, so I
> do not need it to spread traffic across threads again.
>
>
>
> Thanks,
> --
>
> Yuliang Li
>
> PhD student
>
> Department of Computer Science
>
> Yale University
>



-- 
Yuliang Li
PhD student
Department of Computer Science
Yale University
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev