Searched refs:napi_id (Results 1 – 4 of 4) sorted by relevance
| /memcached-1.6.32/doc/ |
| D | napi_ids.txt | 31 During a normal run, each worker thread gets associated with a napi_id and
33 napi_id is received after each thread is associated with its own napi_id
37 napi_id's associated with the threads are reset.
40 virtual interface like loopback, napi_id returned can be 0. This condition
|
| /memcached-1.6.32/ |
| D | thread.c | 715 thread->napi_id = 0; in reset_threads_napi_id()
728 int napi_id, err, i; in select_thread_by_napi_id() local
733 err = getsockopt(sfd, SOL_SOCKET, SO_INCOMING_NAPI_ID, &napi_id, &len); in select_thread_by_napi_id()
734 if ((err == -1) || (napi_id == 0)) { in select_thread_by_napi_id()
745 thread->napi_id = napi_id; in select_thread_by_napi_id()
750 if (thread->napi_id == napi_id) { in select_thread_by_napi_id()
|
| D | memcached.h | 741 int napi_id; /* napi id associated with this thread */ member
|
| D | memcached.c | 3531 int napi_id; local
3532 error = getsockopt(sfd, SOL_SOCKET, SO_INCOMING_NAPI_ID, &napi_id, &len);
|