https://blog.csdn.net/stallion5632zh-cnhttps://blog.csdn.net/https://blog.csdn.net/stallion5632/article/details/166140289https://blog.csdn.net/stallion5632/article/details/166140289stallion5632Sun, 20 Sep 2026 20:29:03 +0800https://blog.csdn.net/stallion5632/article/details/166134526https://blog.csdn.net/stallion5632/article/details/166134526stallion5632Sun, 20 Sep 2026 15:50:11 +0800https://blog.csdn.net/stallion5632/article/details/166102735https://blog.csdn.net/stallion5632/article/details/166102735stallion5632Sun, 20 Sep 2026 09:44:54 +0800https://blog.csdn.net/stallion5632/article/details/165885628https://blog.csdn.net/stallion5632/article/details/165885628stallion5632Fri, 18 Sep 2026 16:55:50 +0800https://blog.csdn.net/stallion5632/article/details/165884013https://blog.csdn.net/stallion5632/article/details/165884013stallion5632Fri, 18 Sep 2026 16:17:00 +0800https://blog.csdn.net/stallion5632/article/details/165617577https://blog.csdn.net/stallion5632/article/details/165617577stallion5632Wed, 16 Sep 2026 15:54:54 +0800https://blog.csdn.net/stallion5632/article/details/165613846https://blog.csdn.net/stallion5632/article/details/165613846stallion5632Wed, 16 Sep 2026 14:57:34 +0800https://blog.csdn.net/stallion5632/article/details/165458966https://blog.csdn.net/stallion5632/article/details/165458966stallion5632Tue, 15 Sep 2026 11:43:16 +0800https://blog.csdn.net/stallion5632/article/details/165290385https://blog.csdn.net/stallion5632/article/details/165290385stallion5632Mon, 14 Sep 2026 10:27:51 +0800https://blog.csdn.net/stallion5632/article/details/165245142https://blog.csdn.net/stallion5632/article/details/165245142stallion5632Mon, 14 Sep 2026 00:10:41 +0800https://blog.csdn.net/stallion5632/article/details/165009063https://blog.csdn.net/stallion5632/article/details/165009063stallion5632Sat, 12 Sep 2026 00:07:23 +0800https://blog.csdn.net/stallion5632/article/details/164993390https://blog.csdn.net/stallion5632/article/details/164993390stallion5632Fri, 11 Sep 2026 14:43:30 +0800https://blog.csdn.net/stallion5632/article/details/164835803https://blog.csdn.net/stallion5632/article/details/164835803stallion5632Thu, 10 Sep 2026 13:28:35 +0800https://blog.csdn.net/stallion5632/article/details/164818078https://blog.csdn.net/stallion5632/article/details/164818078stallion5632Thu, 10 Sep 2026 11:12:41 +0800https://blog.csdn.net/stallion5632/article/details/164815930https://blog.csdn.net/stallion5632/article/details/164815930stallion5632Thu, 10 Sep 2026 10:51:19 +0800https://blog.csdn.net/stallion5632/article/details/164803749https://blog.csdn.net/stallion5632/article/details/164803749stallion5632Thu, 10 Sep 2026 09:04:54 +0800`）处理流程差异，无状态策略（`EventPoolhttps://blog.csdn.net/stallion5632/article/details/164758605https://blog.csdn.net/stallion5632/article/details/164758605stallion5632Thu, 10 Sep 2026 00:34:59 +0800https://blog.csdn.net/stallion5632/article/details/164593464https://blog.csdn.net/stallion5632/article/details/164593464stallion5632Tue, 08 Sep 2026 11:45:42 +0800 libev 是一个单线程的事件循环库（Reactor 模式）。使用时把要等待的事件——文件描述符可读、定时器到期、跨线程通知——注册进去，事件发生后由库调用回调函数处理。在嵌入式系统中，它可以作为一个 RT-Thread 线程运行，STM32F407 上已用 select 后端验证了 ev_io、ev_timer、ev_async 三种用法；它也可以承接中断处理中的耗时部分。是否引入 libev，取决于两点：数据来源能不能映射成文件描述符（fd），以及模块自身是否已经有一套完整的并发处理机制。]]>https://blog.csdn.net/stallion5632/article/details/164115833https://blog.csdn.net/stallion5632/article/details/164115833stallion5632Thu, 27 Aug 2026 13:00:56 +0800https://blog.csdn.net/stallion5632/article/details/164045426https://blog.csdn.net/stallion5632/article/details/164045426stallion5632Tue, 25 Aug 2026 09:47:21 +0800