Thanks! Got it！
/Yalei
Florin Coras 于2018年8月17日周五 上午12:00写道：
> Hi Yalei,
>
> Great! For now, I’m planning on keeping both the condvars and eventfds, at
> least until we completely understand the performance implications.
>
> As for your second question, the session layer will probably at one po
Hi Yalei,
Great! For now, I’m planning on keeping both the condvars and eventfds, at
least until we completely understand the performance implications.
As for your second question, the session layer will probably at one point start
requesting that all attachments be done over the socket trans
Thanks Florin,
It works fine now. :)
And two more questions:
1. Will eventfd replace the condvar way? it will be the default way for
event queue?
2. Will socket api replace the vpe api in the future?
Thanks!
/Yalei
Florin Coras 于2018年8月15日周三 下午11:29写道：
> Hi Yalei,
>
> You definitely need api-
Hi Yalei,
You definitely need api-socket-name /run/vpp-api.sock, don’t comment that out
:-). If that’s not enabled, you can’t exchange file descriptors.
Florin
> On Aug 15, 2018, at 5:43 AM, 汪亚雷 wrote:
>
> looks like APP not attach to the segment vpp created like /dev/shm/$pid
>
> I think
looks like APP not attach to the segment vpp created like /dev/shm/$pid
I think maybe need add the related ssvm_segment_attach in L125
in vl_api_application_attach_reply_t_handler, not sure, will test it.
wylandrea 于2018年8月15日周三 下午12:10写道：
> Thanks, Florin! I tried, but unfortunately got segm
Thanks, Florin! I tried, but unfortunately got segment fault like
below(pull from master today):
The segfault caused by the mq=0x204005440, the addr could not be refered in
APP side, looks like the address is alloc in segment_manager_init L293,
I used the example vcl.conf you provided, just co
Hi Yalei,
You have an example of how to write a vcl.conf file in vcl/vcl_test.conf. It’s
just an example, so if you want to try out eventfd, here’s what I’ve been
recently using:
vcl {
rx-fifo-size 400
tx-fifo-size 400
app-scope-local
app-scope-global
api-socket-name /run/vpp
