Re: About describe doubt for libev release ..

2020-03-29 Thread CandyMi
My personal reason for replying to your email so late! I am very sorry. Thank you for pointing out the problem of the mail format. Currently I use a browser to send mail. This format is likely to cause special characters to escape. I think I will try to improve it. --- I simulated the ev_once

Re: About describe doubt for libev release ..

2020-03-22 Thread Marc Lehmann
On Mon, Mar 23, 2020 at 02:44:58AM +0800, CandyMi <869646...@qq.com> wrote: > "While other data structures are possible and I vaguely plan some minor > optimisations" > > I'm very happy to hear what you said! Because every optimization of > Timer makes it easy for developers to use without

Re: About describe doubt for libev release ..

2020-03-22 Thread CandyMi
"While other data structures are possible and I vaguely plan some minor optimisations" I'm very happy to hear what you said! Because every optimization of Timer makes it easy for developers to use without having to hold hands in some cases (I wrote a lot of code for this). I mentioned in

Re: About describe doubt for libev release ..

2020-03-22 Thread Marc Lehmann
On Sun, Mar 22, 2020 at 12:56:16PM +0800, CandyMi <869646...@qq.com> wrote: > I have the same opinion about Linux aio and io_uring. The performance of aio > is not as good and problematic as described, but the use of io_uring may be > limited by the version of the Linux kernel and it makes me

Re: About describe doubt for libev release ..

2020-03-21 Thread CandyMi
thank you for your reply. I have the same opinion about Linux aio and io_uring. The performance of aio is not as good and problematic as described, but the use of io_uring may be limited by the version of the Linux kernel and it makes me hesitant. There may be very few people who follow up

Re: About describe doubt for libev release ..

2020-03-21 Thread Marc Lehmann
> 1. "the documentation wrongly claimed that user may modify fd > and eventsmembers in io watchers when the watcher was stopped." means: > Can't modify internal members even if I/O watcher has been stopped? Yes - you have to use ev_io_set or the new ev_io_modify, direct modification does not