| /f-stack/app/redis-5.0.5/deps/hiredis/ |
| H A D | test.c | 587 redisReply **replies; in test_throughput() local
600 assert(replies[i] != NULL && replies[i]->type == REDIS_REPLY_STATUS); in test_throughput()
604 free(replies); in test_throughput()
611 assert(replies[i] != NULL && replies[i]->type == REDIS_REPLY_ARRAY); in test_throughput()
612 assert(replies[i] != NULL && replies[i]->elements == 500); in test_throughput()
616 free(replies); in test_throughput()
626 assert(replies[i] != NULL && replies[i]->type == REDIS_REPLY_STATUS); in test_throughput()
630 free(replies); in test_throughput()
639 assert(replies[i] != NULL && replies[i]->type == REDIS_REPLY_ARRAY); in test_throughput()
640 assert(replies[i] != NULL && replies[i]->elements == 500); in test_throughput()
[all …]
|
| H A D | async.c | 133 ac->replies.head = NULL; in redisAsyncInitialize()
134 ac->replies.tail = NULL; in redisAsyncInitialize()
282 while (__redisShiftCallback(&ac->replies,&cb) == REDIS_OK) in __redisAsyncFree()
339 assert(__redisShiftCallback(&ac->replies,NULL) == REDIS_ERR); in __redisAsyncDisconnect()
360 if (!(c->flags & REDIS_IN_CALLBACK) && ac->replies.head == NULL) in redisAsyncDisconnect()
422 && ac->replies.head == NULL) { in redisProcessCallbacks()
429 __redisPushCallback(&ac->replies,&cb); in redisProcessCallbacks()
439 if (__redisShiftCallback(&ac->replies,&cb) != REDIS_OK) { in redisProcessCallbacks()
632 __redisPushCallback(&ac->replies,&cb); in __redisAsyncCommand()
639 __redisPushCallback(&ac->replies,&cb); in __redisAsyncCommand()
|
| H A D | async.h | 93 redisCallbackList replies; member
|
| H A D | README.md | 14 Apart from supporting sending commands and receiving replies, it comes with
101 ### Using replies
109 The standard replies that `redisCommand` are of the type `redisReply`. The
140 free the sub replies (it is actually harmful and will corrupt the memory).
142 **Important:** the current version of hiredis (0.10.0) frees replies when the
198 subsequent replies. The return value for this function is either `REDIS_OK` or `REDIS_ERR`, where
329 have been written to the socket, their respective replies have been read and their respective
370 ### Customizing replies
|
| H A D | CHANGELOG.md | 52 * Prevent crash on pending replies in async code (Thanks, @switch-st)
|
| /f-stack/freebsd/netinet/libalias/ |
| H A D | HISTORY | 139 - Added support to alias 227 replies, allows aliasing for
|
| /f-stack/dpdk/drivers/net/memif/ |
| H A D | rte_eth_memif.c | 131 struct rte_mp_reply replies; in memif_mp_request_regions() local
153 ret = rte_mp_request_sync(&msg, &replies, &timeout); in memif_mp_request_regions()
154 if (ret < 0 || replies.nb_received != 1) { in memif_mp_request_regions()
160 reply = &replies.msgs[0]; in memif_mp_request_regions()
|
| /f-stack/dpdk/drivers/net/tap/ |
| H A D | rte_eth_tap.c | 2312 struct rte_mp_reply replies; in tap_mp_attach_queues() local
2325 ret = rte_mp_request_sync(&request, &replies, &timeout); in tap_mp_attach_queues()
2326 if (ret < 0 || replies.nb_received != 1) { in tap_mp_attach_queues()
2331 reply = &replies.msgs[0]; in tap_mp_attach_queues()
|
| /f-stack/app/redis-5.0.5/tests/unit/ |
| H A D | scripting.tcl | 2 test {EVAL - Does Lua interpreter replies to our requests?} {
|
| /f-stack/app/redis-5.0.5/src/ |
| H A D | redis-cli.c | 6046 long long errors = 0, replies = 0, obuf_len = 0, obuf_pos = 0; in pipeMode() local
6109 replies--; in pipeMode()
6112 replies++; in pipeMode()
6192 printf("errors: %lld, replies: %lld\n", errors, replies); in pipeMode()
|
| H A D | sentinel.c | 1009 redisCallbackList *callbacks = &link->cc->replies; in releaseInstanceLink()
|
| /f-stack/app/redis-5.0.5/ |
| H A D | README.md | 274 * `reply` and `buf` are dynamic and static buffers that accumulate the replies the server sends to …
|
| H A D | 00-RELEASENOTES | 720 Redis 5 changelog: don't expect Lua replies to be ordered.
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_2_1.rst | 428 Fixed issue where in the ``icmpecho`` forwarding mode, ARP replies from
|
| /f-stack/dpdk/doc/guides/testpmd_app_ug/ |
| H A D | testpmd_funcs.rst | 341 …eceives a burst of packets, lookup for ICMP echo requests and, if any, send back ICMP echo replies.
|