Please make absolutely sure that (a) you’ve compiled the tree from scratch, and (b) that you’re not tripping over previously-installed shared libraries built with a different VLIB_FRAME_SIZE.
Why are you interested in changing VLIB_FRAME_SIZE in the first place? Thanks… Dave From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Leonardo Linguaglossa Sent: Wednesday, March 8, 2017 9:11 AM To: vpp-dev@lists.fd.io Subject: [vpp-dev] [Dev question on changing the VLIB_FRAME_SIZE] Hello, I am currently working on VPP version 17.04 and I wanted to perform some measurements w.r.t. the VLIB_FRAME_SIZE, defined in VPP_ROOT/src/vlib/node.h. 1. The issue is that when I define a smaller vector size #define VLIB_FRAME_SIZE 128 I get an error in the vlib/main.c assertion: /*in vlib/main.c line 483*/ ASSERT (n_vectors_left <= VLIB_FRAME_SIZE); 2. Otherwise, if I define a bigger value #define VLIB_FRAME_SIZE 512 Then I get a different error, this time in vlib/physmem.c /*in vlib/physmem.h line 96*/ ASSERT (offset < pm->virtual.size); I would like to ask whether VPP is currently able to manage vector sizes different than 256. If not, how difficult would it be to adapt a different vector size to my vpp version? Thank you in advance, -- Leonardo
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
