Searched refs:multi_socket (Results 1 – 13 of 13) sorted by relevance
| /external/ltp/testcases/kernel/power_management/ |
| D | runpwtests_exclusive04.sh | 33 multi_socket=$(is_multi_socket)
34 if [ $hyper_threaded -ne 0 -o $multi_socket -ne 0 ]; then
|
| D | runpwtests_exclusive02.sh | 35 multi_socket=$(is_multi_socket)
37 if [ $hyper_threaded -ne 0 -o $multi_socket -ne 0 \
|
| D | runpwtests01.sh | 53 multi_socket=$(is_multi_socket)
59 if [ $multi_socket -ne 0 -a $multi_core -ne 0 ] ; then
|
| D | runpwtests_exclusive03.sh | 36 multi_socket=$(is_multi_socket)
38 if [ $multi_socket -ne 0 -o $multi_core -ne 0 -o \
|
| D | runpwtests_exclusive05.sh | 36 multi_socket=$(is_multi_socket)
38 if [ $multi_socket -ne 0 -o $multi_core -ne 0 -o \
|
| D | runpwtests_exclusive01.sh | 36 multi_socket=$(is_multi_socket)
38 if [ $multi_socket -ne 0 -o $multi_core -ne 0 -o \
|
| /external/curl/tests/data/ |
| D | test530 | 37 multi_socket interface transfer with callbacks returning error
|
| /external/curl/tests/ |
| D | valgrind.supp | 64 fun:multi_socket
|
| /external/curl/docs/libcurl/ |
| D | curl_multi_timeout.md | 44 An application that uses the *multi_socket* API should not use this function.
|
| D | libcurl-multi.md | 59 the event based one we call multi_socket. You benefit from reading through the
141 The multi_socket API is designed to inform your application about which
|
| D | libcurl-tutorial.md | 1359 interface. The event based one, also called multi_socket and the "normal one"
1361 on the multi_socket event based API, this description here is for the select()
|
| /external/curl/lib/ |
| D | multi.c | 3274 static CURLMcode multi_socket(struct Curl_multi *multi, function
3468 return multi_socket(multi, FALSE, s, 0, running_handles);
3477 return multi_socket(multi, FALSE, s, ev_bitmask, running_handles);
3485 return multi_socket(multi, TRUE, CURL_SOCKET_BAD, 0, running_handles);
|
| /external/curl/docs/ |
| D | TODO | 513 The multi_socket API should work with edge-triggered socket events. One of
|