Re: [vpp-dev] One question about vpp configuration file

> On 5 Mar 2019, at 08:01, Zhang, Yuwei1 wrote: > > Hello All, > I noticed there’s a config option in startup.conf file named > scheduler-priority, from the comments, it seems related to scheduling policy > about main and worker threads, could anybody give me some more detail > expl

Re: [vpp-dev] Question about the ipsec policy matching

> On 5 Mar 2019, at 04:25, Zhang, Yuwei1 wrote: > > Hello All, > I’m doing some investigation on ipsec in vpp recently, I noticed > that the ipsec policy matching part using a very simple linear search > algorithm which works fine in the case only have a few policy entries, but > on

Re: [vpp-dev] Build failure question

> On 4 Mar 2019, at 22:52, Thomas F Herbert wrote: > > Damjan et. al. > > I get build failures when builging from a tarball outside of git tree on > 19.01 > > I documented this in https://jira.fd.io/browse/VPP-1577 > > This is not reproduceable when bui

[vpp-dev] One question about vpp configuration file

Hello All, I noticed there's a config option in startup.conf file named scheduler-priority, from the comments, it seems related to scheduling policy about main and worker threads, could anybody give me some more detail explanation? Thanks for your kindly help. Regards, Yuwei -=-=-=-=-

[vpp-dev] Question about the ipsec policy matching

Hello All, I'm doing some investigation on ipsec in vpp recently, I noticed that the ipsec policy matching part using a very simple linear search algorithm which works fine in the case only have a few policy entries, but once the policy entries number increase, the performance should be

Re: [vpp-dev] Build failure question

On 03/04/2019 05:12 PM, Paul Vinciguerra wrote: Is this a “must have” or a “nice to have” feature?  I guess what I’m really asking is if this belongs in a CI job. This breaks the building of downstream RPMs for CentOS. Until the 1807 release, we have been maintaining this feature. The downstre

Re: [vpp-dev] Build failure question

Is this a “must have” or a “nice to have” feature? I guess what I’m really asking is if this belongs in a CI job. Paul > On Mar 4, 2019, at 4:52 PM, Thomas F Herbert wrote: > > Damjan et. al. > > I get build failures when builging from a tarball outside of git tree on > 19.01 > > I docum

[vpp-dev] Build failure question

Damjan et. al. I get build failures when builging from a tarball  outside of git tree on 19.01 I documented this in https://jira.fd.io/browse/VPP-1577 This is not reproduceable when building in git tree. Could you please take a look at the cmake output and give me some suggestions. --Tom

Re: [vpp-dev] Regarding node on a feature arc

Check out boilerplate examples of the form: vlib_buffer_t *bufs[VLIB_FRAME_SIZE], **b; u16 nexts[VLIB_FRAME_SIZE], *next; from = vlib_frame_vector_args (frame); n_left_from = frame->n_vectors; vlib_get_buffers (vm, from, bufs, n_left_from); b = bufs; next = nexts; while (n_lef

Re: [vpp-dev] NAT: no free reassembly slot

Hi Ole, -l option worked. I set it to 16 rather than the default 8 KB. I actually came to this problem while trying to figure out another issue (I don't know if it's related). I had a chance to test my VPP setup using an ixia box. For some reason, ixia test was working only in one direction (send

Re: [vpp-dev] NAT: no free reassembly slot

> Got it. > > Since I wanted to test both upstream and downstream with iperf3, I was > using -R option. > Even with disabling virtual-reassembly, packets are being dropped (see below). > > Switching server to 10.155.6.x and client on 10.155.3.x works. > So, for this kind of test, do you recommen

Re: [vpp-dev] NAT: no free reassembly slot

Hi Ole, Got it. Since I wanted to test both upstream and downstream with iperf3, I was using -R option. Even with disabling virtual-reassembly, packets are being dropped (see below). Switching server to 10.155.6.x and client on 10.155.3.x works. So, for this kind of test, do you recommend switc

Re: [vpp-dev] Regarding node on a feature arc

Hi Neale, In one of the usecases I deviated from the normal boilerplate and started getting frames to target nodes with vlib_get_frame_to_node and doing put's to those, the advantage was that I could iterate through the entire input vector and queue up elements on frames of relevant nodes and then

Re: [vpp-dev] Regarding node on a feature arc

I'll bite __ why would you want to do that? /neale -Message d'origine- De : au nom de Prashant Upadhyaya Date : lundi 4 mars 2019 à 16:06 À : "Dave Barach (dbarach)" Cc : "vpp-dev@lists.fd.io" Objet : Re: [vpp-dev] Regarding node on a feature arc Thanks Dave, this is cool !

Re: [vpp-dev] Regarding node on a feature arc

Thanks Dave, this is cool ! Regards -Prashant On Mon, Mar 4, 2019 at 8:29 PM Dave Barach (dbarach) wrote: > > You have: vlib_node_runtime_t *node. Use n = vlib_get_node(vm, > node->node_index) to recover the vlib_node_t. > > Index n->next_nodes to recover the node index corresponding to the ne

Re: [vpp-dev] Regarding node on a feature arc

You have: vlib_node_runtime_t *node. Use n = vlib_get_node(vm, node->node_index) to recover the vlib_node_t. Index n->next_nodes to recover the node index corresponding to the next index you have in mind: nNext = vlib_get_node (vm, n->next_nodes[i]) HTH... Dave -Original Message- Fr

[vpp-dev] Regarding node on a feature arc

Hi, When a node is on a feature arc, a good practice for that node is to inspect the next feature with vnet_feature_next, obtain the next0 from that and send the packets to the next0. All this works properly. My question -- how can I obtain the true vlib_node_t pointer corresponding to the next0

[vpp-dev] can't add vlan_subif

Dear VPP I'm using stable/1901 branch and vpp_api_test give me an error for adding a sub interface. This steps will help you to create the same situation: vpp_api_test vat# create_vlan_subif sw_if_index 1 vlan 2 /* I assume new interface has id 10 */ vat# delete_subif sw_if_index 10 vat# create_v