mirror of
https://github.com/fluencelabs/redis
synced 2025-03-19 09:00:51 +00:00
Put more details in the comment introduced by #4601.
This commit is contained in:
parent
1ed5ac7ce5
commit
c45366be0a
@ -64,9 +64,14 @@ int dbAsyncDelete(redisDb *db, robj *key) {
|
|||||||
robj *val = dictGetVal(de);
|
robj *val = dictGetVal(de);
|
||||||
size_t free_effort = lazyfreeGetFreeEffort(val);
|
size_t free_effort = lazyfreeGetFreeEffort(val);
|
||||||
|
|
||||||
/* If releasing the object is too much work and the refcount
|
/* If releasing the object is too much work, do it in the background
|
||||||
* is 1, that means the object really needs to be freed,
|
* by adding the object to the lazy free list.
|
||||||
* let's put it into the lazy free list. */
|
* Note that if the object is shared, to reclaim it now it is not
|
||||||
|
* possible. This rarely happens, however sometimes the implementation
|
||||||
|
* of parts of the Redis core may call incrRefCount() to protect
|
||||||
|
* objects, and then call dbDelete(). In this case we'll fall
|
||||||
|
* through and reach the dictFreeUnlinkedEntry() call, that will be
|
||||||
|
* equivalent to just calling decrRefCount(). */
|
||||||
if (free_effort > LAZYFREE_THRESHOLD && val->refcount == 1) {
|
if (free_effort > LAZYFREE_THRESHOLD && val->refcount == 1) {
|
||||||
atomicIncr(lazyfree_objects,1);
|
atomicIncr(lazyfree_objects,1);
|
||||||
bioCreateBackgroundJob(BIO_LAZY_FREE,val,NULL,NULL);
|
bioCreateBackgroundJob(BIO_LAZY_FREE,val,NULL,NULL);
|
||||||
|
Loading…
x
Reference in New Issue
Block a user