Seems like my patch https://gerrit.fd.io/r/#/c/13013/
broke the verification job. I provided a fix, but for some strange reason it
seems like the verifiy build is stuck with the broken version of the vpp_papi
package.
This problem seems to persist even after I reverted 13013 with
https://gerrit.
See also vec_capacity(x), vec_len(x) * sizeof (x[0)), vec_new (type,nitems),
and so forth.
If you force the vector infra to repeatedly copy [gb worth of] data, it will
take time.
D.
From: vpp-dev@lists.fd.io On Behalf Of
david.leitch@gmail.com
Sent: Monday, June 18, 2018 8:23 AM
To: vpp-
Hi dave
I am using 64 bit image ( -DCLIB_VEC64=1 ) and as I said, I can get vectors
with large size (more than 5GB)
My problem is not the size of vector it is time delay for allocation.
when I using vec_validate to allocate huge memory size it has a very very long
delay to response,
I don't ge
In a 32-bit vector length image – as in standard vpp – vectors are limited to
4g elements. That includes the main heap, which is a u8 * vector.
You’ll never manage to allocate a single vector larger than a significant
fraction of 4gb.
Of course, you can mmap private memory of some arbitrary siz
Hi,
I have a problem when using *vec_validate* to allocate large memory size ( more
than 5G ) , I am sure that i have enough memory on my system,
but vec_validate take so long time to allocate memory how can i decrease this
delay time for allocate memory and how can calculate memory size
before
