漫话Redis源码之七十七

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

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

这里主要讲位域操作,大家要对基本的位操作有深刻的理解:

/* The following set.*Bitfield and get.*Bitfield functions implement setting* and getting arbitrary size (up to 64 bits) signed and unsigned integers* at arbitrary positions into a bitmap.** The representation considers the bitmap as having the bit number 0 to be* the most significant bit of the first byte, and so forth, so for example* setting a 5 bits unsigned integer to value 23 at offset 7 into a bitmap* previously set to all zeroes, will produce the following representation:** +--------+--------+* |00000001|01110000|* +--------+--------+** When offsets and integer sizes are aligned to bytes boundaries, this is the* same as big endian, however when such alignment does not exist, its important* to also understand how the bits inside a byte are ordered.** Note that this format follows the same convention as SETBIT and related* commands.*/void setUnsignedBitfield(unsigned char *p, uint64_t offset, uint64_t bits, uint64_t value) {uint64_t byte, bit, byteval, bitval, j;for (j = 0; j < bits; j++) {bitval = (value & ((uint64_t)1<<(bits-1-j))) != 0;byte = offset >> 3;bit = 7 - (offset & 0x7);byteval = p[byte];byteval &= ~(1 << bit);byteval |= bitval << bit;p[byte] = byteval & 0xff;offset++;}
}void setSignedBitfield(unsigned char *p, uint64_t offset, uint64_t bits, int64_t value) {uint64_t uv = value; /* Casting will add UINT64_MAX + 1 if v is negative. */setUnsignedBitfield(p,offset,bits,uv);
}uint64_t getUnsignedBitfield(unsigned char *p, uint64_t offset, uint64_t bits) {uint64_t byte, bit, byteval, bitval, j, value = 0;for (j = 0; j < bits; j++) {byte = offset >> 3;bit = 7 - (offset & 0x7);byteval = p[byte];bitval = (byteval >> bit) & 1;value = (value<<1) | bitval;offset++;}return value;
}int64_t getSignedBitfield(unsigned char *p, uint64_t offset, uint64_t bits) {int64_t value;union {uint64_t u; int64_t i;} conv;/* Converting from unsigned to signed is undefined when the value does* not fit, however here we assume two's complement and the original value* was obtained from signed -> unsigned conversion, so we'll find the* most significant bit set if the original value was negative.** Note that two's complement is mandatory for exact-width types* according to the C99 standard. */conv.u = getUnsignedBitfield(p,offset,bits);value = conv.i;/* If the top significant bit is 1, propagate it to all the* higher bits for two's complement representation of signed* integers. */if (bits < 64 && (value & ((uint64_t)1 << (bits-1))))value |= ((uint64_t)-1) << bits;return value;
}/* The following two functions detect overflow of a value in the context* of storing it as an unsigned or signed integer with the specified* number of bits. The functions both take the value and a possible increment.* If no overflow could happen and the value+increment fit inside the limits,* then zero is returned, otherwise in case of overflow, 1 is returned,* otherwise in case of underflow, -1 is returned.** When non-zero is returned (overflow or underflow), if not NULL, *limit is* set to the value the operation should result when an overflow happens,* depending on the specified overflow semantics:** For BFOVERFLOW_SAT if 1 is returned, *limit it is set maximum value that* you can store in that integer. when -1 is returned, *limit is set to the* minimum value that an integer of that size can represent.** For BFOVERFLOW_WRAP *limit is set by performing the operation in order to* "wrap" around towards zero for unsigned integers, or towards the most* negative number that is possible to represent for signed integers. */#define BFOVERFLOW_WRAP 0
#define BFOVERFLOW_SAT 1
#define BFOVERFLOW_FAIL 2 /* Used by the BITFIELD command implementation. */int checkUnsignedBitfieldOverflow(uint64_t value, int64_t incr, uint64_t bits, int owtype, uint64_t *limit) {uint64_t max = (bits == 64) ? UINT64_MAX : (((uint64_t)1<<bits)-1);int64_t maxincr = max-value;int64_t minincr = -value;if (value > max || (incr > 0 && incr > maxincr)) {if (limit) {if (owtype == BFOVERFLOW_WRAP) {goto handle_wrap;} else if (owtype == BFOVERFLOW_SAT) {*limit = max;}}return 1;} else if (incr < 0 && incr < minincr) {if (limit) {if (owtype == BFOVERFLOW_WRAP) {goto handle_wrap;} else if (owtype == BFOVERFLOW_SAT) {*limit = 0;}}return -1;}return 0;handle_wrap:{uint64_t mask = ((uint64_t)-1) << bits;uint64_t res = value+incr;res &= ~mask;*limit = res;}return 1;
}int checkSignedBitfieldOverflow(int64_t value, int64_t incr, uint64_t bits, int owtype, int64_t *limit) {int64_t max = (bits == 64) ? INT64_MAX : (((int64_t)1<<(bits-1))-1);int64_t min = (-max)-1;/* Note that maxincr and minincr could overflow, but we use the values* only after checking 'value' range, so when we use it no overflow* happens. */int64_t maxincr = max-value;int64_t minincr = min-value;if (value > max || (bits != 64 && incr > maxincr) || (value >= 0 && incr > 0 && incr > maxincr)){if (limit) {if (owtype == BFOVERFLOW_WRAP) {goto handle_wrap;} else if (owtype == BFOVERFLOW_SAT) {*limit = max;}}return 1;} else if (value < min || (bits != 64 && incr < minincr) || (value < 0 && incr < 0 && incr < minincr)) {if (limit) {if (owtype == BFOVERFLOW_WRAP) {goto handle_wrap;} else if (owtype == BFOVERFLOW_SAT) {*limit = min;}}return -1;}return 0;handle_wrap:{uint64_t msb = (uint64_t)1 << (bits-1);uint64_t a = value, b = incr, c;c = a+b; /* Perform addition as unsigned so that's defined. *//* If the sign bit is set, propagate to all the higher order* bits, to cap the negative value. If it's clear, mask to* the positive integer limit. */if (bits < 64) {uint64_t mask = ((uint64_t)-1) << bits;if (c & msb) {c |= mask;} else {c &= ~mask;}}*limit = c;}return 1;
}/* Debugging function. Just show bits in the specified bitmap. Not used* but here for not having to rewrite it when debugging is needed. */
void printBits(unsigned char *p, unsigned long count) {unsigned long j, i, byte;for (j = 0; j < count; j++) {byte = p[j];for (i = 0x80; i > 0; i /= 2)printf("%c", (byte & i) ? '1' : '0');printf("|");}printf("\n");
}/* -----------------------------------------------------------------------------* Bits related string commands: GETBIT, SETBIT, BITCOUNT, BITOP.* -------------------------------------------------------------------------- */#define BITOP_AND   0
#define BITOP_OR    1
#define BITOP_XOR   2
#define BITOP_NOT   3#define BITFIELDOP_GET 0
#define BITFIELDOP_SET 1
#define BITFIELDOP_INCRBY 2/* This helper function used by GETBIT / SETBIT parses the bit offset argument* making sure an error is returned if it is negative or if it overflows* Redis 512 MB limit for the string value or more (server.proto_max_bulk_len).** If the 'hash' argument is true, and 'bits is positive, then the command* will also parse bit offsets prefixed by "#". In such a case the offset* is multiplied by 'bits'. This is useful for the BITFIELD command. */
int getBitOffsetFromArgument(client *c, robj *o, uint64_t *offset, int hash, int bits) {long long loffset;char *err = "bit offset is not an integer or out of range";char *p = o->ptr;size_t plen = sdslen(p);int usehash = 0;/* Handle #<offset> form. */if (p[0] == '#' && hash && bits > 0) usehash = 1;if (string2ll(p+usehash,plen-usehash,&loffset) == 0) {addReplyError(c,err);return C_ERR;}/* Adjust the offset by 'bits' for #<offset> form. */if (usehash) loffset *= bits;/* Limit offset to server.proto_max_bulk_len (512MB in bytes by default) */if ((loffset < 0) || (loffset >> 3) >= server.proto_max_bulk_len){addReplyError(c,err);return C_ERR;}*offset = loffset;return C_OK;
}/* This helper function for BITFIELD parses a bitfield type in the form* <sign><bits> where sign is 'u' or 'i' for unsigned and signed, and* the bits is a value between 1 and 64. However 64 bits unsigned integers* are reported as an error because of current limitations of Redis protocol* to return unsigned integer values greater than INT64_MAX.** On error C_ERR is returned and an error is sent to the client. */
int getBitfieldTypeFromArgument(client *c, robj *o, int *sign, int *bits) {char *p = o->ptr;char *err = "Invalid bitfield type. Use something like i16 u8. Note that u64 is not supported but i64 is.";long long llbits;if (p[0] == 'i') {*sign = 1;} else if (p[0] == 'u') {*sign = 0;} else {addReplyError(c,err);return C_ERR;}if ((string2ll(p+1,strlen(p+1),&llbits)) == 0 ||llbits < 1 ||(*sign == 1 && llbits > 64) ||(*sign == 0 && llbits > 63)){addReplyError(c,err);return C_ERR;}*bits = llbits;return C_OK;
}

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



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

相关文章

Redis 基本数据类型和使用详解

《Redis基本数据类型和使用详解》String是Redis最基本的数据类型,一个键对应一个值,它的功能十分强大,可以存储字符串、整数、浮点数等多种数据格式,本文给大家介绍Redis基本数据类型和... 目录一、Redis 入门介绍二、Redis 的五大基本数据类型2.1 String 类型2.2 Hash

Redis中Hash从使用过程到原理说明

《Redis中Hash从使用过程到原理说明》RedisHash结构用于存储字段-值对,适合对象数据,支持HSET、HGET等命令,采用ziplist或hashtable编码,通过渐进式rehash优化... 目录一、开篇:Hash就像超市的货架二、Hash的基本使用1. 常用命令示例2. Java操作示例三

Redis中Set结构使用过程与原理说明

《Redis中Set结构使用过程与原理说明》本文解析了RedisSet数据结构,涵盖其基本操作(如添加、查找)、集合运算(交并差)、底层实现(intset与hashtable自动切换机制)、典型应用场... 目录开篇:从购物车到Redis Set一、Redis Set的基本操作1.1 编程常用命令1.2 集

Redis中的有序集合zset从使用到原理分析

《Redis中的有序集合zset从使用到原理分析》Redis有序集合(zset)是字符串与分值的有序映射,通过跳跃表和哈希表结合实现高效有序性管理,适用于排行榜、延迟队列等场景,其时间复杂度低,内存占... 目录开篇:排行榜背后的秘密一、zset的基本使用1.1 常用命令1.2 Java客户端示例二、zse

Redis中的AOF原理及分析

《Redis中的AOF原理及分析》Redis的AOF通过记录所有写操作命令实现持久化,支持always/everysec/no三种同步策略,重写机制优化文件体积,与RDB结合可平衡数据安全与恢复效率... 目录开篇:从日记本到AOF一、AOF的基本执行流程1. 命令执行与记录2. AOF重写机制二、AOF的

Redis高性能Key-Value存储与缓存利器常见解决方案

《Redis高性能Key-Value存储与缓存利器常见解决方案》Redis是高性能内存Key-Value存储系统,支持丰富数据类型与持久化方案(RDB/AOF),本文给大家介绍Redis高性能Key-... 目录Redis:高性能Key-Value存储与缓存利器什么是Redis?为什么选择Redis?Red

java 恺撒加密/解密实现原理(附带源码)

《java恺撒加密/解密实现原理(附带源码)》本文介绍Java实现恺撒加密与解密,通过固定位移量对字母进行循环替换,保留大小写及非字母字符,由于其实现简单、易于理解,恺撒加密常被用作学习加密算法的入... 目录Java 恺撒加密/解密实现1. 项目背景与介绍2. 相关知识2.1 恺撒加密算法原理2.2 Ja

Nginx屏蔽服务器名称与版本信息方式(源码级修改)

《Nginx屏蔽服务器名称与版本信息方式(源码级修改)》本文详解如何通过源码修改Nginx1.25.4,移除Server响应头中的服务类型和版本信息,以增强安全性,需重新配置、编译、安装,升级时需重复... 目录一、背景与目的二、适用版本三、操作步骤修改源码文件四、后续操作提示五、注意事项六、总结一、背景与

Android实现图片浏览功能的示例详解(附带源码)

《Android实现图片浏览功能的示例详解(附带源码)》在许多应用中,都需要展示图片并支持用户进行浏览,本文主要为大家介绍了如何通过Android实现图片浏览功能,感兴趣的小伙伴可以跟随小编一起学习一... 目录一、项目背景详细介绍二、项目需求详细介绍三、相关技术详细介绍四、实现思路详细介绍五、完整实现代码

Redis 的 SUBSCRIBE命令详解

《Redis的SUBSCRIBE命令详解》Redis的SUBSCRIBE命令用于订阅一个或多个频道,以便接收发送到这些频道的消息,本文给大家介绍Redis的SUBSCRIBE命令,感兴趣的朋友跟随... 目录基本语法工作原理示例消息格式相关命令python 示例Redis 的 SUBSCRIBE 命令用于订