[vpp-dev] Could anyone please take a look at commit 7182?
Dear vpp-dev, 23 days ago, I committed this patch: https://gerrit.fd.io/r/#/c/7182/ for the flowprobe plugin to fix a bug which will cause assertion error for certain parameters. The original committer Ole Troan seems to be not available after giving some comments. Could anyone please take a look at this one-line fix if possible and give code review feedback so that I could proceed? Regards, Andrew ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Why VPP drop packets while the average vectors per node is still low
Hi Xiang, My best guess is that the rx-miss field comes from DPDK, quote from their datasheet: Packets are missed when the receive FIFO has insufficient space to store the incoming packet. This might be caused due to insufficient buffers allocated, or because there is insufficient bandwidth on the IO bus. And most likely it’s not related to VPP itself. Thanks, Andrew On 17/07/2017, 9:59 AM, "vpp-dev-boun...@lists.fd.io on behalf of 陈祥" wrote: Hi, guys Last week I did some performance test on VPP with Spirent testcenter. Below I give two groups of running data in two different situation using the 'show run' command . In both situation VPP drop packets ( from the 'rx-miss' output in 'show int' command). In my opinion, when VPP begins to drop packets, the value of Vectors/Call should be high. So I think situation 1 is easy to understand. But the running data of situation 2 make me confused because Vectors/Call is still very low. Can anyone explains why and what's the relationship between VPP performance and average vectors per node? situation 1--- Thread 1 vpp_wk_0 (lcore 1) Time 225.3, average vectors/node 255.99, last 128 main loops 0.00 per node 0.00 vector rates in 2.2244e6, out 2.2242e6, drop 2.0019e2, punt 0.e0 Name State Calls Vectors Suspends Clocks Vectors/Call TenGigabitEthernet6/0/1-output active1957460 501107294 0 8.67e0 255.99 TenGigabitEthernet6/0/1-tx active1957460 501107294 0 1.08e2 255.99 dpdk-input polling1227897513 501152389 0 4.65e2 .41 error-drop active182 45103 0 4.15e1 247.82 ip4-arp active138 34616 0 3.43e1 250.84 ip4-drop active 44 10487 0 8.91e0 238.34 ip4-input-no-checksumactive1957630 501152389 0 3.77e1 255.99 ip4-lookup active1957630 501152389 0 2.98e1 255.99 ip4-mimic-classify active1957630 501152389 0 2.13e2 255.99 ip4-rewrite active1957452 501107286 0 2.96e1 255.99 lookup-ip4-src active1957630 501152389 0 5.07e1 255.99 snat-in2out-fast active1957630 501152389 0 2.56e2 255.99 situation 2--- Thread 2 vpp_wk_1 (lcore 2) Time 1024.5, average vectors/node 8.57, last 128 main loops 0.00 per node 0.00 vector rates in 1.2209e6, out 1.2209e6, drop 0.e0, punt 0.e0 Name State Calls Vectors Suspends Clocks Vectors/Call TenGigabitEthernet6/0/0-output active 145982828 1250882588 0 2.93e18.57 TenGigabitEthernet6/0/0-tx active 145982828 1250882588 0 1.37e28.57 dpdk-input polling9106470948 1250882588 0 1.31e3 .14 ip4-input-no-checksumactive 145982828 1250882588 0 7.39e18.57 ip4-lookup active 145982828 1250882588 0 7.56e18.57 ip4-mimic-classify active 145982828 1250882588 0 1.31e28.57 ip4-rewrite active 145982828 1250882588 0 6.33e18.57 snat-out2in-fast active 145982828 1250882588 0 4.50e18.57 ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Why VPP drop packets while the average vectors per node is still low
Sorry, I take back my word on “most likely it’s not related to VPP itself”. Since VPP fetch vectors from the NIC’s RX ring, it’d be possible that the NIC run out of space before VPP could poll enough vectors out. But it’s still strange in this case, as 8 vectors/Call means that VPP is not working hard at all. So, it should be unlikely that the packets are dropped. Please follow the other thread with the VPP experts…Sorry for the possible confusion I brought to you. Thanks, Andrew On 17/07/2017, 3:56 PM, "vpp-dev-boun...@lists.fd.io on behalf of Andrew Li (zhaoxili)" wrote: Hi Xiang, My best guess is that the rx-miss field comes from DPDK, quote from their datasheet: Packets are missed when the receive FIFO has insufficient space to store the incoming packet. This might be caused due to insufficient buffers allocated, or because there is insufficient bandwidth on the IO bus. And most likely it’s not related to VPP itself. Thanks, Andrew On 17/07/2017, 9:59 AM, "vpp-dev-boun...@lists.fd.io on behalf of 陈祥" wrote: Hi, guys Last week I did some performance test on VPP with Spirent testcenter. Below I give two groups of running data in two different situation using the 'show run' command . In both situation VPP drop packets ( from the 'rx-miss' output in 'show int' command). In my opinion, when VPP begins to drop packets, the value of Vectors/Call should be high. So I think situation 1 is easy to understand. But the running data of situation 2 make me confused because Vectors/Call is still very low. Can anyone explains why and what's the relationship between VPP performance and average vectors per node? situation 1--- Thread 1 vpp_wk_0 (lcore 1) Time 225.3, average vectors/node 255.99, last 128 main loops 0.00 per node 0.00 vector rates in 2.2244e6, out 2.2242e6, drop 2.0019e2, punt 0.e0 Name State Calls Vectors Suspends Clocks Vectors/Call TenGigabitEthernet6/0/1-output active1957460 501107294 0 8.67e0 255.99 TenGigabitEthernet6/0/1-tx active1957460 501107294 0 1.08e2 255.99 dpdk-input polling1227897513 501152389 0 4.65e2 .41 error-drop active182 45103 0 4.15e1 247.82 ip4-arp active138 34616 0 3.43e1 250.84 ip4-drop active 44 10487 0 8.91e0 238.34 ip4-input-no-checksumactive1957630 501152389 0 3.77e1 255.99 ip4-lookup active1957630 501152389 0 2.98e1 255.99 ip4-mimic-classify active1957630 501152389 0 2.13e2 255.99 ip4-rewrite active1957452 501107286 0 2.96e1 255.99 lookup-ip4-src active1957630 501152389 0 5.07e1 255.99 snat-in2out-fast active1957630 501152389 0 2.56e2 255.99 situation 2--- Thread 2 vpp_wk_1 (lcore 2) Time 1024.5, average vectors/node 8.57, last 128 main loops 0.00 per node 0.00 vector rates in 1.2209e6, out 1.2209e6, drop 0.e0, punt 0.e0 Name State Calls Vectors Suspends Clocks Vectors/Call TenGigabitEthernet6/0/0-output active 145982828 1250882588 0 2.93e18.57 TenGigabitEthernet6/0/0-tx active 145982828 1250882588 0 1.37e28.57 dpdk-input polling9106470948 1250882588 0 1.31e3 .14 ip4-input-no-checksumactive 145982828 1250882588 0 7.39e18.57 ip4-lookup active 145982828 125
Re: [vpp-dev] bug?
Looks like a patch was submitted earlier on that one but not yet merged: https://gerrit.fd.io/r/#/c/7512/ Thanks, Andrew On 20/07/2017, 7:31 AM, "vpp-dev-boun...@lists.fd.io on behalf of Yuliang Li" wrote: Hi, I clone the code from https://gerrit.fd.io/r/vpp. In threads.c, line 643-645: 643 nm_clone->nodes_by_type[VLIB_NODE_TYPE_INTERNAL] = 644 vec_dup (nm->nodes_by_type[VLIB_NODE_TYPE_INTERNAL]); 645 vec_foreach (rt, nm_clone->nodes_by_type[VLIB_NODE_TYPE_INPUT]) Should the VLIB_NODE_TYPE_INPUT in line 645 be VLIB_NODE_TYPE_INTERNAL? Thanks, -- Yuliang Li PhD student Department of Computer Science Yale University ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] Discussion on flowStartNanoSeconds field in flow-per-packet plugin
Hi everyone, Trying out the flow-per-packet plugin which Dave hacked and merged a few days ago. While it works fine in general I’ve noticed the flowStartNanoseconds field here stands for the time since vpp started. This brings in the problem that the collector has to know when VPP started as well. So here’re my questions: 1. How should I know the time when VPP started? 2. Is there a special concern that why this field can’t be the time since a fixed time, say 19700101? In RFC 5102 it said: Timestamps flowStartSeconds, flowEndSeconds, flowStartMilliseconds, flowEndMilliseconds, flowStartMicroseconds, flowEndMicroseconds, flowStartNanoseconds, flowEndNanoseconds, and systemInitTimeMilliseconds are absolute and have a well-defined fixed time base, such as, for example, the number of seconds since UTC Jan 1st 1970. It also recommended using flowStartSysUpTime to represent the time relative to the last initialization of the IPFIX Device: Timestamps flowStartSysUpTime and flowEndSysUpTime are relative timestamps indicating the time relative to the last (re- )initialization of the IPFIX Device. For reporting the time of the last (re-)initialization, systemInitTimeMilliseconds can be reported, for example, in Data Records defined by Option Templates. For reference the plugin is in vpp/plugins/flowperpkt-plugin. Thanks, Andrew ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] May I get clarification on the meaning of vpp_get_metrics api?
Hi everyone, I’m now looking at vpp/vpp-api/vpp_get_metrics.c, which shows the following stats: 1. Vector_rate(vector_counts_per_main_loop / node_counts_per_main_loop): So based on my understanding this shows the average vector length per node per main loop(During the window of last X main loops) ranging from 0 – 255 (For a vector size of 256)? And when it reaches 255 it means that VPP is running in 100% capacity? 2. Input_rate(Aggregate Rx rate): This means the number of packets received from dpdk-input node per second during the set interval? 3. Error_rate(Significant Error rate): This means the number of error packets from all nodes per second during the set interval? (Shown in vppctl sh err?) There’s not much said about it, and I just tried to guess it from the source code. I hope a clarification can be made on these stats so everyone can understand it without confusions. Thanks, Andrew ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] May I get clarification on the meaning of vpp_get_metrics api?
And a follow up question: What’s the difference between these three stats? Time 34962.2, average vectors/node 14.93, last 128 main loops 0.00 per node 0.00 I suppose the first one is number of vectors processed / number of calls. But what about the second and the third one? Thanks, Andrew From: "Andrew Li (zhaoxili)" Date: Monday, 14 November 2016 at 1:41 PM To: "vpp-dev@lists.fd.io" Subject: May I get clarification on the meaning of vpp_get_metrics api? Hi everyone, I’m now looking at vpp/vpp-api/vpp_get_metrics.c, which shows the following stats: 1. Vector_rate(vector_counts_per_main_loop / node_counts_per_main_loop): So based on my understanding this shows the average vector length per node per main loop(During the window of last X main loops) ranging from 0 – 255 (For a vector size of 256)? And when it reaches 255 it means that VPP is running in 100% capacity? 2. Input_rate(Aggregate Rx rate): This means the number of packets received from dpdk-input node per second during the set interval? 3. Error_rate(Significant Error rate): This means the number of error packets from all nodes per second during the set interval? (Shown in vppctl sh err?) There’s not much said about it, and I just tried to guess it from the source code. I hope a clarification can be made on these stats so everyone can understand it without confusions. Thanks, Andrew ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] ioam_trace plugin: registration of HBH_OPTION_TYPE_IOAM_TRACE_DATA_LIST failed
Hi vpp-dev, Yesterday when I upgraded my VPP to latest master, VPP was refusing to start. The last hint was: Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_get_msg_ids:1324: WARNING: duplicate message range registration for 'ioam_trace_715b0386' Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_add_c6300bd4' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_add_reply_fcf91946' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_del_94b1447f' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_del_reply_d04895a4' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_show_config_983f7b0c' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_show_config_reply_4f6f9bdd' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: ip6_hop_by_hop_ioam_trace_init: registration of HBH_OPTION_TYPE_IOAM_TRACE_DATA_LIST failed I was using an earlier master (head dcbc86a on Dec 2) and that worked perfectly. So, something happened in between led to this. I tried to delete the /usr/lib/vpp_plugins/libioam_trace_plugin.so which solved this problem and VPP was able to start properly again. But it’s still strange that nobody reported this. Am I missing something? I’m working on Ubuntu Xenial 16.04. Thanks, Andrew ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] ioam_trace plugin: registration of HBH_OPTION_TYPE_IOAM_TRACE_DATA_LIST failed
Yes, but it’s really strange. I’m sure it’s because the rpath in the deb packages led to duplicated ioam plugins. But Vengada and Shwetha contacted me and assured me that it has been solved in master branch with Damjan’s fix. So, I just initialized a new 16.04 VM and installed VPP from master. And the problem remains. Removing either ~/vpp/build-root/install-vpp-native/plugins/lib64/vpp_plugins/libioam_trace_plugin.so or /usr/lib/vpp_plugins/libioam_trace_plugin.so solves this problem. Anyway, I’ll leave it like that for now if I’m the only victim… Thanks, Andrew From: "Dave Barach (dbarach)" Date: Thursday, 22 December 2016 at 10:39 PM To: "Andrew Li (zhaoxili)" , "vpp-dev@lists.fd.io" Subject: RE: [vpp-dev] ioam_trace plugin: registration of HBH_OPTION_TYPE_IOAM_TRACE_DATA_LIST failed Workaround: you can make the pain go away by trashing the ioam plugin(s), e.g. in /usr/lib/vpp_plugins. Or, disable them in .../plugins/configure.ac in the obvious way, remove / rebuild / reinstall the Debian plugin package. Thanks… Dave From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Andrew Li (zhaoxili) Sent: Thursday, December 22, 2016 3:53 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] ioam_trace plugin: registration of HBH_OPTION_TYPE_IOAM_TRACE_DATA_LIST failed Hi vpp-dev, Yesterday when I upgraded my VPP to latest master, VPP was refusing to start. The last hint was: Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_get_msg_ids:1324: WARNING: duplicate message range registration for 'ioam_trace_715b0386' Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_add_c6300bd4' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_add_reply_fcf91946' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_del_94b1447f' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_del_reply_d04895a4' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_show_config_983f7b0c' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: vl_msg_api_add_msg_name_crc:1361: attempt to redefine 'trace_profile_show_config_reply_4f6f9bdd' ignored... Dec 22 08:30:37 ubuntu-xenial vpp[6999]: 0: ip6_hop_by_hop_ioam_trace_init: registration of HBH_OPTION_TYPE_IOAM_TRACE_DATA_LIST failed I was using an earlier master (head dcbc86a on Dec 2) and that worked perfectly. So, something happened in between led to this. I tried to delete the /usr/lib/vpp_plugins/libioam_trace_plugin.so which solved this problem and VPP was able to start properly again. But it’s still strange that nobody reported this. Am I missing something? I’m working on Ubuntu Xenial 16.04. Thanks, Andrew ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] FW: Error reading from file descriptor 9: Input/output error
Hi vpp-dev, I’m encountering this strange issue: VPP keeps generating this error message into /var/log/syslog: Jan 24 23:28:19 localhost vpp[4749]: EAL: Error reading from file descriptor 9: Input/output error Jan 24 23:28:19 localhost vpp[4749]: /usr/bin/vpp[4749]: EAL: Error reading from file descriptor 9: Input/output error And my disk space is being eaten quickly…Haven’t encountered this before. VPP version(latest master): stack@devstack-vpp2:~/src/vpp$ git log commit f69ecfe09db52c672ccbe47e714bc9c9a70d5539 Author: Andrew Yourtchenko Date: Tue Jan 24 15:47:27 2017 +0100 Does anyone know what this error means? Or how to solve this? Looks like a dpdk issue. Thanks, Andrew ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Error reading from file descriptor 9: Input/output error
Hi Damjan, Yes…and will it hurt anything other than printing this error message? If so we could move to VMXNET3. Thanks, Andrew From: Damjan Marion Date: Wednesday, 25 January 2017 at 6:27 PM To: "Andrew Li (zhaoxili)" Cc: "vpp-dev@lists.fd.io" Subject: Re: [vpp-dev] Error reading from file descriptor 9: Input/output error On 25 Jan 2017, at 05:43, Andrew Li (zhaoxili) mailto:zhaox...@cisco.com>> wrote: Hi vpp-dev, I’m encountering this strange issue: VPP keeps generating this error message into /var/log/syslog: Jan 24 23:28:19 localhost vpp[4749]: EAL: Error reading from file descriptor 9: Input/output error Jan 24 23:28:19 localhost vpp[4749]: /usr/bin/vpp[4749]: EAL: Error reading from file descriptor 9: Input/output error And my disk space is being eaten quickly…Haven’t encountered this before. VPP version(latest master): stack@devstack-vpp2:~/src/vpp$ git log commit f69ecfe09db52c672ccbe47e714bc9c9a70d5539 Author: Andrew Yourtchenko mailto:ayour...@gmail.com>> Date: Tue Jan 24 15:47:27 2017 +0100 Does anyone know what this error means? Or how to solve this? Looks like a dpdk issue. Are you using ESXi VM with e1000 interfaces? ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] Error reading from file descriptor 9: Input/output error
Thank you, Dave, and Damjan, that’s clear enough for this question…We’ll plan to switch to Vmxnet3 then. - Andrew From: "Dave Barach (dbarach)" Date: Wednesday, 25 January 2017 at 9:37 PM To: "Andrew Li (zhaoxili)" , Damjan Marion Cc: "vpp-dev@lists.fd.io" Subject: RE: [vpp-dev] Error reading from file descriptor 9: Input/output error Vmxnet3 interfaces are strongly preferred: for performance, as well as to make this specific issue disappear. We have a patch floating around which turns off the disk-filling syslog message, but if you simply switch to vmxnet3 interfaces the pain will go away without rebuilding images, etc. etc. HTH... D From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Andrew Li (zhaoxili) Sent: Wednesday, January 25, 2017 6:51 AM To: Damjan Marion Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] Error reading from file descriptor 9: Input/output error Hi Damjan, Yes…and will it hurt anything other than printing this error message? If so we could move to VMXNET3. Thanks, Andrew From: Damjan Marion mailto:dmarion.li...@gmail.com>> Date: Wednesday, 25 January 2017 at 6:27 PM To: "Andrew Li (zhaoxili)" mailto:zhaox...@cisco.com>> Cc: "vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>" mailto:vpp-dev@lists.fd.io>> Subject: Re: [vpp-dev] Error reading from file descriptor 9: Input/output error On 25 Jan 2017, at 05:43, Andrew Li (zhaoxili) mailto:zhaox...@cisco.com>> wrote: Hi vpp-dev, I’m encountering this strange issue: VPP keeps generating this error message into /var/log/syslog: Jan 24 23:28:19 localhost vpp[4749]: EAL: Error reading from file descriptor 9: Input/output error Jan 24 23:28:19 localhost vpp[4749]: /usr/bin/vpp[4749]: EAL: Error reading from file descriptor 9: Input/output error And my disk space is being eaten quickly…Haven’t encountered this before. VPP version(latest master): stack@devstack-vpp2:~/src/vpp$ git log commit f69ecfe09db52c672ccbe47e714bc9c9a70d5539 Author: Andrew Yourtchenko mailto:ayour...@gmail.com>> Date: Tue Jan 24 15:47:27 2017 +0100 Does anyone know what this error means? Or how to solve this? Looks like a dpdk issue. Are you using ESXi VM with e1000 interfaces? ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
[vpp-dev] The right way to disable dpdk-plugin?
Hi vpp-dev,
I’m trying to run VPP without dpdk enabled. According to previous mails, looks
like I need to add this to startup.conf:
plugins {
plugin dpdk_plugin.so { disable }
}
However when I restart VPP, it was not happy with the fact that DPDK was gone:
…
Apr 5 23:28:12 guestendpoint-vpp-vxlan-jkulrk-server-1 vpp[2805]:
load_one_plugin:103: Plugin disabled: dpdk_plugin.so
…
Apr 5 23:28:12 guestendpoint-vpp-vxlan-jkulrk-server-1 vpp[2805]:
vlib_call_all_config_functions: unknown input `dpdk '
Apr 5 23:28:12 guestendpoint-vpp-vxlan-jkulrk-server-1 systemd[1]:
vpp.service: Main process exited, code=exited, status=1/FAILURE
Is there a way to gracefully stop VPP from using DPDK (like we did in VPP-lite)?
Thanks,
Andrew
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] The right way to disable dpdk-plugin?
It works, thanks Sergio.
Thanks,
Andrew
On 06/04/2017, 3:41 PM, "Sergio Gonzalez Monroy"
wrote:
On 06/04/2017 07:37, Andrew Li (zhaoxili) wrote:
> Hi vpp-dev,
>
> I’m trying to run VPP without dpdk enabled. According to previous mails,
looks like I need to add this to startup.conf:
> plugins {
> plugin dpdk_plugin.so { disable }
> }
> However when I restart VPP, it was not happy with the fact that DPDK was
gone:
> …
> Apr 5 23:28:12 guestendpoint-vpp-vxlan-jkulrk-server-1 vpp[2805]:
load_one_plugin:103: Plugin disabled: dpdk_plugin.so
> …
> Apr 5 23:28:12 guestendpoint-vpp-vxlan-jkulrk-server-1 vpp[2805]:
vlib_call_all_config_functions: unknown input `dpdk '
> Apr 5 23:28:12 guestendpoint-vpp-vxlan-jkulrk-server-1 systemd[1]:
vpp.service: Main process exited, code=exited, status=1/FAILURE
>
> Is there a way to gracefully stop VPP from using DPDK (like we did in
VPP-lite)?
I think you just need to comment out the dpdk section, as was done in
the following change:
https://gerrit.fd.io/r/#/c/5837/
Regards,
Sergio
> Thanks,
> Andrew
>
>
> ___
> 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
