Re: 答复: libprocess libevent backend

2018-05-06 Thread Benjamin Mahler
er [mailto:bmah...@apache.org] > 发送时间: 2018年5月4日 11:47 > 收件人: Joris Van Remoortere ; > dev@mesos.apache.org > 主题: Re: libprocess libevent backend > > +Joris > > Wow, Joris do you know why this is disabled? What were the issues? > > Suteng, can you file a JIRA ticket? >

答复: libprocess libevent backend

2018-05-03 Thread Suteng
Create an issue https://issues.apache.org/jira/browse/MESOS-8881 -邮件原件- 发件人: Benjamin Mahler [mailto:bmah...@apache.org] 发送时间: 2018年5月4日 11:47 收件人: Joris Van Remoortere ; dev@mesos.apache.org 主题: Re: libprocess libevent backend +Joris Wow, Joris do you know why this is disabled? What

Re: libprocess libevent backend

2018-05-03 Thread Benjamin Mahler
- > 发件人: Benjamin Mahler [mailto:bmah...@apache.org] > 发送时间: 2018年5月4日 3:33 > 收件人: dev > 主题: Re: libprocess libevent backend > > Which issue are you referring to? > > Libprocess uses libev by default, with --enable-libevent as a configure > option to use libevent instead. Bo

答复: libprocess libevent backend

2018-05-03 Thread Suteng
new(); 209 event_config_avoid_method(config, "epoll"); -邮件原件- 发件人: Benjamin Mahler [mailto:bmah...@apache.org] 发送时间: 2018年5月4日 3:33 收件人: dev 主题: Re: libprocess libevent backend Which issue are you referring to? Libprocess uses libev by default, with --enable-libevent as a conf

Re: libprocess libevent backend

2018-05-03 Thread Benjamin Mahler
Which issue are you referring to? Libprocess uses libev by default, with --enable-libevent as a configure option to use libevent instead. Both of these backends should use epoll if the system has it available. Are you seeing otherwise? On Thu, May 3, 2018 at 6:15 AM, Suteng wrote: > libprocess

libprocess libevent backend

2018-05-03 Thread Suteng
libprocess uie poll as libevent backend, can change to epoll to improve performance ? There is a TODO issue, is resolved? [cid:image001.png@01D3E323.E3736F30] Thanks, SU Teng [cid:image002.png@01D3E323.E3736F30] Su Teng 00241668 Distributed and Parallel Software Lab Huawei Technologies Co.