jiangdongzi
jiangdongzi
> 可以参考[这里](https://coostdocs.gitee.io/cn/co/coroutine/#%E5%8D%8F%E7%A8%8B%E5%8C%96) 这个文档我详细看了，一自己协程化三方网络库，二，hook，hook是全局的，总觉得不安全。而我说的这种方式，是只要可以找到异步客户端(支持回调， 就可以轻松改造成支持协程的客户端。 我试了下, 可以的
搜狗开源的workflow支持redis，mysql，kafka异步客户端，结合这个协程库，可以轻松协程化这三个客户端
@idealvin 我觉得可以调用异步客户端返回后直接yield, 以在call_back(异步客户端框架的线程中)中调用唤醒. 不过我是直接在call_back中调用了add_ready_task. 这样就集成了. 你觉得呢
> > @idealvin 我觉得可以调用异步客户端返回后直接yield, 以在call_back(异步客户端框架的线程中)中调用唤醒. 不过我是直接在call_back中调用了add_ready_task. 这样就集成了. 你觉得呢 > > 这样是可以的，可以贴下代码，看看还需要暴露哪些接口 我用add_ready_task实现啦, 目前不用暴露了. 不过如果可以封装成比如signal唤醒更合适一些.
> https://github.com/alibaba/PhotonLibOS 支持io_uring作为事件引擎和I/O引擎哦 有对比过性能么 最近在选协程库
> Note this is not the ultimate version of multi-core support, the full automatic coroutine scheduling like Golang did (also called task stealing) Does this mean at current time, one...
> > awesome, looking forwards to the full automatic coroutine scheduling enhancement like golang. > > when will this feature be available? > > The development of work-stealing has already...
> 10 to 20 nano seconds wonderful, can not believe, as I know the bthread which is a coroutine in brpc context switch time is 2~3 us..........
> BTW, we used to migrate some thread-based projects to coroutines with Photon, for example, rocksdb. No matter of std::thread, std::mutex, std::condition_variable and so on, most of the components are...
> > In our business, we hash user to specified thread via uid, every business thread has its own specified data. While coroutine maybe transfered from std::threadA to std::threadB, this...