Home
last modified time | relevance | path

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

12345678910>>...38

/openbmc/linux/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
/openbmc/openbmc-tools/openbmctool/
H A Dopenbmctool.py18 import requests
122 except(requests.exceptions.Timeout):
125 except(requests.exceptions.ConnectionError) as err:
129 mysess = requests.session()
406 except(requests.exceptions.Timeout):
409 except(requests.exceptions.ConnectionError) as err:
433 mysess = requests.session()
460 except(requests.exceptions.Timeout):
462 except(requests.exceptions.ConnectionError) as err:
478 except(requests.exceptions.Timeout):
[all …]
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-requests-toolbelt/
H A D720240501dca0b4eacc3295665d7ced8719e11d2.patch6 Upstream-Status: Submitted [https://github.com/requests/toolbelt/pull/356]
33 - "User-Agent": "python-requests/2.8.1"
44 + "python-requests/2.28.1"
103 - "User-Agent": "python-requests/2.8.1"
114 + "python-requests/2.28.1"
173 - "User-Agent": "python-requests/2.8.1"
184 + "python-requests/2.28.1"
243 - "User-Agent": "python-requests/2.8.1"
254 + "python-requests/2.28.1"
313 - "User-Agent": "python-requests/2.8.1"
[all …]
/openbmc/linux/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 Dfsl-imx-dma.txt18 - dma-requests : Number of DMA requests supported.
19 - #dma-requests : deprecated
34 Clients have to specify the DMA requests with phandles in a list.
40 - dma-names: List of string identifiers for the DMA requests. For the correct
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>;
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-requests-unixsocket_0.3.0.bb1 SUMMARY = "Use requests to talk HTTP via a UNIX domain socket"
2 HOMEPAGE = "https://pypi.org/project/requests-unixsocket/"
8 PYPI_PACKAGE = "requests-unixsocket"
14 RDEPENDS:${PN} = "python3-requests python3-urllib3"
H A Dpython3-requests-futures_1.0.1.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"
11 python3-requests \
/openbmc/linux/Documentation/virt/acrn/
H A Dio-request.rst14 For each User VM, there is a shared 4-KByte memory region used for I/O requests
26 An I/O client is responsible for handling User VM I/O requests whose accessed
29 default client, that handles all I/O requests that do not fit into the range of
33 Below illustration shows the relationship between I/O requests shared buffer,
34 I/O requests and I/O clients.
84 4. Processing flow of I/O requests
91 c. The upcall handler schedules a worker to dispatch I/O requests.
92 d. The worker looks for the PENDING I/O requests, assigns them to different
95 e. The notified client handles the assigned I/O requests.
96 f. The HSM updates I/O requests states to COMPLETE and notifies the hypervisor
/openbmc/linux/drivers/gpu/drm/i915/gt/uc/
H A Dintel_guc_ct.c117 spin_lock_init(&ct->requests.lock); in intel_guc_ct_init_early()
118 INIT_LIST_HEAD(&ct->requests.pending); in intel_guc_ct_init_early()
119 INIT_LIST_HEAD(&ct->requests.incoming); in intel_guc_ct_init_early()
123 INIT_WORK(&ct->requests.worker, ct_incoming_request_worker_func); in intel_guc_ct_init_early()
382 unsigned int lost = fence % ARRAY_SIZE(ct->requests.lost_and_found); in ct_track_lost_and_found()
390 ct->requests.lost_and_found[lost].stack = stack_depot_save(entries, n, GFP_NOWAIT); in ct_track_lost_and_found()
392 ct->requests.lost_and_found[lost].fence = fence; in ct_track_lost_and_found()
393 ct->requests.lost_and_found[lost].action = action; in ct_track_lost_and_found()
400 return ++ct->requests.last_fence; in ct_get_next_fence()
740 spin_lock(&ct->requests.lock); in ct_send()
[all …]
/openbmc/linux/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()
208 container_of(work, typeof(*gt), requests.retire_work.work); in retire_work_handler()
210 queue_delayed_work(gt->i915->unordered_wq, &gt->requests.retire_work, in retire_work_handler()
217 INIT_DELAYED_WORK(&gt->requests.retire_work, retire_work_handler); in intel_gt_init_requests()
222 cancel_delayed_work(&gt->requests.retire_work); in intel_gt_park_requests()
227 queue_delayed_work(gt->i915->unordered_wq, &gt->requests.retire_work, in intel_gt_unpark_requests()
234 cancel_delayed_work_sync(&gt->requests.retire_work); in intel_gt_fini_requests()
/openbmc/qemu/backends/
H A Drng.c37 QSIMPLEQ_INSERT_TAIL(&s->requests, req, next); in rng_backend_request_entropy()
75 QSIMPLEQ_FOREACH_SAFE(req, &s->requests, next, next) { in rng_backend_free_requests()
79 QSIMPLEQ_INIT(&s->requests); in rng_backend_free_requests()
84 QSIMPLEQ_REMOVE(&s->requests, req, RngRequest, next); in rng_backend_finalize_request()
92 QSIMPLEQ_INIT(&s->requests); in rng_backend_init()
/openbmc/openbmc-test-automation/lib/
H A Dredfish_plus.py11 import requests
188 response = requests.get(
204 response = requests.post(
219 response = requests.patch(
233 response = requests.delete(
247 response = requests.put(
262 response = requests.head(
H A Dredfish_request.py8 import requests
97 requests.packages.urllib3.disable_warnings(
143 response = requests.get(
192 response = requests.patch(
241 response = requests.post(
299 response = requests.put(
355 response = requests.delete(
/openbmc/linux/Documentation/virt/kvm/
H A Dvcpu-requests.rst14 /* Check if any requests are pending for VCPU @vcpu. */
40 as possible after making the request. This means most requests
69 ensure VCPU requests are seen by VCPUs (see "Ensuring Requests Are Seen"),
90 certain VCPU requests, namely KVM_REQ_TLB_FLUSH, to wait until the VCPU
96 VCPU requests are simply bit indices of the ``vcpu->requests`` bitmap.
100 clear_bit(KVM_REQ_UNBLOCK & KVM_REQUEST_MASK, &vcpu->requests);
104 independent requests; all additional bits are available for architecture
105 dependent requests.
142 VCPU requests should be masked by KVM_REQUEST_MASK before using them with
152 This flag is applied to requests that only need immediate attention
[all …]
/openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-pykickstart/files/
H A D0001-support-authentication-for-kickstart.patch60 import requests
61 +from requests.auth import HTTPDigestAuth
62 +from requests.auth import HTTPBasicAuth
68 from requests.exceptions import SSLError, RequestException
96 + request = requests.get(location, verify=SSL_VERIFY)
97 + if request.status_code == requests.codes.unauthorized:
117 - request = requests.get(location, verify=SSL_VERIFY)
118 + request = requests.get(location, verify=SSL_VERIFY, auth=auth)
H A D0004-load.py-retry-to-invoke-request-with-timeout.patch23 import requests
24 from requests.auth import HTTPDigestAuth
25 from requests.auth import HTTPBasicAuth
31 from requests.exceptions import SSLError, RequestException
51 + request = requests.get(location, verify=SSL_VERIFY, timeout=2)
/openbmc/linux/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.
/openbmc/linux/arch/powerpc/kvm/
H A Dtrace.h106 __field( __u32, requests )
111 __entry->requests = vcpu->requests;
115 __entry->cpu_nr, __entry->requests)
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-bus-xen-backend39 Number of flush requests from the frontend.
46 Number of requests delayed because the backend was too
47 busy processing previous requests.
54 Number of read requests from the frontend.
68 Number of write requests from the frontend.
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-scsi_tape33 The number of I/O requests issued to the tape drive other
34 than SCSI read/write requests.
54 Shows the total number of read requests issued to the tape
65 read I/O requests to complete.
85 Shows the total number of write requests issued to the tape
96 write I/O requests to complete.
/openbmc/linux/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
/openbmc/linux/Documentation/scsi/
H A Dhptiop.rst110 All queued requests are handled via inbound/outbound queue port.
125 - Post the packet to IOP by writing it to inbound queue. For requests
127 requests allocated in host memory, write (0x80000000|(bus_addr>>5))
134 For requests allocated in IOP memory, the request offset is posted to
137 For requests allocated in host memory, (0x80000000|(bus_addr>>5))
144 For requests allocated in IOP memory, the host driver free the request
147 Non-queued requests (reset/flush etc) can be sent via inbound message
155 All queued requests are handled via inbound/outbound list.
169 round to 0 if the index reaches the supported count of requests.
186 Non-queued requests (reset communication/reset/flush etc) can be sent via PCIe

12345678910>>...38