gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

fix typo (#1136)

Browse Source 
Signed-off-by: chx9 <cheng.huan@icloud.com>
This commit is contained in:
chx9 2024-10-08 23:07:51 +08:00 committed by GitHub
parent e617bf2ddc
commit cba8eaf4c9
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/object.c
View File

@ -1416,7 +1416,7 @@ int objectSetLRUOrLFU(robj *val, long long lfu_freq, long long lru_idle, long lo
lru_idle = lru_idle * lru_multiplier / LRU_CLOCK_RESOLUTION; lru_idle = lru_idle * lru_multiplier / LRU_CLOCK_RESOLUTION;
long lru_abs = lru_clock - lru_idle; /* Absolute access time. */ long lru_abs = lru_clock - lru_idle; /* Absolute access time. */
/* If the LRU field underflows (since lru_clock is a wrapping clock), /* If the LRU field underflows (since lru_clock is a wrapping clock),
* we need to make it positive again. This be handled by the unwrapping * we need to make it positive again. This will be handled by the unwrapping
* code in estimateObjectIdleTime. I.e. imagine a day when lru_clock * code in estimateObjectIdleTime. I.e. imagine a day when lru_clock
* wrap arounds (happens once in some 6 months), and becomes a low * wrap arounds (happens once in some 6 months), and becomes a low
* value, like 10, an lru_idle of 1000 should be near LRU_CLOCK_MAX. */ * value, like 10, an lru_idle of 1000 should be near LRU_CLOCK_MAX. */