date:20180201

[vpp-dev] Support for recvmmsg

2018-02-01 Thread Shashi Kant Singh

Hello
I have a requirement in my application to read multiple packets in single call 
like recvmmsg supported by native linux stack.
In VPP, I see the following. Let me know what is the plan on supporting 
vcom_socket_recvmmsg.

Regards
Shashi

/*
* Receive up to VLEN messages as described by VMESSAGES from socket FD.
* Returns the number of messages received or -1 for errors.
* This function is a cancellation point and therefore not marked
* with __THROW.
* */
int
vcom_recvmmsg (int __fd, struct mmsghdr *__vmessages,
   unsigned int __vlen, int __flags, struct timespec *__tmo)
{
  if (vcom_init () != 0)
{
  return -1;
}

  return vcom_socket_recvmmsg (__fd, __message, __vlen, __flags, __tmo);
}

int
recvmmsg (int __fd, struct mmsghdr *__vmessages,
  unsigned int __vlen, int __flags, struct timespec *__tmo)
{
  ssize_t size;
  pid_t pid = getpid ();

  if (is_vcom_socket_fd (__fd))
{
  size = vcom_recvmmsg (__fd, __message, __vlen, __flags, __tmo);
  if (VCOM_DEBUG > 0)
fprintf (stderr,
 "[%d] recvmmsg: "
 "'%04d'='%04d', '%p', "
 "'%04d', '%04x', '%p'\n",
 pid, (int) size, __fd, __vmessages, __vlen, __flags, __tmo);
  if (size < 0)
{
  errno = -size;
  return -1;
}
  return size;
}
  return libc_recvmmsg (__fd, __message, __vlen, __flags, __tmo);
}

nt
vcom_socket_recvmmsg (int __fd, struct mmsghdr *__vmessages,
  unsigned int __vlen, int __flags,
  struct timespec *__tmo)
{
  /* TBD: define a new vppcom api */
  return 0;
}
#endif



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

Re: [vpp-dev] How to get dns server of dhcp client interface

2018-02-01 Thread 陈敬志

Hi Dave,

thanks, I will have a try as you said.

Regards,

jzhchen
From: Dave Barach (dbarach)
Date: 2018-01-31 23:41
To: 陈敬志; vpp-dev
Subject: Re: [vpp-dev] How to get dns server of dhcp client interface
Option 6 (dhcp server) parsing is not implemented. See 
…/src/vnet/dhcp/client.c, switch statement near line 112… 

Should be a simple coding task. Feel free to submit a patch.

Worst-case, file a Jira ticket so we don’t forget about it.

Thanks… Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of ???
Sent: Tuesday, January 30, 2018 7:58 PM
To: vpp-dev 
Subject: [vpp-dev] How to get dns server of dhcp client interface

Hi,vpp-dev team,
When I use dhcp client to get a wan ip address for vpp interface,How to get the 
dns server address?
sudo vppctl set dhcp client intfc GigabitEthernet0/a/0
vagrant@localhost:~$ sudo vppctl show dhcp client 
[0] GigabitEthernet0/a/0 state DHCP_BOUND addr 10.180.30.193/24 gw 10.180.30.1

Thanks.

Regards,
Jzhchen

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

Re: [vpp-dev] Guidance on using UDP / TCP built-in servers

2018-02-01 Thread Shaun McGinnity

Hi Florin,


thanks, I will give that a go.


Regards,


Shaun



From: Florin Coras 
Sent: 01 February 2018 19:09
To: Shaun McGinnity
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Guidance on using UDP / TCP built-in servers

Hi Shaun,

Those have recently been moved to session-apps. The short cli help should give 
you an idea of how to configure them: “test echo server ?"

For starters, doing something like: "test echo server uri :///" starts a server that listens on the ip:port tuple 
for the transport requested.

On a different vpp you can do: "test echo client uri ” 
to connect the client to the server. Note that only the tcp and sctp clients 
are properly supported for now. Additionally, for this to work, the two vpps 
should obviously be configured to have ip layer connectivity between them.

Let me know if you have more specific questions.

Regards,
Florin

On Feb 1, 2018, at 10:33 AM, Shaun McGinnity 
mailto:shaun.mcginn...@owmobility.com>> wrote:

Hi,

Could anyone point me to documentation or a tutorial on using the built-in UDP 
/ TCP servers under ./src/vnet/udp and ./src/vnet/tcp ?

Regards,

Shaun
___
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] Guidance on using UDP / TCP built-in servers

2018-02-01 Thread Florin Coras

Hi Shaun, 

Those have recently been moved to session-apps. The short cli help should give 
you an idea of how to configure them: “test echo server ?"

For starters, doing something like: "test echo server uri :///" starts a server that listens on the ip:port tuple 
for the transport requested.

On a different vpp you can do: "test echo client uri ” 
to connect the client to the server. Note that only the tcp and sctp clients 
are properly supported for now. Additionally, for this to work, the two vpps 
should obviously be configured to have ip layer connectivity between them. 

Let me know if you have more specific questions. 

Regards, 
Florin

> On Feb 1, 2018, at 10:33 AM, Shaun McGinnity  
> wrote:
> 
> Hi,
>  
> Could anyone point me to documentation or a tutorial on using the built-in 
> UDP / TCP servers under ./src/vnet/udp and ./src/vnet/tcp ?
>  
> Regards,
>  
> Shaun
> ___
> 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] Guidance on using UDP / TCP built-in servers

2018-02-01 Thread Shaun McGinnity

Hi,

Could anyone point me to documentation or a tutorial on using the built-in UDP 
/ TCP servers under ./src/vnet/udp and ./src/vnet/tcp ?

Regards,

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

Re: [vpp-dev] Consolidatation of fib_ip_proto() functions?

2018-02-01 Thread Neale Ranns (nranns)

Hi Jon,

I would welcome such a patch.

/neale

From: Jon Loeliger 
Date: Thursday, 1 February 2018 at 17:18
To: vpp-dev , "Neale Ranns (nranns)" 
Subject: Consolidatation of fib_ip_proto() functions?

Neale,

I have need of using a function like fib_ip_proto(), below, in yet another file.
But rather than introduce a 5th copy of the same function, would you
accept a patch that consolidated them all into one static inline in, say,
fib_types.h where the FIB_PROTOCOL_* values are defined?

Thanks,
jdl

static inline fib_protocol_t
fib_ip_proto(bool is_ip6)
{
  return (is_ip6) ? FIB_PROTOCOL_IP6 : FIB_PROTOCOL_IP4;
}

jdl@bcc-1 $ git grep fib_ip_proto src/
src/plugins/gtpu/gtpu.c:fib_ip_proto (bool is_ip6)
src/plugins/gtpu/gtpu.c:  fib_protocol_t fp = fib_ip_proto (is_ip6);
src/plugins/gtpu/gtpu.c:  encap_fib_index = fib_table_find 
(fib_ip_proto (ipv6_set), tmp);
src/vnet/geneve/geneve.c:fib_ip_proto (bool is_ip6)
src/vnet/geneve/geneve.c: fib_protocol_t fp = fib_ip_proto (is_ip6);
src/vnet/geneve/geneve.c: encap_fib_index = fib_table_find 
(fib_ip_proto (ipv6_set), tmp);
src/vnet/vxlan-gpe/vxlan_gpe.c:fib_ip_proto (bool is_ip6)
src/vnet/vxlan-gpe/vxlan_gpe.c:   fib_protocol_t fp = fib_ip_proto (is_ip6);
src/vnet/vxlan/vxlan.c:fib_ip_proto(bool is_ip6)
src/vnet/vxlan/vxlan.c:  fib_protocol_t fp = fib_ip_proto(is_ip6);
src/vnet/vxlan/vxlan.c:encap_fib_index = fib_table_find (fib_ip_proto 
(ipv6_set), tmp);

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

[vpp-dev] fd.io Community Goals and Objectives for reporting to the LFN board

2018-02-01 Thread Ed Warnicke

FD.io has recently transitioned from being its own independent foundation,
to being one of several projects (ONAP, OpNFV, ODL, etc) under the Linux
Foundation Networking (LFN) umbrella.

As part of this transition, the LFN board has asked to be educated about
what Goals and Objectives the community intends to undertake in the next
year.   Since an Open Source community intrinsically is a harmonious
collection of folks working on different things, the only way to
ascertain what its is really planning to do is to *ask* what folks are
planning to do.

What are the plans of various folks participating in the community for
2018?  What are the themes of the problems you are planning to address, the
kinds of features you are looking to implement etc?

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

[vpp-dev] Consolidatation of fib_ip_proto() functions?

2018-02-01 Thread Jon Loeliger

Neale,

I have need of using a function like fib_ip_proto(), below, in yet another
file.
But rather than introduce a 5th copy of the same function, would you
accept a patch that consolidated them all into one static inline in, say,
fib_types.h where the FIB_PROTOCOL_* values are defined?

Thanks,
jdl


static inline fib_protocol_t
fib_ip_proto(bool is_ip6)
{
  return (is_ip6) ? FIB_PROTOCOL_IP6 : FIB_PROTOCOL_IP4;
}


jdl@bcc-1 $ git grep fib_ip_proto src/
src/plugins/gtpu/gtpu.c:fib_ip_proto (bool is_ip6)
src/plugins/gtpu/gtpu.c:  fib_protocol_t fp = fib_ip_proto (is_ip6);
src/plugins/gtpu/gtpu.c:  encap_fib_index = fib_table_find
(fib_ip_proto (ipv6_set), tmp);
src/vnet/geneve/geneve.c:fib_ip_proto (bool is_ip6)
src/vnet/geneve/geneve.c: fib_protocol_t fp = fib_ip_proto (is_ip6);
src/vnet/geneve/geneve.c: encap_fib_index = fib_table_find
(fib_ip_proto (ipv6_set), tmp);
src/vnet/vxlan-gpe/vxlan_gpe.c:fib_ip_proto (bool is_ip6)
src/vnet/vxlan-gpe/vxlan_gpe.c:   fib_protocol_t fp = fib_ip_proto (is_ip6);
src/vnet/vxlan/vxlan.c:fib_ip_proto(bool is_ip6)
src/vnet/vxlan/vxlan.c:  fib_protocol_t fp = fib_ip_proto(is_ip6);
src/vnet/vxlan/vxlan.c:encap_fib_index = fib_table_find
(fib_ip_proto (ipv6_set), tmp);
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Questions about ACL features of VPP

2018-02-01 Thread Andrew Yourtchenko

Kaneko-San,

My replies are inline below.


> On 1 Feb 2018, at 02:38, kaneko  wrote:
> 
> Hello, my name is Hitoshi Kaneko.
> 
> I belong to NTT Laboratories.
> 
> I evaluate VPP and there have been questions.
> 
>  
> 
> (1)Question 1
> 
> I have wanted to evaluate Access Control List of VPP.
> 
> About this feature, I have read VPP Documents “1.3 VAT CLI, 
> VPP/SecurityGroups”.
> 
> There is a sentence “The ACL plugin does not supply the "supported" debug CLI 
> for configuration, but has the full support for talking to it via VAT CLI, 
> which are documented below” , at the beginning.
> 
> Does this mean that to register ACL rules can be done but ACL doesn’t “work” ?
> 
> I could register ACL rules with acl_add_replace command, but the ACL rules 
> did not work
> 
You would also need to apply the acl rules to an interface via another call, 
acl_interface_set_acl_list, you can look here for an example:

https://wiki.fd.io/view/VPP/SecurityGroups#acl_interface_set_acl_list_:_set_the_list_of_inbound.2Boutbound_ACLs_for_a_given_interface


>  
> 
> (2)Question 2
> 
> If ACL doesn’t work about “1.3 VAT CLI, VPP/SecurityGroups”, does ACL work 
> about any other feature, for example, “set interface ip table” command, “set 
> ip source-and-port-range-check” command, and etc. .
> 
Acl is used at this time only for ingress and egress filtering on the 
interfaces.

Kind regards,
Andrew


>  
> 
> Regards,
> 
> Hitoshi Kaneko
> 
>  
> 
> E-mail: kaneko.hito...@lab.ntt.co.jp
> 
> Phone: +81 422 59 4946
> 
> ___
> 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] Error when trying to add interface to vpp on ARM server.

2018-02-01 Thread adarsh m via vpp-dev

 Hi,
After removing socket-mem now vpp is stable but when we try to connect through 
CLI connection is refused.

ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 21:42:23 CST; 1s ago
  Process: 49787 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 49793 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 49790 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 49796 (vpp)
   CGroup: /system.slice/vpp.service
   └─49796 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 19:37:16 vasily vpp[43454]: /usr/bin/vpp[43454]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 
0002:f9:00.0 --master-lcore 0 --socket-mem 1024,
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0002:f9:00.0 
--master-lcore 0 --socket-mem 1024,0,0,0
Feb 01 19:37:16 vasily vpp[43454]: EAL: VFIO support initialized
Feb 01 19:37:16 vasily vnet[43454]: EAL: VFIO support initialized
ubuntu@vasily:~$ sudo vppctl show int
clib_socket_init: connect (fd 3, '/run/vpp/cli.sock'): Connection refused
ubuntu@vasily:~$ 


Startup.conf :unix {
  nodaemon
  log /tmp/vpp.log
  full-coredump
  cli-listen /run/vpp/cli.sock
  gid vpp
}

api-trace {
## This stanza controls binary API tracing. Unless there is a very strong 
reason,
## please leave this feature enabled.
  on
## Additional parameters:
##
## To set the number of binary API trace records in the circular buffer, 
configure nitems
##
## nitems  
##
## To save the api message table decode tables, configure a filename. Results 
in /tmp/
## Very handy for understanding api message changes between versions, 
identifying missing
## plugins, and so forth.
##
## save-api-table 
}

api-segment {
  gid vpp
}

cpu {
    ## In the VPP there is one main thread and optionally the user can create 
worker(s)
    ## The main thread and worker thread(s) can be pinned to CPU core(s) 
manually or automatically

    ## Manual pinning of thread(s) to CPU core(s)

    ## Set logical CPU core where main thread runs
    # main-core 1

    ## Set logical CPU core(s) where worker threads are running
    # corelist-workers 2-3,18-19

    ## Automatic pinning of thread(s) to CPU core(s)

    ## Sets number of CPU core(s) to be skipped (1 ... N-1)
    ## Skipped CPU core(s) are not used for pinning main thread and working 
thread(s).
    ## The main thread is automatically pinned to the first available CPU core 
and worker(s)
    ## are pinned to next free CPU core(s) after core assigned to main thread
    # skip-cores 4

    ## Specify a number of workers to be created
    ## Workers are pinned to N consecutive CPU cores while skipping 
"skip-cores" CPU core(s)
    ## and main thread's CPU core
    # workers 2

    ## Set scheduling policy and priority of main and worker threads

    ## Scheduling policy options are: other (SCHED_OTHER), batch (SCHED_BATCH)
    ## idle (SCHED_IDLE), fifo (SCHED_FIFO), rr (SCHED_RR)
    # scheduler-policy fifo

    ## Scheduling priority is used only for "real-time policies (fifo and rr),
    ## and has to be in the range of priorities supported for a particular 
policy
    # scheduler-priority 50
}

 dpdk {
   
   dev 0002:f9:00.0
    ## Change default settings for all intefaces
    # dev default {
        ## Number of receive queues, enables RSS
        ## Default is 1
        # num-rx-queues 3

        ## Number of transmit queues, Default is equal
        ## to number of worker threads or 1 if no workers treads
        # num-tx-queues 3

        ## Number of descriptors in transmit and receive rings
        ## increasing or reducing number can impact performance
        ## Default is 1024 for both rx and tx
        # num-rx-desc 512
        # num-tx-desc 512

        ## VLAN strip offload mode for interface
        ## Default i

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

2018-02-01 Thread adarsh m via vpp-dev

 Support 2 channel 32core processor(ARM64)

On Thursday 1 February 2018, 6:47:31 PM IST, Damjan Marion (damarion) 
 wrote:  
 
 You also added socket-mem which is pretty bad idea, try without.If that 
doesn't help then you will need to run VPP form console and possibly use gdb to 
collect more details.
Which ARM board is that?


On 1 Feb 2018, at 14:15, adarsh m  wrote:
Hi,
This is on ARM board. and yes i have modified the specific pcie address to 
added in startup.conf

 dpdk {
   socket-mem 1024
   dev 0002:f9:00.0

}


On Thursday 1 February 2018, 5:20:59 PM IST, Damjan Marion (damarion) 
 wrote:

Please keep mailing list in CC.
Those lines doesn't show that anything is wrong...
Is this 4 socket computer? Have you modified startup.conf?


On 1 Feb 2018, at 12:40, adarsh m  wrote:
Hi,
Very sorry pls check the complete one.

Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 19:37:16 vasily vpp[43454]: /usr/bin/vpp[43454]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 
0002:f9:00.0 --master-lcore 0 --socket-mem 1024,
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0002:f9:00.0 
--master-lcore 0 --socket-mem 1024,0,0,0
Feb 01 19:37:16 vasily vpp[43454]: EAL: VFIO support initialized
Feb 01 19:37:16 vasily vnet[43454]: EAL: VFIO support initialized




On Thursday 1 February 2018, 4:48:35 PM IST, Damjan Marion (damarion) 
 wrote: 


Unfortunately log you provided is incomplete and truncated so I cannot help 
much


On 1 Feb 2018, at 11:59, adarsh m  wrote:
Hi,
I checked hugepage and it was 0, so i freed this and increased it to 5120
ubuntu@vasily:~$ sudo -i
root@vasily:~# echo 5120 > /proc/sys/vm/nr_hugepages


now the previous error is not occurring when i start but VPP is not stable, 
it'll become dead after a few sceonds from start.
Logs : 
ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free: 5120
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) since Thu 2018-02-01 18:50:46 CST; 5min ago
  Process: 42736 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42731 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, 
status=0/SUCCESS)
  Process: 42728 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42726 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42731 (code=exited, status=0/SUCCESS)

Feb 01 18:50:46 vasily systemd[1]: vpp.service: Service hold-off time over, 
scheduling restart.
Feb 01 18:50:46 vasily systemd[1]: Stopped vector packet processing engine.
Feb 01 18:50:46 vasily systemd[1]: vpp.service: Start request repeated too 
quickly.
Feb 01 18:50:46 vasily systemd[1]: Failed to start vector packet processing 
engine.
Feb 01 18:56:12 vasily systemd[1]: Stopped vector packet processing engine.
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp start
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
   └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

2018-02-01 Thread adarsh m via vpp-dev

Hi,
This is on ARM board. and yes i have modified the specific pcie address to 
added in startup.conf

 dpdk {
   socket-mem 1024
   dev 0002:f9:00.0

}
 

On Thursday 1 February 2018, 5:20:59 PM IST, Damjan Marion (damarion) 
 wrote:  
 
 Please keep mailing list in CC.
Those lines doesn't show that anything is wrong...
Is this 4 socket computer? Have you modified startup.conf?


On 1 Feb 2018, at 12:40, adarsh m  wrote:
Hi,
Very sorry pls check the complete one.

Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 19:37:16 vasily vpp[43454]: /usr/bin/vpp[43454]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 
0002:f9:00.0 --master-lcore 0 --socket-mem 1024,
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0002:f9:00.0 
--master-lcore 0 --socket-mem 1024,0,0,0
Feb 01 19:37:16 vasily vpp[43454]: EAL: VFIO support initialized
Feb 01 19:37:16 vasily vnet[43454]: EAL: VFIO support initialized




On Thursday 1 February 2018, 4:48:35 PM IST, Damjan Marion (damarion) 
 wrote:


Unfortunately log you provided is incomplete and truncated so I cannot help 
much


On 1 Feb 2018, at 11:59, adarsh m  wrote:
Hi,
I checked hugepage and it was 0, so i freed this and increased it to 5120
ubuntu@vasily:~$ sudo -i
root@vasily:~# echo 5120 > /proc/sys/vm/nr_hugepages


now the previous error is not occurring when i start but VPP is not stable, 
it'll become dead after a few sceonds from start.
Logs : 
ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free: 5120
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) since Thu 2018-02-01 18:50:46 CST; 5min ago
  Process: 42736 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42731 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, 
status=0/SUCCESS)
  Process: 42728 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42726 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42731 (code=exited, status=0/SUCCESS)

Feb 01 18:50:46 vasily systemd[1]: vpp.service: Service hold-off time over, 
scheduling restart.
Feb 01 18:50:46 vasily systemd[1]: Stopped vector packet processing engine.
Feb 01 18:50:46 vasily systemd[1]: vpp.service: Start request repeated too 
quickly.
Feb 01 18:50:46 vasily systemd[1]: Failed to start vector packet processing 
engine.
Feb 01 18:56:12 vasily systemd[1]: Stopped vector packet processing engine.
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp start
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
   └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.s
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plu
Feb 01 18:56:49 vasily /usr/bin/vpp[42866

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

2018-02-01 Thread Damjan Marion (damarion)

You also added socket-mem which is pretty bad idea, try without.
If that doesn't help then you will need to run VPP form console and possibly 
use gdb to collect more details.

Which ARM board is that?


On 1 Feb 2018, at 14:15, adarsh m 
mailto:addi.ada...@yahoo.in>> wrote:

Hi,

This is on ARM board. and yes i have modified the specific pcie address to 
added in startup.conf

 dpdk {
   socket-mem 1024
   dev 0002:f9:00.0

}


On Thursday 1 February 2018, 5:20:59 PM IST, Damjan Marion (damarion) 
mailto:damar...@cisco.com>> wrote:


Please keep mailing list in CC.

Those lines doesn't show that anything is wrong...

Is this 4 socket computer? Have you modified startup.conf?


On 1 Feb 2018, at 12:40, adarsh m 
mailto:addi.ada...@yahoo.in>> wrote:

Hi,

Very sorry pls check the complete one.

Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 19:37:16 vasily vpp[43454]: /usr/bin/vpp[43454]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 
0002:f9:00.0 --master-lcore 0 --socket-mem 1024,
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0002:f9:00.0 
--master-lcore 0 --socket-mem 1024,0,0,0
Feb 01 19:37:16 vasily vpp[43454]: EAL: VFIO support initialized
Feb 01 19:37:16 vasily vnet[43454]: EAL: VFIO support initialized




On Thursday 1 February 2018, 4:48:35 PM IST, Damjan Marion (damarion) 
mailto:damar...@cisco.com>> wrote:



Unfortunately log you provided is incomplete and truncated so I cannot help 
much

On 1 Feb 2018, at 11:59, adarsh m 
mailto:addi.ada...@yahoo.in>> wrote:

Hi,

I checked hugepage and it was 0, so i freed this and increased it to 5120

ubuntu@vasily:~$ sudo -i
root@vasily:~# echo 5120 > /proc/sys/vm/nr_hugepages


now the previous error is not occurring when i start but VPP is not stable, 
it'll become dead after a few sceonds from start.

Logs :
ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free: 5120
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) since Thu 2018-02-01 18:50:46 CST; 5min ago
  Process: 42736 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42731 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, 
status=0/SUCCESS)
  Process: 42728 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42726 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42731 (code=exited, status=0/SUCCESS)

Feb 01 18:50:46 vasily systemd[1]: vpp.service: Service hold-off time over, 
scheduling restart.
Feb 01 18:50:46 vasily systemd[1]: Stopped vector packet processing engine.
Feb 01 18:50:46 vasily systemd[1]: vpp.service: Start request repeated too 
quickly.
Feb 01 18:50:46 vasily systemd[1]: Failed to start vector packet processing 
engine.
Feb 01 18:56:12 vasily systemd[1]: Stopped vector packet processing engine.
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp start
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
   └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plug

[vpp-dev] Questions about ACL features of VPP

2018-02-01 Thread kaneko


Hello, my name is Hitoshi Kaneko.

I belong to NTT Laboratories.

I evaluate VPP and there have been questions.

(1)Question 1

I have wanted to evaluate Access Control List of VPP.

About this feature, I have read VPP Documents “1.3 VAT CLI, 
VPP/SecurityGroups”.


There is a sentence “The ACL plugin does not supply the "supported" 
debug CLI for configuration, but has the full support for talking to it 
via VAT CLI, which are documented below” , at the beginning.


Does this mean that to register ACL rules can be done but ACL doesn’t 
“work” ?


I could register ACL rules with acl_add_replace command, but the ACL 
rules did not work.


(2)Question 2

If ACL doesn’t work about “1.3 VAT CLI, VPP/SecurityGroups”, does ACL 
work about any other feature, for example, “set interface ip table” 
command, “set ip source-and-port-range-check” command, and etc. .


Regards,

Hitoshi Kaneko

E-mail: kaneko.hito...@lab.ntt.co.jp 

Phone: +81 422 59 4946

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

Re: [vpp-dev] adding large number of route prefixes

2018-02-01 Thread Konrad Gutkowski


Hi,

Thanks for the info, that seems to brought 18.01 up to 1M, although it  
stops there.

With heap-size manipulation i can get 17.10 much higher (>3M).
While it seems to be purely academical at this point 18.01 showed  
preference towards sequential prefixes.


For 18.01 there seems to be no difference in maximum amount between 1G -  
4G setting, is that expected?


(only tested it with cli)

Konrad

W dniu 01.02.2018 o 10:11 Neale Ranns (nranns)  pisze:


Hi Konrad,

As of 18.01 the amount of memory available for IP routes is controlled  
in the startup config with:

  ip {heap-size }

/neale

-Original Message-
From:  on behalf of Konrad Gutkowski  


Date: Thursday, 1 February 2018 at 03:01
To: vpp-dev 
Subject: [vpp-dev] adding large number of route prefixes

Hi,
   While testing ipv4 routing I found that vpp crashes when supplied with
large sets of prefixes, the exact point when vpp goes down changes
depending on prefix set and vpp version tested.
   Tried 17.10 and 18.01, first consistently crashes at around 1m (though
tested only with sequential /24 and /32 prefixes), for the latter it
depends on the set, for sequential it's around 390k, while public bgp
table does crash pretty randomly around 100-300k, (my file has  
around 750k

routes).
   For 17.10, adding less than 1m prefixes works for both scenarios and
continues working - adding and deleting it multiple times does not  
cause

any stability issues.
It doesn't seem dependent on heap-size parameter value.
   I used both cli "ip route add count" as well as modified router  
plugin to

pull the table from netlink.
Any suggestions are welcome.
   --
Konrad Gutkowski
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev




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

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

2018-02-01 Thread Damjan Marion (damarion)

Please keep mailing list in CC.

Those lines doesn't show that anything is wrong...

Is this 4 socket computer? Have you modified startup.conf?


On 1 Feb 2018, at 12:40, adarsh m 
mailto:addi.ada...@yahoo.in>> wrote:

Hi,

Very sorry pls check the complete one.

Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 19:37:16 vasily vpp[43454]: /usr/bin/vpp[43454]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 
0002:f9:00.0 --master-lcore 0 --socket-mem 1024,
Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w 0002:f9:00.0 
--master-lcore 0 --socket-mem 1024,0,0,0
Feb 01 19:37:16 vasily vpp[43454]: EAL: VFIO support initialized
Feb 01 19:37:16 vasily vnet[43454]: EAL: VFIO support initialized




On Thursday 1 February 2018, 4:48:35 PM IST, Damjan Marion (damarion) 
mailto:damar...@cisco.com>> wrote:



Unfortunately log you provided is incomplete and truncated so I cannot help 
much

On 1 Feb 2018, at 11:59, adarsh m 
mailto:addi.ada...@yahoo.in>> wrote:

Hi,

I checked hugepage and it was 0, so i freed this and increased it to 5120

ubuntu@vasily:~$ sudo -i
root@vasily:~# echo 5120 > /proc/sys/vm/nr_hugepages


now the previous error is not occurring when i start but VPP is not stable, 
it'll become dead after a few sceonds from start.

Logs :
ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free: 5120
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) since Thu 2018-02-01 18:50:46 CST; 5min ago
  Process: 42736 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42731 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, 
status=0/SUCCESS)
  Process: 42728 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42726 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42731 (code=exited, status=0/SUCCESS)

Feb 01 18:50:46 vasily systemd[1]: vpp.service: Service hold-off time over, 
scheduling restart.
Feb 01 18:50:46 vasily systemd[1]: Stopped vector packet processing engine.
Feb 01 18:50:46 vasily systemd[1]: vpp.service: Start request repeated too 
quickly.
Feb 01 18:50:46 vasily systemd[1]: Failed to start vector packet processing 
engine.
Feb 01 18:56:12 vasily systemd[1]: Stopped vector packet processing engine.
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp start
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
   └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.s
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plu
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

2018-02-01 Thread Damjan Marion (damarion)


Unfortunately log you provided is incomplete and truncated so I cannot help 
much

On 1 Feb 2018, at 11:59, adarsh m 
mailto:addi.ada...@yahoo.in>> wrote:

Hi,

I checked hugepage and it was 0, so i freed this and increased it to 5120

ubuntu@vasily:~$ sudo -i
root@vasily:~# echo 5120 > /proc/sys/vm/nr_hugepages


now the previous error is not occurring when i start but VPP is not stable, 
it'll become dead after a few sceonds from start.

Logs :
ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free: 5120
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) since Thu 2018-02-01 18:50:46 CST; 5min ago
  Process: 42736 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42731 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, 
status=0/SUCCESS)
  Process: 42728 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42726 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42731 (code=exited, status=0/SUCCESS)

Feb 01 18:50:46 vasily systemd[1]: vpp.service: Service hold-off time over, 
scheduling restart.
Feb 01 18:50:46 vasily systemd[1]: Stopped vector packet processing engine.
Feb 01 18:50:46 vasily systemd[1]: vpp.service: Start request repeated too 
quickly.
Feb 01 18:50:46 vasily systemd[1]: Failed to start vector packet processing 
engine.
Feb 01 18:56:12 vasily systemd[1]: Stopped vector packet processing engine.
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp start
ubuntu@vasily:~$
ubuntu@vasily:~$
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
   └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.s
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plu
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 18:56:49 vasily vpp[42866]: /usr/bin/vpp[42866]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --f
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix v
Feb 01 18:56:49 vasily vpp[42866]: EAL: VFIO support initialized
Feb 01 18:56:49 vasily vnet[42866]: EAL: VFIO support initialized
...skipping...
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
   └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.s
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plu
Feb 01 18:56:49 vasily /usr/bin/vpp[428

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

2018-02-01 Thread adarsh m via vpp-dev

Hi,
I checked hugepage and it was 0, so i freed this and increased it to 5120 
ubuntu@vasily:~$ sudo -i
root@vasily:~# echo 5120 > /proc/sys/vm/nr_hugepages


now the previous error is not occurring when i start but VPP is not stable, 
it'll become dead after a few sceonds from start.
Logs : 
 ubuntu@vasily:~$ grep HugePages_Free /proc/meminfo
HugePages_Free: 5120
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: inactive (dead) since Thu 2018-02-01 18:50:46 CST; 5min ago
  Process: 42736 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42731 ExecStart=/usr/bin/vpp -c /etc/vpp/startup.conf (code=exited, 
status=0/SUCCESS)
  Process: 42728 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42726 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42731 (code=exited, status=0/SUCCESS)

Feb 01 18:50:46 vasily systemd[1]: vpp.service: Service hold-off time over, 
scheduling restart.
Feb 01 18:50:46 vasily systemd[1]: Stopped vector packet processing engine.
Feb 01 18:50:46 vasily systemd[1]: vpp.service: Start request repeated too 
quickly.
Feb 01 18:50:46 vasily systemd[1]: Failed to start vector packet processing 
engine.
Feb 01 18:56:12 vasily systemd[1]: Stopped vector packet processing engine.
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp start
ubuntu@vasily:~$ 
ubuntu@vasily:~$ 
ubuntu@vasily:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
   └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.s
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plu
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
Feb 01 18:56:49 vasily vpp[42866]: /usr/bin/vpp[42866]: dpdk_config:1240: EAL 
init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --f
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: dpdk_config:1240: EAL init args: -c 
1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix v
Feb 01 18:56:49 vasily vpp[42866]: EAL: VFIO support initialized
Feb 01 18:56:49 vasily vnet[42866]: EAL: VFIO support initialized
...skipping...
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Thu 2018-02-01 18:56:49 CST; 298ms ago
  Process: 42857 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 42863 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 42860 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 42866 (vpp)
   CGroup: /system.slice/vpp.service
   └─42866 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/acl_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.s
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plu
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63: Loaded plugin: 
/usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
Feb 01 18:56:49 vasily /usr/bin/vpp[42866]: load_one_plugin:63

Re: [vpp-dev] adding large number of route prefixes

2018-02-01 Thread Neale Ranns (nranns)

Hi Konrad,

As of 18.01 the amount of memory available for IP routes is controlled in the 
startup config with:
  ip {heap-size }

/neale

-Original Message-
From:  on behalf of Konrad Gutkowski 

Date: Thursday, 1 February 2018 at 03:01
To: vpp-dev 
Subject: [vpp-dev] adding large number of route prefixes

Hi,

While testing ipv4 routing I found that vpp crashes when supplied with  
large sets of prefixes, the exact point when vpp goes down changes  
depending on prefix set and vpp version tested.

Tried 17.10 and 18.01, first consistently crashes at around 1m (though  
tested only with sequential /24 and /32 prefixes), for the latter it  
depends on the set, for sequential it's around 390k, while public bgp  
table does crash pretty randomly around 100-300k, (my file has around 750k  
routes).

For 17.10, adding less than 1m prefixes works for both scenarios and  
continues working - adding and deleting it multiple times does not cause  
any stability issues.
It doesn't seem dependent on heap-size parameter value.

I used both cli "ip route add count" as well as modified router plugin to  
pull the table from netlink.
Any suggestions are welcome.

--
Konrad Gutkowski
___
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] Support for recvmmsg

Re: [vpp-dev] How to get dns server of dhcp client interface

Re: [vpp-dev] Guidance on using UDP / TCP built-in servers

Re: [vpp-dev] Guidance on using UDP / TCP built-in servers

[vpp-dev] Guidance on using UDP / TCP built-in servers

Re: [vpp-dev] Consolidatation of fib_ip_proto() functions?

[vpp-dev] fd.io Community Goals and Objectives for reporting to the LFN board

[vpp-dev] Consolidatation of fib_ip_proto() functions?

Re: [vpp-dev] Questions about ACL features of VPP

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

[vpp-dev] Questions about ACL features of VPP

Re: [vpp-dev] adding large number of route prefixes

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

Re: [vpp-dev] adding large number of route prefixes

19 matches

Site Navigation

Mail list logo

Footer information