[vpp-dev] IS THERE ANY SETUP FOR BUILDING AND TESTING ALL THE FD.IO MODULES TOGETHER

Hello all, I am a newbie to fd.io. I have started with setting up dev environment by following this link https://wiki.fd.io/view/VPP/Setting_Up_Your_Dev_Environment . This setup is building only VPP libs. (so I was considering it as a VPP setup and not a FD.IO setup) IS THERE ANY SETUP FOR BUIL

[vpp-dev] multi-threaded application, "epoll_wait" and "epoll_ctl" have "received signal SIGABRT, Aborted".

Hello all, I am a newbie to VPP. I am trying to run VPP with a multi-threaded application. "recv" works fine from non-main threads, whereas "epoll_wait" and "epoll_ctl" have "received signal SIGABRT, Aborted". Is this a known issue? Or am I doing something wrong? Attaching backtrace for "epol

Re: [vpp-dev] multi-threaded application, "epoll_wait" and "epoll_ctl" have "received signal SIGABRT, Aborted".

n the PDT time zone, so don’t > expect to hear from him for a few hours. > > D. > > *From:* vpp-dev@lists.fd.io *On Behalf Of *sharath > kumar > *Sent:* Friday, March 29, 2019 12:18 AM > *To:* vpp-dev@lists.fd.io; csit-...@lists.fd.io > *Subject:* [vpp-dev] multi-threaded appli

Re: [vpp-dev] multi-threaded application, "epoll_wait" and "epoll_ctl" have "received signal SIGABRT, Aborted".

ns the rest of the threads do only io work. > > If all the threads must handle async communication via epoll/select, then > they should register themselves as workers with vcl and get their own epoll > fd. LDP does not support that. > > Florin > > On Mar 29, 2019, at 12:13 P