Re: [vpp-dev] memmove fault

[薛欣颖]

Hi Chris,

Until today, the problem only appeared again:

Program received signal SIGSEGV, Segmentation fault.
__memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1663
1663../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S: No such file or 
directory.
(gdb) bt
#0  __memmove_ssse3_back () at 
../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1663
#1  0x7796531f in unix_cli_line_process_one (cm=0x77ba6d80 
, um=0x77ba77e0 , cf=0x7fffb5e5bf80, 
uf=0x7fffb5e5bf24, 
input=115 's', action=UNIX_CLI_PARSE_ACTION_NOMATCH) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2065
#2  0x77965911 in unix_cli_line_edit (cm=0x77ba6d80 
, um=0x77ba77e0 , cf=0x7fffb5e5bf80)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2154
#3  0x77965c49 in unix_cli_process_input (cm=0x77ba6d80 
, cli_file_index=0)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2194
#4  0x77966814 in unix_cli_process (vm=0x77ba7080 
, rt=0x7fffb5e5c000, f=0x0)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2320
#5  0x77928699 in vlib_process_bootstrap (_a=140736239855696) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1275
#6  0x7695fddc in clib_calljmp () at 
/home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/longjmp.S:128
#7  0x7fffb5956820 in ?? ()
#8  0x779287ce in vlib_process_startup (vm=0x7795c5b2 
, p=0x7fffb5956880, f=0x8496528d2a6d3500)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1300
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) f 1
#1  0x7796531f in unix_cli_line_process_one (cm=0x77ba6d80 
, um=0x77ba77e0 , cf=0x7fffb5e5bf80, 
uf=0x7fffb5e5bf24, 
input=115 's', action=UNIX_CLI_PARSE_ACTION_NOMATCH) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2065
2065  memmove (cf->current_command + cf->cursor + 1,
(gdb) p cf->current_command 
$36 = (u8 *) 0x7fffb5e5b740 "Ahow interface ipsec-gre "
(gdb) p  cf->cursor
$37 = 15
(gdb) p j
$38 = -15
(gdb) 

Until now I have not figured out the rule that it appears.

Thanks,
xyxue



 
From: Luke, Chris
Date: 2017-08-17 04:54
To: 薛欣颖; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] memmove fault
Can you be more specific about the steps that led up to this issue?
 
I won’t be able to work on it until September (about to go on vacation) but I 
do want to try to capture the details so I can try to recreate it.
 
Chris.
 
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of ???
Sent: Tuesday, August 15, 2017 5:14
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] memmove fault
 
 
Hi,

When I failed to configure a command, then click the up key , there is a 
Segmentation fault(not every time):

Program received signal SIGSEGV, Segmentation fault.
__memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1664
1664../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S: No such file or 
directory.
(gdb) bt
#0  __memmove_ssse3_back () at 
../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1664
#1  0x77966f56 in unix_cli_line_process_one (cm=0x77ba4960 
, 
um=0x77ba7dc0 , cf=0x7fffb5de5b3c, uf=0x7fffb5de5ae0, 
input=102 'f', 
action=UNIX_CLI_PARSE_ACTION_NOMATCH) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2063
#2  0x77967548 in unix_cli_line_edit (cm=0x77ba4960 
, um=0x77ba7dc0 , 
cf=0x7fffb5de5b3c) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2152
#3  0x77967880 in unix_cli_process_input (cm=0x77ba4960 
, cli_file_index=0)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2192
#4  0x7796844b in unix_cli_process (vm=0x77ba7560 
, rt=0x7fffb5e7, f=0x0)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/unix/cli.c:2318
#5  0x7792a320 in vlib_process_bootstrap (_a=140736239921232)
at /home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1274
#6  0x7696fd4c in clib_calljmp () at 
/home/vpp/17.07_x64/vpp/build-data/../src/vppinfra/longjmp.S:128
#7  0x7fffb5966820 in ?? ()
#8  0x7792a455 in vlib_process_startup (vm=0x7795e1e9 
, p=0x7fffb5966880, 
f=0xedcb4a35d968b00) at 
/home/vpp/17.07_x64/vpp/build-data/../src/vlib/main.c:1299
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

How should we solve this problem?

Thanks,
xyxue


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

Re: [vpp-dev] Failed to use vcl_test_client

[Florin Coras]

Hi xyxue, 

I just tested the stack with linux and everything seems to be working fine. I 
tested the stack with linux using uri_tcp_test and nc and the cut-through path 
with the vcl test tools. How are you running the server?

Florin

> On Sep 19, 2017, at 8:29 PM, 薛欣颖  wrote:
> 
> Hi Florin,
> 
> The server is started on the peer vpp . And through  
> 'sock_test_client/sock_test_server' can be normal communication.
> 
> Thanks,
> xyxue
>  
> From: Florin Coras 
> Date: 2017-09-20 10:52
> To: 薛欣颖 
> CC: dwallacelf ; vpp-dev 
> 
> Subject: Re: [vpp-dev] Failed to use vcl_test_client
> Hi xyxue,
> 
> What you’re getting is a connect fail because, I assume from trace, the 
> server is not started on the peer vpp. Because the server is not started, 
> i.e., bind wasn’t called, when the peer vpp receives the syn it replies with 
> a reset. That reset finally results in a connect fail notify. 
> 
> As for your other questions:
> 
> 1. Obviously, the one in vpp is for handling connect requests from 
> applications while the one in vppcom is for cut-through session. That is, vpp 
> acts as introduction mechanism for the two apps which afterwards exchange 
> data via shared memory fifos. 
> 2. For exchanging control messages, e.g., bind, connect, accept, they use the 
> binary api. For exchanging data, that is, moving data from vpp to vcl and 
> vice-versa, they use shared memory fifos. 
> 3. That message is a notification from vpp to the application (vcl in this 
> case) regarding a previous connect attempt. As you’ve discovered, if 
> is_fail=1, the connect attempt failed. 
> 
> Hope this helps, 
> Florin
> 
>> On Sep 19, 2017, at 7:30 PM, 薛欣颖 > > wrote:
>> 
>> 
>> Hi ,
>> 
>> There are still problems:
>> root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin#
>>  ./vcl_test_client -U 1.1.1.2 22000
>> 
>> CLIENT: Connecting to server...
>> vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session 
>> failed to connect (-115)
>> 
>> Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0, 
>> s=0x0, is_fail=1 '\001')
>> at 
>> /home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
>> 157 {
>> (gdb) bt
>> #0  send_session_connected_callback (app_index=1, api_context=0, s=0x0, 
>> is_fail=1 '\001')
>> at 
>> /home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
>> #1  0x7f35c658459c in stream_session_connect_notify (tc=0x7f358585e3f8, 
>> is_fail=, 
>> is_fail@entry=1 '\001') at 
>> /home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
>> #2  0x7f35c6456972 in tcp_connection_reset (tc=tc@entry=0x7f358585e3f8)
>> at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:258
>> #3  0x7f35c6429977 in tcp46_syn_sent_inline (is_ip4=1, 
>> from_frame=, node=, 
>> vm=) at 
>> /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2023
>> #4  tcp4_syn_sent (vm=, node=, 
>> from_frame=)
>> at 
>> /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2184
>> #5  0x7f35c6962d14 in dispatch_node (last_time_stamp=204974335045786, 
>> frame=0x7f35858596c0, 
>> dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL, 
>> node=0x7f3584da06c0, 
>> 
>> 
>> code segment：
>> int
>> send_session_connected_callback (u32 app_index, u32 api_context,
>>   stream_session_t * s, u8 is_fail)
>> {
>>   vl_api_connect_session_reply_t *mp;
>>   unix_shared_memory_queue_t *q;
>>   application_t *app;
>>   unix_shared_memory_queue_t *vpp_queue;
>> 
>>   app = application_get (app_index);
>>   q = vl_api_client_index_to_input_queue (app->api_client_index);
>> 
>>   if (!q)
>> return -1;
>> 
>>   mp = vl_msg_api_alloc (sizeof (*mp));
>>   mp->_vl_msg_id = clib_host_to_net_u16 (VL_API_CONNECT_SESSION_REPLY); 
>>   mp->context = api_context;
>>   if (!is_fail)
>> {
>>   vpp_queue = session_manager_get_vpp_event_queue (s->thread_index);
>>   mp->server_rx_fifo = pointer_to_uword (s->server_rx_fifo);
>>   mp->server_tx_fifo = pointer_to_uword (s->server_tx_fifo);
>>   mp->handle = stream_session_handle (s);
>>   mp->vpp_event_queue_address = pointer_to_uword (vpp_queue);
>>   mp->retval = 0;
>> }
>>   else
>> {
>>   mp->retval = clib_host_to_net_u32 
>> (VNET_API_ERROR_SESSION_CONNECT_FAIL);  
>> }
>>   vl_msg_api_send_shmem (q, (u8 *) & mp);
>>   return 0;
>> }
>> 
>> ruturn message to VCL， connect failed: Session failed to connect 
>> 
>> I have two question :
>> 1.  there are two function "vl_api_connect_sock_t_handler", one in 
>> session_api.c,  another in vppcom.c, 
>> How to work ?
>> 
>> 2.  How to VCL and VPP communication ? 
>> 
>> 3. Why the message of VPP to VCL  is 

Re: [vpp-dev] some issue about using unformat %u

[Florin Coras]

Hi Hui, 

Yup, that’s a ‘known’ unformat trap. When unformatting integers, use u32. 

Florin

> On Sep 19, 2017, at 8:33 PM,   
> wrote:
> 
> hi all:
> 
> we found some common using issues about the use of CLI unformat, as follow:
> 
> 
> 
> u16 out_port = 0;
> 
> u32 vrf_id = 0, protocol;
> 
> else if (unformat (line_input, "%U %u", unformat_ip4_address,
> 
>_addr, _port))
> 
> 
> 
> when inputing u16 or u8 type param(not u32)， the  local variable which behind 
> of "out_port" in stack will be overwrited, is that right? is there some Notes 
> about this?
> 
> I think the bellow code maybe  cause that issue.
> 
> unformat->va_unformat->do_percent->unformat_integer-> *(u32 *) v = value;
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 王辉 wanghui
> 
> 
> 
> IT开发工程师 IT Development Engineer
> 虚拟化南京四部/无线研究院/无线产品经营部 NIV Nanjing Dept. IV/Wireless Product R＆D 
> Institute/Wireless Product Operation Division
> 
> 
> 
> 
> ___
> 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

[vpp-dev] some issue about using unformat %u

[wang.hui56]

hi all:

we found some common using issues about the use of CLI unformat, as follow:




u16 out_port = 0

u32 vrf_id = 0, protocol

else if (unformat (line_input, "%U %u", unformat_ip4_address,

 _addr, _port))




when inputing u16 or u8 type param(not u32)， the  local variable which behind 
of "out_port" in stack will be overwrited, is that right? is there some Notes 
about this?

I think the bellow code maybe  cause that issue.


unformat->va_unformat->do_percent->unformat_integer-> *(u32 *) v = value



















王辉 wanghui






IT开发工程师 IT Development
Engineer
虚拟化南京四部/无线研究院/无线产品经营部 NIV Nanjing Dept. IV/Wireless Product R＆D 
Institute/Wireless Product Operation Division___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Failed to use vcl_test_client

[薛欣颖]

Hi Florin,

The server is started on the peer vpp . And through  
'sock_test_client/sock_test_server' can be normal communication.

Thanks,
xyxue


 
From: Florin Coras
Date: 2017-09-20 10:52
To: 薛欣颖
CC: dwallacelf; vpp-dev
Subject: Re: [vpp-dev] Failed to use vcl_test_client
Hi xyxue,

What you’re getting is a connect fail because, I assume from trace, the server 
is not started on the peer vpp. Because the server is not started, i.e., bind 
wasn’t called, when the peer vpp receives the syn it replies with a reset. That 
reset finally results in a connect fail notify. 

As for your other questions:

1. Obviously, the one in vpp is for handling connect requests from applications 
while the one in vppcom is for cut-through session. That is, vpp acts as 
introduction mechanism for the two apps which afterwards exchange data via 
shared memory fifos. 
2. For exchanging control messages, e.g., bind, connect, accept, they use the 
binary api. For exchanging data, that is, moving data from vpp to vcl and 
vice-versa, they use shared memory fifos. 
3. That message is a notification from vpp to the application (vcl in this 
case) regarding a previous connect attempt. As you’ve discovered, if is_fail=1, 
the connect attempt failed. 

Hope this helps, 
Florin

On Sep 19, 2017, at 7:30 PM, 薛欣颖  wrote:


Hi ,

There are still problems:
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# 
./vcl_test_client -U 1.1.1.2 22000

CLIENT: Connecting to server...
vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session 
failed to connect (-115)

Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0, 
s=0x0, is_fail=1 '\001')
at 
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
157 {
(gdb) bt
#0  send_session_connected_callback (app_index=1, api_context=0, s=0x0, 
is_fail=1 '\001')
at 
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
#1  0x7f35c658459c in stream_session_connect_notify (tc=0x7f358585e3f8, 
is_fail=, 
is_fail@entry=1 '\001') at 
/home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
#2  0x7f35c6456972 in tcp_connection_reset (tc=tc@entry=0x7f358585e3f8)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:258
#3  0x7f35c6429977 in tcp46_syn_sent_inline (is_ip4=1, 
from_frame=, node=, 
vm=) at 
/home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2023
#4  tcp4_syn_sent (vm=, node=, 
from_frame=)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2184
#5  0x7f35c6962d14 in dispatch_node (last_time_stamp=204974335045786, 
frame=0x7f35858596c0, 
dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL, 
node=0x7f3584da06c0, 


code segment：
int
send_session_connected_callback (u32 app_index, u32 api_context,
 stream_session_t * s, u8 is_fail)
{
  vl_api_connect_session_reply_t *mp;
  unix_shared_memory_queue_t *q;
  application_t *app;
  unix_shared_memory_queue_t *vpp_queue;

  app = application_get (app_index);
  q = vl_api_client_index_to_input_queue (app->api_client_index);

  if (!q)
return -1;

  mp = vl_msg_api_alloc (sizeof (*mp));
  mp->_vl_msg_id = clib_host_to_net_u16 (VL_API_CONNECT_SESSION_REPLY); 
  mp->context = api_context;
  if (!is_fail)
{
  vpp_queue = session_manager_get_vpp_event_queue (s->thread_index);
  mp->server_rx_fifo = pointer_to_uword (s->server_rx_fifo);
  mp->server_tx_fifo = pointer_to_uword (s->server_tx_fifo);
  mp->handle = stream_session_handle (s);
  mp->vpp_event_queue_address = pointer_to_uword (vpp_queue);
  mp->retval = 0;
}
  else
{
  mp->retval = clib_host_to_net_u32 (VNET_API_ERROR_SESSION_CONNECT_FAIL);  
}
  vl_msg_api_send_shmem (q, (u8 *) & mp);
  return 0;
}

ruturn message to VCL， connect failed: Session failed to connect 

I have two question :
1.  there are two function "vl_api_connect_sock_t_handler", one in 
session_api.c,  another in vppcom.c, 
How to work ?

2.  How to VCL and VPP communication ? 

3. Why the message of VPP to VCL  is "send_session_connected_callback" function 
send ?

thanks,
xyxue
 
From: Dave Wallace
Date: 2017-09-19 01:29
To: 薛欣颖; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Failed to use vcl_test_client
Hi Xyeue,

I believe this patch fixes this issue:  https://gerrit.fd.io/r/#/c/8315/

Can you please pull the latest source code and try again?

Thanks,
-daw-

On 9/18/2017 2:43 AM, 薛欣颖 wrote:

Hi,

When I test vcl ,there is some error :
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# 
./vcl_test_client -U 1.1.1.2 22000

CLIENT: Connecting to server...
msg_handler_internal:429: no handler for msg id 424
..
...
...
ERROR in main(): Bad file descriptor
ERROR: connect failed (errno = 9)!
Segmentation fault

The msg id 424 is VL_API_CONNECT_URI_REPLY .The 

Re: [vpp-dev] Failed to use vcl_test_client

[Florin Coras]

Hi xyxue,

What you’re getting is a connect fail because, I assume from trace, the server 
is not started on the peer vpp. Because the server is not started, i.e., bind 
wasn’t called, when the peer vpp receives the syn it replies with a reset. That 
reset finally results in a connect fail notify. 

As for your other questions:

1. Obviously, the one in vpp is for handling connect requests from applications 
while the one in vppcom is for cut-through session. That is, vpp acts as 
introduction mechanism for the two apps which afterwards exchange data via 
shared memory fifos. 
2. For exchanging control messages, e.g., bind, connect, accept, they use the 
binary api. For exchanging data, that is, moving data from vpp to vcl and 
vice-versa, they use shared memory fifos. 
3. That message is a notification from vpp to the application (vcl in this 
case) regarding a previous connect attempt. As you’ve discovered, if is_fail=1, 
the connect attempt failed. 

Hope this helps, 
Florin

> On Sep 19, 2017, at 7:30 PM, 薛欣颖  wrote:
> 
> 
> Hi ,
> 
> There are still problems:
> root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin#
>  ./vcl_test_client -U 1.1.1.2 22000
> 
> CLIENT: Connecting to server...
> vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session 
> failed to connect (-115)
> 
> Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0, 
> s=0x0, is_fail=1 '\001')
> at 
> /home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
> 157 {
> (gdb) bt
> #0  send_session_connected_callback (app_index=1, api_context=0, s=0x0, 
> is_fail=1 '\001')
> at 
> /home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
> #1  0x7f35c658459c in stream_session_connect_notify (tc=0x7f358585e3f8, 
> is_fail=, 
> is_fail@entry=1 '\001') at 
> /home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
> #2  0x7f35c6456972 in tcp_connection_reset (tc=tc@entry=0x7f358585e3f8)
> at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:258
> #3  0x7f35c6429977 in tcp46_syn_sent_inline (is_ip4=1, 
> from_frame=, node=, 
> vm=) at 
> /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2023
> #4  tcp4_syn_sent (vm=, node=, 
> from_frame=)
> at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2184
> #5  0x7f35c6962d14 in dispatch_node (last_time_stamp=204974335045786, 
> frame=0x7f35858596c0, 
> dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL, 
> node=0x7f3584da06c0, 
> 
> 
> code segment：
> int
> send_session_connected_callback (u32 app_index, u32 api_context,
>stream_session_t * s, u8 is_fail)
> {
>   vl_api_connect_session_reply_t *mp;
>   unix_shared_memory_queue_t *q;
>   application_t *app;
>   unix_shared_memory_queue_t *vpp_queue;
> 
>   app = application_get (app_index);
>   q = vl_api_client_index_to_input_queue (app->api_client_index);
> 
>   if (!q)
> return -1;
> 
>   mp = vl_msg_api_alloc (sizeof (*mp));
>   mp->_vl_msg_id = clib_host_to_net_u16 (VL_API_CONNECT_SESSION_REPLY); 
>   mp->context = api_context;
>   if (!is_fail)
> {
>   vpp_queue = session_manager_get_vpp_event_queue (s->thread_index);
>   mp->server_rx_fifo = pointer_to_uword (s->server_rx_fifo);
>   mp->server_tx_fifo = pointer_to_uword (s->server_tx_fifo);
>   mp->handle = stream_session_handle (s);
>   mp->vpp_event_queue_address = pointer_to_uword (vpp_queue);
>   mp->retval = 0;
> }
>   else
> {
>   mp->retval = clib_host_to_net_u32 
> (VNET_API_ERROR_SESSION_CONNECT_FAIL);  
> }
>   vl_msg_api_send_shmem (q, (u8 *) & mp);
>   return 0;
> }
> 
> ruturn message to VCL， connect failed: Session failed to connect 
> 
> I have two question :
> 1.  there are two function "vl_api_connect_sock_t_handler", one in 
> session_api.c,  another in vppcom.c, 
> How to work ?
> 
> 2.  How to VCL and VPP communication ? 
> 
> 3. Why the message of VPP to VCL  is "send_session_connected_callback" 
> function send ?
> 
> thanks,
> xyxue
>  
> From: Dave Wallace 
> Date: 2017-09-19 01:29
> To: 薛欣颖 ; vpp-dev@lists.fd.io 
> 
> Subject: Re: [vpp-dev] Failed to use vcl_test_client
> Hi Xyeue,
> 
> I believe this patch fixes this issue:  https://gerrit.fd.io/r/#/c/8315/ 
> 
> 
> Can you please pull the latest source code and try again?
> 
> Thanks,
> -daw-
> 
> On 9/18/2017 2:43 AM, 薛欣颖 wrote:
>> 
>> Hi,
>> 
>> When I test vcl ,there is some error :
>> root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin#
>>  ./vcl_test_client -U 1.1.1.2 22000
>> 
>> CLIENT: Connecting to server...
>> msg_handler_internal:429: no handler for msg id 424
>> ..
>> ...
>> ...
>> ERROR in main(): 

Re: [vpp-dev] Failed to use vcl_test_client

[薛欣颖]

Hi ,

There are still problems:
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# 
./vcl_test_client -U 1.1.1.2 22000

CLIENT: Connecting to server...
vl_api_connect_session_reply_t_handler:697: [9478] connect failed: Session 
failed to connect (-115)

Breakpoint 1, send_session_connected_callback (app_index=1, api_context=0, 
s=0x0, is_fail=1 '\001')
at 
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
157 {
(gdb) bt
#0  send_session_connected_callback (app_index=1, api_context=0, s=0x0, 
is_fail=1 '\001')
at 
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:157
#1  0x7f35c658459c in stream_session_connect_notify (tc=0x7f358585e3f8, 
is_fail=, 
is_fail@entry=1 '\001') at 
/home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
#2  0x7f35c6456972 in tcp_connection_reset (tc=tc@entry=0x7f358585e3f8)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:258
#3  0x7f35c6429977 in tcp46_syn_sent_inline (is_ip4=1, 
from_frame=, node=, 
vm=) at 
/home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2023
#4  tcp4_syn_sent (vm=, node=, 
from_frame=)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2184
#5  0x7f35c6962d14 in dispatch_node (last_time_stamp=204974335045786, 
frame=0x7f35858596c0, 
dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL, 
node=0x7f3584da06c0, 


code segment：
int
send_session_connected_callback (u32 app_index, u32 api_context,
 stream_session_t * s, u8 is_fail)
{
  vl_api_connect_session_reply_t *mp;
  unix_shared_memory_queue_t *q;
  application_t *app;
  unix_shared_memory_queue_t *vpp_queue;

  app = application_get (app_index);
  q = vl_api_client_index_to_input_queue (app->api_client_index);

  if (!q)
return -1;

  mp = vl_msg_api_alloc (sizeof (*mp));
  mp->_vl_msg_id = clib_host_to_net_u16 (VL_API_CONNECT_SESSION_REPLY); 
  mp->context = api_context;
  if (!is_fail)
{
  vpp_queue = session_manager_get_vpp_event_queue (s->thread_index);
  mp->server_rx_fifo = pointer_to_uword (s->server_rx_fifo);
  mp->server_tx_fifo = pointer_to_uword (s->server_tx_fifo);
  mp->handle = stream_session_handle (s);
  mp->vpp_event_queue_address = pointer_to_uword (vpp_queue);
  mp->retval = 0;
}
  else
{
  mp->retval = clib_host_to_net_u32 (VNET_API_ERROR_SESSION_CONNECT_FAIL);  
}
  vl_msg_api_send_shmem (q, (u8 *) & mp);
  return 0;
}

ruturn message to VCL， connect failed: Session failed to connect 

I have two question :
1.  there are two function "vl_api_connect_sock_t_handler", one in 
session_api.c,  another in vppcom.c, 
How to work ?

2.  How to VCL and VPP communication ? 

3. Why the message of VPP to VCL  is "send_session_connected_callback" function 
send ?

thanks,
xyxue


 
From: Dave Wallace
Date: 2017-09-19 01:29
To: 薛欣颖; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Failed to use vcl_test_client
Hi Xyeue,

I believe this patch fixes this issue:  https://gerrit.fd.io/r/#/c/8315/

Can you please pull the latest source code and try again?

Thanks,
-daw-

On 9/18/2017 2:43 AM, 薛欣颖 wrote:

Hi,

When I test vcl ,there is some error :
root@ubuntu:/home/vpp_communication/vpp/build-root/install-vpp-native/vpp/bin# 
./vcl_test_client -U 1.1.1.2 22000

CLIENT: Connecting to server...
msg_handler_internal:429: no handler for msg id 424
..
...
...
ERROR in main(): Bad file descriptor
ERROR: connect failed (errno = 9)!
Segmentation fault

The msg id 424 is VL_API_CONNECT_URI_REPLY .The VL_API_CONNECT_URI_REPLY is 
registed in vat.
Is there anything wrong in my test?

The gdb information is shown below:
(gdb) bt
#0  vl_msg_api_send_shmem (q=q@entry=0x302891c0, elem=elem@entry=0x7faafab32cc8 
"\344o\006\060")
at 
/home/vpp_communication/vpp/build-data/../src/vlibmemory/memory_shared.c:584
#1  0x7fab3c053b55 in send_session_connected_callback (app_index=, api_context=3472551422, 
s=0x0, is_fail=) at 
/home/vpp_communication/vpp/build-data/../src/vnet/session/session_api.c:186
#2  0x7fab3c03cc44 in stream_session_connect_notify (tc=0x7faafa776bd8, 
is_fail=, 
is_fail@entry=1 '\001') at 
/home/vpp_communication/vpp/build-data/../src/vnet/session/session.c:489
#3  0x7fab3bf0f642 in tcp_connection_reset (tc=tc@entry=0x7faafa776bd8)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp.c:257
#4  0x7fab3bee4077 in tcp46_syn_sent_inline (is_ip4=1, 
from_frame=, node=, 
vm=) at 
/home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:1938
#5  tcp4_syn_sent (vm=, node=, 
from_frame=)
at /home/vpp_communication/vpp/build-data/../src/vnet/tcp/tcp_input.c:2091
#6  0x7fab3c4159e4 in dispatch_node (last_time_stamp=1926897640132334, 
frame=0x7faafb34a000, 
dispatch_state=VLIB_NODE_STATE_POLLING, type=VLIB_NODE_TYPE_INTERNAL, 
node=0x7faafa86a600, 

Re: [vpp-dev] CentOS 7.4

[Burt Silverman]

Problem solved after 1)rebooting, 2) cd ~/vpp; rm -rf *; git checkout . 3)
make install-dep; make bootstrap; make build-release.

Possibly it was just the reboot and make install-dep, I am not sure, but I
saw nasm getting updated at that point.

Thanks, Tom, for hints.

Burt

On Mon, Sep 18, 2017 at 10:59 PM, Burt Silverman  wrote:

> I updated my CentOS using "yum update" and that leaves me with CentOS 7.4.
> So I get those fPIC errors that others have reported on non CentOS systems
> but that have glibc 2.17. Are others seeing the same thing? It looks to me
> that the official builds under CentOS are being done WITHOUT "yum update".
> Thanks.
>
> Burt
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP 1704 and router plugin

[Neale Ranns (nranns)]

Hi Bhanu,

Sorry, then I’m out of ideas. And I don’t have access to similar HW to try and 
reproduce and debug. A var args issue is still my best guess.

/neale

From: Bhanu Chander Gaddoju 
Date: Tuesday, 19 September 2017 at 10:24
To: "Neale Ranns (nranns)" , "Dave Barach (dbarach)" 
, "vpp-dev@lists.fd.io" , "Ni, Hongjun" 

Subject: RE: [vpp-dev] VPP 1704 and router plugin

Hi Neale,

  I am getting the same issue even after the change.

Regards,
Bhanu,
HSDC, NXP India.


From: Bhanu Chander Gaddoju
Sent: Tuesday, September 19, 2017 9:52 AM
To: Neale Ranns (nranns) ; Dave Barach (dbarach) 
; vpp-dev@lists.fd.io; Ni, Hongjun 
Subject: RE: [vpp-dev] VPP 1704 and router plugin

Hi Neale,

   Please find the information below,

 ARCH  =   aarch64
 OS   =   Ubuntu 16.04
GCC =   Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4

 I am using VPP stable/1704 and external DPDK version 17.02.

 I will test as you suggested and would let you know.


Regards,
Bhanu,
HSDC, NXP India.


From: Neale Ranns (nranns) [mailto:nra...@cisco.com]
Sent: Tuesday, September 19, 2017 2:15 AM
To: Bhanu Chander Gaddoju 
>; Dave Barach (dbarach) 
>; 
vpp-dev@lists.fd.io; Ni, Hongjun 
>
Subject: Re: [vpp-dev] VPP 1704 and router plugin

Hi Bhanu,

Can you give us some information on the CPU arch, OS and compiler version you 
are using please.

My best guess at the issue here is the problem of integer promotion through a 
variadic function. Perhaps you could test this idea by declaring;
 int fproto = FIB_PROTOCOL_IP4;
And then pass the variable ‘fproto’ and not FIB_PROTOCOL_IP4 to the call to 
vlib_cli_output (in frame 4).

Regards,
neale


From: > on 
behalf of Bhanu Chander Gaddoju 
>
Date: Monday, 18 September 2017 at 00:58
To: "Dave Barach (dbarach)" >, 
"vpp-dev@lists.fd.io" 
>, "Ni, Hongjun" 
>
Subject: Re: [vpp-dev] VPP 1704 and router plugin

Hi All,

   Could you please help me to resolve this issue.

Regards,
Bhanu.


From: Bhanu Chander Gaddoju
Sent: Tuesday, September 12, 2017 10:18 PM
To: 'Dave Barach (dbarach)' >; 
vpp-dev@lists.fd.io; Ni, Hongjun 
>
Subject: RE: VPP 1704 and router plugin

Hi Dave,

Thank you for your response.
fib_table->ft_desc is not NULL. Please find the details below,

(gdb) c
Continuing.

Breakpoint 1, format_fib_table_name (s=0x0, ap=...) at 
/root/vpp-1704/build-data/../src/vnet/fib/fib_table.c:1095
1095/root/vpp-1704/build-data/../src/vnet/fib/fib_table.c: No such file or 
directory.
(gdb) n
1096in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1097in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1096in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1097in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1100in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1102in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb) p fib_table
$2 = (fib_table_t *) 0x3e1c9b80
(gdb) p fib_table->ft_desc
$3 = (u8 *) 0x3eb07a80 "ipv4-VRF:0"
(gdb) p *fib_table
$4 = {{v4 = {fib_entry_by_dst_address = {0x3d92f738, 0x0, 0x0, 0x0, 
0x3d92ead8, 0x0 , 0x3d92b9a0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 0x3d92f170}, mtrie = {
ply_pool = 0x3eb5b000, default_leaf = 1}, table_id = 0, index = 0, 
flow_hash_config = 31, fwd_classify_table_index = 4294967295, 
rev_classify_table_index = 4294967295}, v6 = {
  table_id = 1033041720, index = 65535, flow_hash_config = 0}, mpls = 
{mf_entries = 0x3d92f738, mf_lbs = {0, 0, 0, 0, 0, 0, 1033038552, 65535, 0 
, 1033025952, 65535,
0 , 1033040240, 65535, 1052094464, 65535, 1, 0, 0, 0, 
31, 4294967295, 4294967295, 0 }}}, ft_proto = 
FIB_PROTOCOL_IP4, ft_locks = 3,
  ft_table_id = 0, ft_index = 0, ft_flow_hash_config = 31, ft_src_route_counts 
= {2, 0, 5, 0, 3, 0 , 3}, ft_total_route_counts = 11, ft_desc 
= 0x3eb07a80 "ipv4-VRF:0"}



Regards,
Bhanu,
HSDC, NXP India.


From: Dave Barach (dbarach) 

[vpp-dev] Latest git vpp dpdk problem / undefined symbol: aes_gcm_enc_128_sse

[Paweł Staszewski]

Sep 19 20:34:25 ubuntu vpp[11348]: vlib_plugin_early_init:356: plugin 
path /usr/lib/vpp_plugins
Sep 19 20:34:25 ubuntu vpp[11348]: load_one_plugin:184: Loaded plugin: 
acl_plugin.so (Access Control Lists)
Sep 19 20:34:25 ubuntu vpp[11348]: load_one_plugin:142: 
/usr/lib/vpp_plugins/dpdk_plugin.so: undefined symbol: aes_gcm_enc_128_sse
Sep 19 20:34:25 ubuntu vpp[11348]: load_one_plugin:143: Failed to load 
plugin 'dpdk_plugin.so'
Sep 19 20:34:25 ubuntu systemd[1]: vpp.service: Main process exited, 
code=dumped, status=6/ABRT

Sep 19 20:34:25 ubuntu systemd[1]: vpp.service: Unit entered failed state.
Sep 19 20:34:25 ubuntu systemd[1]: vpp.service: Failed with result 
'core-dump'.
Sep 19 20:34:25 ubuntu systemd[1]: vpp.service: Service hold-off time 
over, scheduling restart.

Sep 19 20:34:25 ubuntu systemd[1]: Stopped vector packet processing engine.
Sep 19 20:34:25 ubuntu systemd[1]: vpp.service: Start request repeated 
too quickly.
Sep 19 20:34:25 ubuntu systemd[1]: Failed to start vector packet 
processing engine.

Sep 19 20:34:25 ubuntu systemd[1]: vpp.service: Unit entered failed state.
Sep 19 20:34:25 ubuntu systemd[1]: vpp.service: Failed with result 
'start-limit-hit'.





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

Re: [vpp-dev] Multiple vppctl Considered Harmful

[Dave Barach (dbarach)]

Give me a minute, I'll try it right away...

Thanks... Dave

-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Jon Loeliger
Sent: Tuesday, September 19, 2017 2:01 PM
To: vpp-dev 
Subject: [vpp-dev] Multiple vppctl Considered Harmful

Folks,

While I appear to be able to run a single vppctl up against VPP,
if I then start a second one, to the same VPP process, VPP immediately
aborts.  It's pretty unfriendly.

EAL:   Invalid NUMA socket, default to 0
EAL:   Invalid NUMA socket, default to 0
DPDK physical memory layout:
Segment 0: phys:0x3520, len:2097152, virt:0x7ff40d00,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 1: phys:0x35c0, len:8388608, virt:0x7ff40c60,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 2: phys:0x36c0, len:2097152, virt:0x7ff40c20,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 3: phys:0x6d80, len:224395264, virt:0x7ff3fea0,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 4: phys:0x3f940, len:2097152, virt:0x7ff3fe60,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 5: phys:0x3f980, len:29360128, virt:0x7ff38c80,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Aborted



vpp# show version
vpp v17.10-rc0~307-g6b3a8ef built by jdl on bcc-1.netgate.com at Mon
Sep 11 18:38:26 CDT 2017



Does anyone else see that?  Or am I special?

Thanks,
jdl
___
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

[vpp-dev] Multiple vppctl Considered Harmful

[Jon Loeliger]

Folks,

While I appear to be able to run a single vppctl up against VPP,
if I then start a second one, to the same VPP process, VPP immediately
aborts.  It's pretty unfriendly.

EAL:   Invalid NUMA socket, default to 0
EAL:   Invalid NUMA socket, default to 0
DPDK physical memory layout:
Segment 0: phys:0x3520, len:2097152, virt:0x7ff40d00,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 1: phys:0x35c0, len:8388608, virt:0x7ff40c60,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 2: phys:0x36c0, len:2097152, virt:0x7ff40c20,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 3: phys:0x6d80, len:224395264, virt:0x7ff3fea0,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 4: phys:0x3f940, len:2097152, virt:0x7ff3fe60,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Segment 5: phys:0x3f980, len:29360128, virt:0x7ff38c80,
socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
Aborted



vpp# show version
vpp v17.10-rc0~307-g6b3a8ef built by jdl on bcc-1.netgate.com at Mon
Sep 11 18:38:26 CDT 2017



Does anyone else see that?  Or am I special?

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

Re: [vpp-dev] Coverity runs

[Florin Coras]

+1

Thanks, Chris!

Florin

> On Sep 19, 2017, at 9:03 AM, Dave Barach (dbarach)  wrote:
> 
> Very cool! Thanks for working on it...  <>Dave
>  
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Luke, Chris
> Sent: Tuesday, September 19, 2017 11:50 AM
> To: vpp-dev 
> Subject: [vpp-dev] Coverity runs
>  
> All,
>  
> Coverity have increased the limits for our project size again; effective 
> yesterday I run the build twice daily. 0600 and 1500 Eastern is what I have 
> in cron currently, which I hope will be useful times for the majority of the 
> current contributors to get feedback on their patches once merged. Thoughts 
> on the timing welcome.
>  
> Chris.
> ___
> 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] Coverity runs

[Dave Barach (dbarach)]

Very cool! Thanks for working on it... Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Luke, Chris
Sent: Tuesday, September 19, 2017 11:50 AM
To: vpp-dev 
Subject: [vpp-dev] Coverity runs

All,

Coverity have increased the limits for our project size again; effective 
yesterday I run the build twice daily. 0600 and 1500 Eastern is what I have in 
cron currently, which I hope will be useful times for the majority of the 
current contributors to get feedback on their patches once merged. Thoughts on 
the timing welcome.

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

[vpp-dev] Coverity runs

[Luke, Chris]

All,

Coverity have increased the limits for our project size again; effective 
yesterday I run the build twice daily. 0600 and 1500 Eastern is what I have in 
cron currently, which I hope will be useful times for the majority of the 
current contributors to get feedback on their patches once merged. Thoughts on 
the timing welcome.

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

Re: [vpp-dev] VPP 1704 and router plugin

[Bhanu Chander Gaddoju]

Hi Neale,

  I am getting the same issue even after the change.

Regards,
Bhanu,
HSDC, NXP India.


From: Bhanu Chander Gaddoju
Sent: Tuesday, September 19, 2017 9:52 AM
To: Neale Ranns (nranns) ; Dave Barach (dbarach) 
; vpp-dev@lists.fd.io; Ni, Hongjun 
Subject: RE: [vpp-dev] VPP 1704 and router plugin

Hi Neale,

   Please find the information below,

 ARCH  =   aarch64
 OS   =   Ubuntu 16.04
GCC =   Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4

 I am using VPP stable/1704 and external DPDK version 17.02.

 I will test as you suggested and would let you know.


Regards,
Bhanu,
HSDC, NXP India.


From: Neale Ranns (nranns) [mailto:nra...@cisco.com]
Sent: Tuesday, September 19, 2017 2:15 AM
To: Bhanu Chander Gaddoju 
>; Dave Barach (dbarach) 
>; 
vpp-dev@lists.fd.io; Ni, Hongjun 
>
Subject: Re: [vpp-dev] VPP 1704 and router plugin

Hi Bhanu,

Can you give us some information on the CPU arch, OS and compiler version you 
are using please.

My best guess at the issue here is the problem of integer promotion through a 
variadic function. Perhaps you could test this idea by declaring;
 int fproto = FIB_PROTOCOL_IP4;
And then pass the variable ‘fproto’ and not FIB_PROTOCOL_IP4 to the call to 
vlib_cli_output (in frame 4).

Regards,
neale


From: > on 
behalf of Bhanu Chander Gaddoju 
>
Date: Monday, 18 September 2017 at 00:58
To: "Dave Barach (dbarach)" >, 
"vpp-dev@lists.fd.io" 
>, "Ni, Hongjun" 
>
Subject: Re: [vpp-dev] VPP 1704 and router plugin

Hi All,

   Could you please help me to resolve this issue.

Regards,
Bhanu.


From: Bhanu Chander Gaddoju
Sent: Tuesday, September 12, 2017 10:18 PM
To: 'Dave Barach (dbarach)' >; 
vpp-dev@lists.fd.io; Ni, Hongjun 
>
Subject: RE: VPP 1704 and router plugin

Hi Dave,

Thank you for your response.
fib_table->ft_desc is not NULL. Please find the details below,

(gdb) c
Continuing.

Breakpoint 1, format_fib_table_name (s=0x0, ap=...) at 
/root/vpp-1704/build-data/../src/vnet/fib/fib_table.c:1095
1095/root/vpp-1704/build-data/../src/vnet/fib/fib_table.c: No such file or 
directory.
(gdb) n
1096in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1097in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1096in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1097in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1100in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb)
1102in /root/vpp-1704/build-data/../src/vnet/fib/fib_table.c
(gdb) p fib_table
$2 = (fib_table_t *) 0x3e1c9b80
(gdb) p fib_table->ft_desc
$3 = (u8 *) 0x3eb07a80 "ipv4-VRF:0"
(gdb) p *fib_table
$4 = {{v4 = {fib_entry_by_dst_address = {0x3d92f738, 0x0, 0x0, 0x0, 
0x3d92ead8, 0x0 , 0x3d92b9a0, 0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 0x3d92f170}, mtrie = {
ply_pool = 0x3eb5b000, default_leaf = 1}, table_id = 0, index = 0, 
flow_hash_config = 31, fwd_classify_table_index = 4294967295, 
rev_classify_table_index = 4294967295}, v6 = {
  table_id = 1033041720, index = 65535, flow_hash_config = 0}, mpls = 
{mf_entries = 0x3d92f738, mf_lbs = {0, 0, 0, 0, 0, 0, 1033038552, 65535, 0 
, 1033025952, 65535,
0 , 1033040240, 65535, 1052094464, 65535, 1, 0, 0, 0, 
31, 4294967295, 4294967295, 0 }}}, ft_proto = 
FIB_PROTOCOL_IP4, ft_locks = 3,
  ft_table_id = 0, ft_index = 0, ft_flow_hash_config = 31, ft_src_route_counts 
= {2, 0, 5, 0, 3, 0 , 3}, ft_total_route_counts = 11, ft_desc 
= 0x3eb07a80 "ipv4-VRF:0"}



Regards,
Bhanu,
HSDC, NXP India.


From: Dave Barach (dbarach) [mailto:dbar...@cisco.com]
Sent: Tuesday, September 12, 2017 10:04 PM
To: Bhanu Chander Gaddoju 
>; 
vpp-dev@lists.fd.io; Ni, Hongjun 
>
Subject: RE: VPP 1704 and router plugin

Set a breakpoint in format_fib_table_name, and see if e.g. fib_table->ft_desc 
is NULL.

Thanks… Dave

From: vpp-dev-boun...@lists.fd.io 

Re: [vpp-dev] net/mlx5: install libmlx5 & libibverbs if no OFED

[Damjan Marion (damarion)]

We don’t want official binaries to be linked against libibverbs so, and forcing 
all vpp consumers to install
subset of OFED packages to get VPP running.

If you are able to  statically link all dependencies into dpdk_plugin then 
mlx4/mlx5 pmd can be enabled in default build.
We do similar thing with IPSec MB libs...

On 19 Sep 2017, at 09:12, Shachar Beiser 
> wrote:
Hi Damjan,

  Can you please explain why dynamic linkage preventing to enable “mlx4/5  PMDs 
as default” ?

-Shachar Beiser.

From: Damjan Marion (damarion) [mailto:damar...@cisco.com]
Sent: Tuesday, September 19, 2017 3:23 PM
To: Shachar Beiser >
Cc: vpp-dev@lists.fd.io; Shahaf Shuler 
>
Subject: Re: net/mlx5: install libmlx5 & libibverbs if no OFED



I need to take a a deeper look into it. I’m currently on business travel so It 
will take a bit more time.

If I get it right this still uses dynamically linked libraries so we cannot 
enable mlx4/5  PMDs as default.
Is that correct?

Thanks.,

Damjan

On 19 Sep 2017, at 06:29, Shachar Beiser 
> wrote:

Hi ,

 I have sent a second patch for a review. I wait for comments .

  -Shachar Beiser.

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

[vpp-dev] 17.07.01 Released

[Neale Ranns (nranns)]

Dear All,

The 17.07.01 release is now available on a nexus server near you.

Best regards,
neale

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

Re: [vpp-dev] net/mlx5: install libmlx5 & libibverbs if no OFED

[Shachar Beiser]

From: Damjan Marion (damarion) [mailto:damar...@cisco.com]
Sent: Tuesday, September 19, 2017 3:23 PM
To: Shachar Beiser 
Cc: vpp-dev@lists.fd.io; Shahaf Shuler 
Subject: Re: net/mlx5: install libmlx5 & libibverbs if no OFED



I need to take a a deeper look into it. I’m currently on business travel so It 
will take a bit more time.

If I get it right this still uses dynamically linked libraries so we cannot 
enable mlx4/5  PMDs as default.
Is that correct?
The difference between [PATCH v1] and [PATCH v2] is that
I have changed the DISTRO to work the same way you do in the VPP Makefile.
ifeq ($(filter ubuntu debian,$(OS_ID)),$(OS_ID))
RH_OFED := 0
else ifeq ($(filter rhel centos fedora opensuse,$(OS_ID)),$(OS_ID))
RH_OFED := 1
Endif

For the linkage, yes is dynamic as before. I have not changed that .

Thanks.,

Damjan

On 19 Sep 2017, at 06:29, Shachar Beiser 
> wrote:

Hi ,

 I have sent a second patch for a review. I wait for comments .

  -Shachar Beiser.

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

Re: [vpp-dev] net/mlx5: install libmlx5 & libibverbs if no OFED

[Damjan Marion (damarion)]

I need to take a a deeper look into it. I’m currently on business travel so It 
will take a bit more time.

If I get it right this still uses dynamically linked libraries so we cannot 
enable mlx4/5  PMDs as default.
Is that correct?

Thanks.,

Damjan

On 19 Sep 2017, at 06:29, Shachar Beiser 
> wrote:

Hi ,

 I have sent a second patch for a review. I wait for comments .

  -Shachar Beiser.

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