Re: [vpp-dev] Getting invalid address while doing pool_alloc_aligned with release build

Hello Everyone, As I find a document where it is mentioned that - Setting the main heap size to 4GB or more requires recompilation of the entire system with CLIB_VEC64 > 0. See …/clib/clib/vec_bootstrap.h. Can anybody please suggest the best way for setting CLIB_VEC64 in vpp 18.01 release. Than

Re: [vpp-dev] vmxnet3 devices

On Thu, Mar 7, 2019 at 12:19 PM Damjan Marion wrote: > > > On 7 Mar 2019, at 18:57, Jim Thompson wrote: > > > > On Mar 7, 2019, at 11:52 AM, Damjan Marion via Lists.Fd.Io < > dmarion=me@lists.fd.io> wrote: > > > > On 7 Mar 2019, at 18:33, Matthew Smith wrote: > > > Hi all, > > At startup, t

Re: [vpp-dev] vmxnet3 devices

> On 7 Mar 2019, at 18:57, Jim Thompson wrote: > > > >> On Mar 7, 2019, at 11:52 AM, Damjan Marion via Lists.Fd.Io >> mailto:dmarion=me@lists.fd.io>> wrote: >> >> >> >>> On 7 Mar 2019, at 18:33, Matthew Smith >> > wrote: >>> >>> >>> Hi all, >>> >>> At st

Re: [vpp-dev] vmxnet3 devices

> On Mar 7, 2019, at 11:52 AM, Damjan Marion via Lists.Fd.Io > wrote: > > > >> On 7 Mar 2019, at 18:33, Matthew Smith wrote: >> >> >> Hi all, >> >> At startup, the DPDK plugin attempts to take over most PCI network devices >> which are supported by a PMD and are not in use by the kernel

Re: [vpp-dev] vmxnet3 devices

> On 7 Mar 2019, at 18:33, Matthew Smith wrote: > > > Hi all, > > At startup, the DPDK plugin attempts to take over most PCI network devices > which are supported by a PMD and are not in use by the kernel. It seems that > vmxnet3 is an exception to this - if vmxnet3 devices are present, the

[vpp-dev] vmxnet3 devices

Hi all, At startup, the DPDK plugin attempts to take over most PCI network devices which are supported by a PMD and are not in use by the kernel. It seems that vmxnet3 is an exception to this - if vmxnet3 devices are present, they are blacklisted unless they were explicitly whitelisted in startup

Re: [vpp-dev] Fresh install shows large latency increase when using workers #vpp_stability

I can confirm that this does NOT happen in 19.01 stable -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12458): https://lists.fd.io/g/vpp-dev/message/12458 Mute This Topic: https://lists.fd.io/mt/30295958/21656 Mute #vpp_stability: https://lists.fd.i

[vpp-dev] Fresh install shows large latency increase when using workers #vpp_stability

Hi everyone, I noticed something today using v19.04-rc0, running Ubuntu 18.04 Fresh install, nothing modified, cloned straight from https://gerrit.fd.io/r/vpp Either built manually or via vpp/build-root/vagrant/build.sh, then installed non-dev and non-debug debs When NOT using workers, latency

Re: [vpp-dev] Submitting code for NAT PAP

Hi Ole, I'll see to submitting it then! Sincerely, John -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12456): https://lists.fd.io/g/vpp-dev/message/12456 Mute This Topic: https://lists.fd.io/mt/30286653/21656 Group Owner: vpp-dev+ow...@lists.fd.i

Re: [vpp-dev] Events from VPP worker thread over shared memory

> I want to send some events from VPP to client over shared memory. The trigger > for these events are being detected on my worker threads. > > Can I directly send them from the worker threads or do I need to send them to > the main thread first from where they will be forwarded over shared mem