Home
last modified time | relevance | path

Searched refs:requests (Results 1 – 25 of 193) sorted by relevance

12345678

/f-stack/freebsd/contrib/device-tree/Bindings/dma/
H A Dlpc1850-dmamux.txt11 - dma-requests: Number of DMA requests for the mux
15 - dma-requests: Number of DMA requests the controller can handle
28 dma-requests = <16>;
40 dma-requests = <64>;
H A Dti-dma-crossbar.txt9 - dma-requests: Number of DMA requests the crossbar can receive
13 - dma-requests: Number of DMA requests the controller can handle
43 dma-requests = <127>;
51 dma-requests = <205>;
H A Dmtk-uart-apdma.txt11 One interrupt per dma-requests, or 8 if no dma-requests property is present
13 - dma-requests: The number of DMA channels
50 dma-requests = <12>;
H A Dfsl-imx-dma.txt17 - #dma-requests : Number of DMA requests supported.
32 Clients have to specify the DMA requests with phandles in a list.
38 - dma-names: List of string identifiers for the DMA requests. For the correct
H A Ddma-router.yaml18 have more peripherals integrated with DMA requests than what the DMA
31 dma-requests:
45 dma-requests = <205>;
H A Dowl-dma.yaml41 dma-requests:
58 - dma-requests
75 dma-requests = <46>;
H A Darm-pl330.txt17 - dma-requests: contains the total number of DMA requests supported by the DMAC
32 #dma-requests = <32>;
H A Dzxdma.txt9 - dma-requests: virtual channels supported, each virtual channel
23 dma-requests = <24>;
H A Dk3dma.txt13 - dma-requests: virtual channels supported, each virtual channel
25 dma-requests = <27>;
H A Dowl-dma.txt12 - dma-requests: Number of DMA request signals supported by the controller.
28 dma-requests = <46>;
H A Drenesas,nbpfaxi.txt35 You can use dma-channels and dma-requests as described in dma.txt, although they
53 dma-requests = <8>;
H A Dsnps-dma.txt8 - dma-requests: Number of DMA request lines supported, up to 16
42 dma-requests = <16>;
H A Drenesas,shdma.txt20 - dma-requests: number of DMA request signals
34 dma-requests = <256>;
H A Darm-pl08x.txt25 - dma-requests: contains the total number of DMA requests supported by the DMAC
H A Dst_fdma.txt4 supporting 16 independent DMA channels. It accepts up to 32 DMA requests.
44 - dmas: Comma separated list of dma channel requests
/f-stack/app/redis-5.0.5/src/
H A Dredis-benchmark.c59 int requests; member
174 if (config.requests_finished == config.requests) { in clientDone()
244 if (config.requests_finished < config.requests) in readHandler()
267 if (config.requests_issued++ >= config.requests) { in writeHandler()
445 qsort(config.latency,config.requests,sizeof(long long),compareLatency); in showLatencyReport()
446 for (i = 0; i < config.requests; i++) { in showLatencyReport()
447 if (config.latency[i]/1000 != curlat || i == (config.requests-1)) { in showLatencyReport()
449 perc = ((float)(i+1)*100)/config.requests; in showLatencyReport()
493 config.requests = atoi(argv[++i]); in parseOptions()
660 config.requests = 100000; in main()
[all …]
/f-stack/tools/libxo/tests/core/saved/
H A Dtest_03.XP.out8 <requests>32145</requests>
H A Dtest_03.X.out1 …45</in-use><memory-use>54321</memory-use><high-use>-</high-use><requests>32145</requests></memory>…
H A Dtest_03.J.out1 …ory": [{"type":"name","in-use":12345,"memory-use":54321,"high-use":"-","requests":32145}], "employ…
H A Dtest_03.JP.out12 "requests": 32145
/f-stack/app/nginx-1.16.1/src/http/modules/
H A Dngx_http_upstream_keepalive_module.c15 ngx_uint_t requests; member
100 offsetof(ngx_http_upstream_keepalive_srv_conf_t, requests),
153 ngx_conf_init_uint_value(kcf->requests, 100); in ngx_http_upstream_init_keepalive()
324 if (c->requests >= kp->conf->requests) { in ngx_http_upstream_free_keepalive_peer()
516 conf->requests = NGX_CONF_UNSET_UINT; in ngx_http_upstream_keepalive_create_conf()
/f-stack/freebsd/contrib/device-tree/Bindings/net/
H A Dsnps,dwc-qos-ethernet.txt109 - snps,write-requests: Number of write requests that the AXI port can issue.
111 - snps,read-requests: Number of read requests that the AXI port can issue.
151 snps,write-requests = <2>;
152 snps,read-requests = <16>;
/f-stack/dpdk/lib/librte_eal/common/
H A Deal_common_proc.c98 struct pending_request_list requests; member
101 .requests = TAILQ_HEAD_INITIALIZER(pending_requests.requests),
126 TAILQ_FOREACH(r, &pending_requests.requests, next) { in find_pending_request()
504 TAILQ_REMOVE(&pending_requests.requests, req, next); in async_reply_handle_thread_unsafe()
885 TAILQ_INSERT_TAIL(&pending_requests.requests, pending_req, next); in mp_request_async()
924 TAILQ_INSERT_TAIL(&pending_requests.requests, &pending_req, next); in mp_request_sync()
933 TAILQ_REMOVE(&pending_requests.requests, &pending_req, next); in mp_request_sync()
1140 TAILQ_INSERT_TAIL(&pending_requests.requests, dummy, in rte_mp_request_async()
1184 TAILQ_INSERT_HEAD(&pending_requests.requests, dummy, next); in rte_mp_request_async()
/f-stack/dpdk/doc/guides/prog_guide/
H A Dmulti_proc_support.rst218 notification mechanism, while the two types of "requests" are meant to be a two
222 Both messages and requests will trigger a named callback on the receiver side.
256 Sending requests
270 * ``nb_sent`` - number indicating how many requests were sent (i.e. how many
276 which responses appear is undefined. When doing synchronous requests, this
279 For asynchronous requests, a function pointer to the callback function must be
293 When doing asynchronous requests, there is no need to free the resulting
323 requests (i.e. sending a request while responding to another request) is not
324 supported. However, since sending messages (not requests) does not involve an
337 messages or synchronous requests.
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/clock/
H A Dqcom,rpmcc.txt6 and accepts clock requests, aggregates the requests and turns

12345678