Home
last modified time | relevance | path

Searched refs:background (Results 1 – 8 of 8) sorted by relevance

/memcached-1.6.32/doc/
Dnew_lru.txt22 * A background thread exists which shuffles items between/within the LRU's as
24 * The background thread can also control the lru_crawler, if enabled.
32 most item reads, largely during sets and from the background thread. Also the
33 background thread is likely to find expired items and release them back to the
Dthreads.txt5 - Some misc background threads
48 Various locks exist for background threads. They can be used to pause the
Dprotocol.txt1013 The slabs automove command enables a background thread which decides on its
1057 time. If switching from segmented to flat mode, the background thread will
1077 The LRU Crawler is an optional background thread which will walk from the tail
1085 - Enable or disable the LRU Crawler background thread.
1504 | | bool | Split LRU mode and background threads |
1517 | | | which the background thread reads from. |
DDoxyfile1225 # background. This is disabled by default, which results in a white background.
/memcached-1.6.32/
Dproxy_luafgen.c856 p->background = true; in _mcp_start_rctx_process_error()
875 p->background = true; in mcp_start_subrctx()
887 p->background = true; in mcp_start_subrctx()
1238 p->background = true; in mcplib_rcontext_wait_cond()
Dproxy.h550 bool background; // dummy IO for backgrounded awaits member
Dproto_proxy.c512 if (p->background) { in proxy_submit_cb()
DDoxyfile1477 # background. This is disabled by default, because dot on Windows does not