Home
last modified time | relevance | path

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

12345678910>>...34

/OK3568_Linux_fs/kernel/Documentation/block/
H A Dstat.rst29 read I/Os requests number of read I/Os processed
30 read merges requests number of read I/Os merged with in-queue I/O
32 read ticks milliseconds total wait time for read requests
33 write I/Os requests number of write I/Os processed
34 write merges requests number of write I/Os merged with in-queue I/O
36 write ticks milliseconds total wait time for write requests
37 in_flight requests number of I/Os currently in flight
39 time_in_queue milliseconds total wait time for all requests
40 discard I/Os requests number of discard I/Os processed
41 discard merges requests number of discard I/Os merged with in-queue I/O
[all …]
H A Dblk-mq.rst9 through queueing and submitting IO requests to block devices simultaneously,
23 involves ordering read/write requests according to the current position of the
32 The former design had a single queue to store block IO requests with a single
45 for instance), blk-mq takes action: it will store and manage IO requests to
53 layer or if we want to try to merge requests. In both cases, requests will be
56 Then, after the requests are processed by software queues, they will be placed
58 to process those requests. However, if the hardware does not have enough
59 resources to accept more requests, blk-mq will places requests on a temporary
65 The block IO subsystem adds requests in the software staging queues
73 The staging queue can be used to merge requests for adjacent sectors. For
[all …]
H A Dwriteback_cache_control.rst17 a forced cache flush, and the Force Unit Access (FUA) flag for requests.
26 guarantees that previously completed write requests are on non-volatile
58 on non-empty bios can simply be ignored, and REQ_PREFLUSH requests without
68 support required, the block layer completes empty REQ_PREFLUSH requests before
70 requests that have a payload. For devices with volatile write caches the
76 and handle empty REQ_OP_FLUSH requests in its prep_fn/request_fn. Note that
77 REQ_PREFLUSH requests with a payload are automatically turned into a sequence
84 and the driver must handle write requests that have the REQ_FUA bit set
/OK3568_Linux_fs/external/xserver/doc/
H A Dsmartsched10 client requests. The original design was simplistic; under the maximum
66 With a single client executing a stream of requests:
68 A client sends a packet of requests to the server.
74 full of requests from the client
76 The server executes requests from this buffer until it emptys,
77 in two stages -- 10 requests at a time are executed in the
78 inner Dispatch loop, a buffer full of requests are executed
80 have complete requests pending in their input queues.
84 WaitForSomething; now that the client has no requests pending,
89 With multiple clients sending streams of requests, the sequence
[all …]
/OK3568_Linux_fs/external/xserver/dix/
H A Dregistry.c44 static char ***requests, **events, **errors; variable
91 if (!double_size(&requests, nmajor, sizeof(char **))) in RegisterRequestName()
98 if (!double_size(requests + major, nminor[major], sizeof(char *))) in RegisterRequestName()
103 free(requests[major][minor]); in RegisterRequestName()
104 requests[major][minor] = name; in RegisterRequestName()
219 return requests[major][minor] ? requests[major][minor] : XREGISTRY_UNKNOWN; in LookupRequestName()
233 retval = requests[major][0]; in LookupMajorName()
300 free(requests[nmajor][--nminor[nmajor]]); in dixFreeRegistry()
301 free(requests[nmajor]); in dixFreeRegistry()
303 free(requests); in dixFreeRegistry()
[all …]
/OK3568_Linux_fs/kernel/drivers/gpu/drm/i915/gt/uc/
H A Dintel_guc_ct.c44 spin_lock_init(&ct->requests.lock); in intel_guc_ct_init_early()
45 INIT_LIST_HEAD(&ct->requests.pending); in intel_guc_ct_init_early()
46 INIT_LIST_HEAD(&ct->requests.incoming); in intel_guc_ct_init_early()
47 INIT_WORK(&ct->requests.worker, ct_incoming_request_worker_func); in intel_guc_ct_init_early()
291 return ++ct->requests.last_fence; in ct_get_next_fence()
501 spin_lock_irqsave(&ct->requests.lock, flags); in ct_send()
502 list_add_tail(&request.link, &ct->requests.pending); in ct_send()
503 spin_unlock_irqrestore(&ct->requests.lock, flags); in ct_send()
536 spin_lock_irqsave(&ct->requests.lock, flags); in ct_send()
538 spin_unlock_irqrestore(&ct->requests.lock, flags); in ct_send()
[all …]
/OK3568_Linux_fs/kernel/drivers/gpu/drm/i915/gt/
H A Dintel_gt_requests.c21 list_for_each_entry_safe(rq, rn, &tl->requests, link) in retire_requests()
31 return !list_empty(&engine->kernel_context->timeline->requests); in engine_active()
224 container_of(work, typeof(*gt), requests.retire_work.work); in retire_work_handler()
226 schedule_delayed_work(&gt->requests.retire_work, in retire_work_handler()
233 INIT_DELAYED_WORK(&gt->requests.retire_work, retire_work_handler); in intel_gt_init_requests()
238 cancel_delayed_work(&gt->requests.retire_work); in intel_gt_park_requests()
243 schedule_delayed_work(&gt->requests.retire_work, in intel_gt_unpark_requests()
250 cancel_delayed_work_sync(&gt->requests.retire_work); in intel_gt_fini_requests()
/OK3568_Linux_fs/kernel/Documentation/devicetree/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
/OK3568_Linux_fs/buildroot/package/python-requests-oauthlib/
H A DConfig.in2 bool "python-requests-oauthlib"
3 depends on BR2_PACKAGE_PYTHON3 # python-requests -> python-idna
9 https://github.com/requests/requests-oauthlib
H A Dpython-requests-oauthlib.hash1 # md5, sha256 from https://pypi.org/pypi/requests-oauthlib/json
2 md5 1ebcd55f1b1b9281940b4bc33010e2ba requests-oauthlib-1.3.0.tar.gz
3 sha256 b4261601a71fd721a8bd6d7aa1cc1d6a8a93b4a9f5e96626f8e4d91e8beeaa6a requests-oauthlib-1.3.0.t…
/OK3568_Linux_fs/yocto/meta-openembedded/meta-python/recipes-extended/python-pykickstart/files/
H A D0004-load.py-retry-to-invoke-request-with-timeout.patch23 @@ -21,12 +21,16 @@ import requests
24 from requests.auth import HTTPDigestAuth
25 from requests.auth import HTTPBasicAuth
32 from requests.exceptions import SSLError, RequestException
52 + request = requests.get(location, verify=SSL_VERIFY, timeout=2)
80 request = requests.get(location, verify=SSL_VERIFY, auth=auth)
H A D0001-support-authentication-for-kickstart.patch61 import requests
62 +from requests.auth import HTTPDigestAuth
63 +from requests.auth import HTTPBasicAuth
70 from requests.exceptions import SSLError, RequestException
99 + request = requests.get(location, verify=SSL_VERIFY)
100 + if request.status_code == requests.codes.unauthorized:
119 - request = requests.get(location, verify=SSL_VERIFY)
120 + request = requests.get(location, verify=SSL_VERIFY, auth=auth)
/OK3568_Linux_fs/kernel/Documentation/virt/kvm/
H A Dvcpu-requests.rst12 /* Check if any requests are pending for VCPU @vcpu. */
38 as possible after making the request. This means most requests
67 ensure VCPU requests are seen by VCPUs (see "Ensuring Requests Are Seen"),
88 certain VCPU requests, namely KVM_REQ_TLB_FLUSH, to wait until the VCPU
94 VCPU requests are simply bit indices of the ``vcpu->requests`` bitmap.
98 clear_bit(KVM_REQ_UNHALT & KVM_REQUEST_MASK, &vcpu->requests);
102 independent requests, all additional bits are available for architecture
103 dependent requests.
140 VCPU requests should be masked by KVM_REQUEST_MASK before using them with
150 This flag is applied to requests that only need immediate attention
[all …]
/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A Dvirtiofs.rst58 Since the virtio-fs device uses the FUSE protocol for file system requests, the
64 FUSE requests are placed into a virtqueue and processed by the host. The
71 prioritize certain requests over others. Virtqueues have queue semantics and
72 it is not possible to change the order of requests that have been enqueued.
74 impossible to add high priority requests. In order to address this difference,
75 the virtio-fs device uses a "hiprio" virtqueue specifically for requests that
76 have priority over normal requests.
/OK3568_Linux_fs/buildroot/package/python-requests/
H A Dpython-requests.hash1 # md5, sha256 from https://pypi.org/pypi/requests/json
2 md5 8c745949ad3e9ae83d9927fed213db8a requests-2.26.0.tar.gz
3 sha256 b8aa58f8cf793ffd8782d3d8cb19e66ef36f7aba4353eec859e74678b01b07a7 requests-2.26.0.tar.gz
/OK3568_Linux_fs/buildroot/package/docker-compose/
H A D0001-Strip-up-generic-versions-and-bump-requests.patch4 Subject: [PATCH] Strip up generic versions and bump requests
7 Bump the minimal `requests` to 2.20.0
26 - 'requests >= 2.6.1, != 2.11.0, != 2.12.2, != 2.18.0, < 2.21',
33 + 'requests >= 2.20.0, < 3',
/OK3568_Linux_fs/buildroot/package/python-requests-toolbelt/
H A Dpython-requests-toolbelt.hash1 # md5, sha256 from https://pypi.org/pypi/requests-toolbelt/json
2 md5 b1509735c4b4cf95df2619facbc3672e requests-toolbelt-0.9.1.tar.gz
3 sha256 968089d4584ad4ad7c171454f0a5c6dac23971e9472521ea3b6d49d610aa6fc0 requests-toolbelt-0.9.1.t…
H A DConfig.in2 bool "python-requests-toolbelt"
3 depends on BR2_PACKAGE_PYTHON3 # python-requests -> python-idna
6 A utility belt for advanced users of python-requests.
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/platform/default/mbgl/storage/
H A Doffline_download.cpp276 …while (!resourcesRemaining.empty() && requests.size() < HTTPFileSource::maximumConcurrentRequests(… in continueDownload()
285 requests.clear(); in deactivateDownload()
303 auto workRequestsIt = requests.insert(requests.begin(), nullptr); in ensureResource()
305 requests.erase(workRequestsIt); in ensureResource()
338 auto fileRequestsIt = requests.insert(requests.begin(), nullptr); in ensureResource()
345 requests.erase(fileRequestsIt); in ensureResource()
/OK3568_Linux_fs/yocto/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-requests-futures_1.0.0.bb1 SUMMARY = "Small add-on for the python requests http library. Makes use of python 3.2’s concurrent.…
2 HOMEPAGE = "https://github.com/ross/requests-futures"
12 python3-requests \
/OK3568_Linux_fs/kernel/arch/powerpc/kvm/
H A Dtrace.h106 __field( __u32, requests )
111 __entry->requests = vcpu->requests;
115 __entry->cpu_nr, __entry->requests)
/OK3568_Linux_fs/kernel/Documentation/admin-guide/device-mapper/
H A Dlog-writes.rst10 that is in the WRITE requests is copied into the log to make the replay happen
17 cache. This means that normal WRITE requests are not actually logged until the
22 This works by attaching all WRITE requests to a list once the write completes.
39 Any REQ_FUA requests bypass this flushing mechanism and are logged as soon as
40 they complete as those requests will obviously bypass the device cache.
42 Any REQ_OP_DISCARD requests are treated like WRITE requests. Otherwise we would
43 have all the DISCARD requests, and then the WRITE requests and then the FLUSH

12345678910>>...34