漫话Redis源码之八十三

2024-02-06 09:38
文章标签 源码 redis 漫话 八十三

本文主要是介绍漫话Redis源码之八十三,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

触发并掩码掉给定的fd:

static int aeApiLookupPending(aeApiState *state, int fd) {uint_t i;for (i = 0; i < state->npending; i++) {if (state->pending_fds[i] == fd)return (i);}return (-1);
}/** Helper function to invoke port_associate for the given fd and mask.*/
static int aeApiAssociate(const char *where, int portfd, int fd, int mask) {int events = 0;int rv, err;if (mask & AE_READABLE)events |= POLLIN;if (mask & AE_WRITABLE)events |= POLLOUT;if (evport_debug)fprintf(stderr, "%s: port_associate(%d, 0x%x) = ", where, fd, events);rv = port_associate(portfd, PORT_SOURCE_FD, fd, events,(void *)(uintptr_t)mask);err = errno;if (evport_debug)fprintf(stderr, "%d (%s)\n", rv, rv == 0 ? "no error" : strerror(err));if (rv == -1) {fprintf(stderr, "%s: port_associate: %s\n", where, strerror(err));if (err == EAGAIN)fprintf(stderr, "aeApiAssociate: event port limit exceeded.");}return rv;
}static int aeApiAddEvent(aeEventLoop *eventLoop, int fd, int mask) {aeApiState *state = eventLoop->apidata;int fullmask, pfd;if (evport_debug)fprintf(stderr, "aeApiAddEvent: fd %d mask 0x%x\n", fd, mask);/** Since port_associate's "events" argument replaces any existing events, we* must be sure to include whatever events are already associated when* we call port_associate() again.*/fullmask = mask | eventLoop->events[fd].mask;pfd = aeApiLookupPending(state, fd);if (pfd != -1) {/** This fd was recently returned from aeApiPoll.  It should be safe to* assume that the consumer has processed that poll event, but we play* it safer by simply updating pending_mask.  The fd will be* re-associated as usual when aeApiPoll is called again.*/if (evport_debug)fprintf(stderr, "aeApiAddEvent: adding to pending fd %d\n", fd);state->pending_masks[pfd] |= fullmask;return 0;}return (aeApiAssociate("aeApiAddEvent", state->portfd, fd, fullmask));
}static void aeApiDelEvent(aeEventLoop *eventLoop, int fd, int mask) {aeApiState *state = eventLoop->apidata;int fullmask, pfd;if (evport_debug)fprintf(stderr, "del fd %d mask 0x%x\n", fd, mask);pfd = aeApiLookupPending(state, fd);if (pfd != -1) {if (evport_debug)fprintf(stderr, "deleting event from pending fd %d\n", fd);/** This fd was just returned from aeApiPoll, so it's not currently* associated with the port.  All we need to do is update* pending_mask appropriately.*/state->pending_masks[pfd] &= ~mask;if (state->pending_masks[pfd] == AE_NONE)state->pending_fds[pfd] = -1;return;}/** The fd is currently associated with the port.  Like with the add case* above, we must look at the full mask for the file descriptor before* updating that association.  We don't have a good way of knowing what the* events are without looking into the eventLoop state directly.  We rely on* the fact that our caller has already updated the mask in the eventLoop.*/fullmask = eventLoop->events[fd].mask;if (fullmask == AE_NONE) {/** We're removing *all* events, so use port_dissociate to remove the* association completely.  Failure here indicates a bug.*/if (evport_debug)fprintf(stderr, "aeApiDelEvent: port_dissociate(%d)\n", fd);if (port_dissociate(state->portfd, PORT_SOURCE_FD, fd) != 0) {perror("aeApiDelEvent: port_dissociate");abort(); /* will not return */}} else if (aeApiAssociate("aeApiDelEvent", state->portfd, fd,fullmask) != 0) {/** ENOMEM is a potentially transient condition, but the kernel won't* generally return it unless things are really bad.  EAGAIN indicates* we've reached a resource limit, for which it doesn't make sense to* retry (counter-intuitively).  All other errors indicate a bug.  In any* of these cases, the best we can do is to abort.*/abort(); /* will not return */}
}static int aeApiPoll(aeEventLoop *eventLoop, struct timeval *tvp) {aeApiState *state = eventLoop->apidata;struct timespec timeout, *tsp;uint_t mask, i;uint_t nevents;port_event_t event[MAX_EVENT_BATCHSZ];/** If we've returned fd events before, we must re-associate them with the* port now, before calling port_get().  See the block comment at the top of* this file for an explanation of why.*/for (i = 0; i < state->npending; i++) {if (state->pending_fds[i] == -1)/* This fd has since been deleted. */continue;if (aeApiAssociate("aeApiPoll", state->portfd,state->pending_fds[i], state->pending_masks[i]) != 0) {/* See aeApiDelEvent for why this case is fatal. */abort();}state->pending_masks[i] = AE_NONE;state->pending_fds[i] = -1;}state->npending = 0;if (tvp != NULL) {timeout.tv_sec = tvp->tv_sec;timeout.tv_nsec = tvp->tv_usec * 1000;tsp = &timeout;} else {tsp = NULL;}/** port_getn can return with errno == ETIME having returned some events (!).* So if we get ETIME, we check nevents, too.*/nevents = 1;if (port_getn(state->portfd, event, MAX_EVENT_BATCHSZ, &nevents,tsp) == -1 && (errno != ETIME || nevents == 0)) {if (errno == ETIME || errno == EINTR)return 0;/* Any other error indicates a bug. */perror("aeApiPoll: port_get");abort();}state->npending = nevents;for (i = 0; i < nevents; i++) {mask = 0;if (event[i].portev_events & POLLIN)mask |= AE_READABLE;if (event[i].portev_events & POLLOUT)mask |= AE_WRITABLE;eventLoop->fired[i].fd = event[i].portev_object;eventLoop->fired[i].mask = mask;if (evport_debug)fprintf(stderr, "aeApiPoll: fd %d mask 0x%x\n",(int)event[i].portev_object, mask);state->pending_fds[i] = event[i].portev_object;state->pending_masks[i] = (uintptr_t)event[i].portev_user;}return nevents;
}static char *aeApiName(void) {return "evport";
}

这篇关于漫话Redis源码之八十三的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/683881

相关文章

Knife4j+Axios+Redis前后端分离架构下的 API 管理与会话方案(最新推荐)

《Knife4j+Axios+Redis前后端分离架构下的API管理与会话方案(最新推荐)》本文主要介绍了Swagger与Knife4j的配置要点、前后端对接方法以及分布式Session实现原理,... 目录一、Swagger 与 Knife4j 的深度理解及配置要点Knife4j 配置关键要点1.Spri

Redis出现中文乱码的问题及解决

《Redis出现中文乱码的问题及解决》:本文主要介绍Redis出现中文乱码的问题及解决,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录1. 问题的产生2China编程. 问题的解决redihttp://www.chinasem.cns数据进制问题的解决中文乱码问题解决总结

Redis的持久化之RDB和AOF机制详解

《Redis的持久化之RDB和AOF机制详解》:本文主要介绍Redis的持久化之RDB和AOF机制,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录概述RDB(Redis Database)核心原理触发方式手动触发自动触发AOF(Append-Only File)核

Redis分片集群、数据读写规则问题小结

《Redis分片集群、数据读写规则问题小结》本文介绍了Redis分片集群的原理,通过数据分片和哈希槽机制解决单机内存限制与写瓶颈问题,实现分布式存储和高并发处理,但存在通信开销大、维护复杂及对事务支持... 目录一、分片集群解android决的问题二、分片集群图解 分片集群特征如何解决的上述问题?(与哨兵模

SpringBoot连接Redis集群教程

《SpringBoot连接Redis集群教程》:本文主要介绍SpringBoot连接Redis集群教程,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录1. 依赖2. 修改配置文件3. 创建RedisClusterConfig4. 测试总结1. 依赖 <de

SpringBoot+Redis防止接口重复提交问题

《SpringBoot+Redis防止接口重复提交问题》:本文主要介绍SpringBoot+Redis防止接口重复提交问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不... 目录前言实现思路代码示例测试总结前言在项目的使用使用过程中,经常会出现某些操作在短时间内频繁提交。例

Redis 配置文件使用建议redis.conf 从入门到实战

《Redis配置文件使用建议redis.conf从入门到实战》Redis配置方式包括配置文件、命令行参数、运行时CONFIG命令,支持动态修改参数及持久化,常用项涉及端口、绑定、内存策略等,版本8... 目录一、Redis.conf 是什么?二、命令行方式传参(适用于测试)三、运行时动态修改配置(不重启服务

浅析如何保证MySQL与Redis数据一致性

《浅析如何保证MySQL与Redis数据一致性》在互联网应用中,MySQL作为持久化存储引擎,Redis作为高性能缓存层,两者的组合能有效提升系统性能,下面我们来看看如何保证两者的数据一致性吧... 目录一、数据不一致性的根源1.1 典型不一致场景1.2 关键矛盾点二、一致性保障策略2.1 基础策略:更新数

Redis Cluster模式配置

《RedisCluster模式配置》:本文主要介绍RedisCluster模式配置,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下吧... 目录分片 一、分片的本质与核心价值二、分片实现方案对比 ‌三、分片算法详解1. ‌范围分片(顺序分片)‌2. ‌哈希分片3. ‌虚

Springboot整合Redis主从实践

《Springboot整合Redis主从实践》:本文主要介绍Springboot整合Redis主从的实例,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录前言原配置现配置测试LettuceConnectionFactory.setShareNativeConnect