Home
last modified time | relevance | path

Searched refs:requests (Results 1 – 200 of 300) sorted by relevance

12

/linux-4.4.14/Documentation/block/
Dstat.txt23 read I/Os requests number of read I/Os processed
24 read merges requests number of read I/Os merged with in-queue I/O
26 read ticks milliseconds total wait time for read requests
27 write I/Os requests number of write I/Os processed
28 write merges requests number of write I/Os merged with in-queue I/O
30 write ticks milliseconds total wait time for write requests
31 in_flight requests number of I/Os currently in flight
33 time_in_queue milliseconds total wait time for all requests
57 These values count the number of milliseconds that I/O requests have
58 waited on this block device. If there are multiple I/O requests waiting,
[all …]
Dwriteback_cache_control.txt17 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_FLUSH requests without
68 support required, the block layer completes empty REQ_FLUSH requests before
70 requests that have a payload. For devices with volatile write caches the
76 and handle empty REQ_FLUSH requests in its prep_fn/request_fn. Note that
77 REQ_FLUSH 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
Dcfq-iosched.txt5 I/O bandwidth for all the processes which requests an I/O operation.
8 operation(synchronous requests). In case of asynchronous requests, all the
9 requests from all the processes are batched together according to their
45 This parameter allows the scheduler to anticipate requests in the "backward"
53 request, then the seeking cost of two requests is considered equivalent.
60 This parameter is used to set the timeout of asynchronous requests. Default
65 This parameter is used to set the timeout of synchronous requests. Default
66 value of this is 124ms. In case to favor synchronous requests over asynchronous
78 Not idling on individual queues in the group will dispatch requests from
98 latency mode is enabled. It will ensure that sync requests have an estimated
[all …]
Ddeadline-iosched.txt33 fifo_batch (number of requests)
39 maximum number of requests per batch.
50 When we have to move requests from the io scheduler queue to the block
67 front merge requests. Setting front_merges to 0 disables this functionality.
Dbiodoc.txt172 by default copyin/out i/o requests on high-memory buffers to low-memory buffers
221 routine on its own to bounce highmem i/o to low memory for specific requests
267 requests in the queue. For example it allows reads for bringing in an
269 requests which haven't aged too much on the queue. Potentially this priority
272 requests. Some bits in the bi_rw flags field in the bio structure are
290 for specially crafted requests which such ioctl or diagnostics
292 can instead be used to directly insert such requests in the queue or preferably
318 handling direct requests easier for such drivers; Also for drivers that
346 It can help to pre-build device commands for requests in advance.
351 (The prepare function would not be called for requests that have REQ_DONTPREP
[all …]
Dqueue-sysfs.txt29 requests issued to the device must not exceed this limit. A discard_max_bytes
88 merging requests in the block layer. By default (0) all merges are
95 This controls how many requests may be allocated in the block layer for
96 read or write requests. Note that the total allocated number may be twice
Dnull_blk.txt18 - Bio-based. IO requests are submitted directly to the device driver.
/linux-4.4.14/Documentation/devicetree/bindings/dma/
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>;
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
39 dma-requests = <127>;
47 dma-requests = <205>;
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
Ddma.txt17 - dma-requests: Number of DMA request signals supported by the
31 dma-requests = <127>;
38 integrated with DMA requests than what the DMA controller can handle directly.
48 - dma-requests: Number of incoming request lines the router can handle.
50 - dma-requests: The router driver might need to look for this in order
58 dma-requests = <205>;
Darm-pl330.txt17 - dma-requests: contains the total number of DMA requests supported by the DMAC
27 #dma-requests = <32>;
Dzxdma.txt9 - dma-requests: virtual channels supported, each virtual channel
23 dma-requests = <24>;
Dk3dma.txt11 - dma-requests: virtual channels supported, each virtual channel
23 dma-requests = <27>;
Dnbpfaxi.txt27 You can use dma-channels and dma-requests as described in dma.txt, although they
45 dma-requests = <8>;
Darm-pl08x.txt20 - dma-requests: contains the total number of DMA requests supported by the DMAC
Dsnps-dma.txt8 - dma-requests: Number of DMA request lines supported, up to 16
35 dma-requests = <16>;
Dshdma.txt20 - dma-requests: number of DMA request signals
34 dma-requests = <256>;
Dste-dma40.txt33 - dmas: Comma separated list of dma channel requests
38 2. Device signal number, the signal line for single and burst requests
Dti-edma.txt52 dma-requests = <64>;
/linux-4.4.14/arch/powerpc/kvm/
Dtrace.h107 __field( __u32, requests )
112 __entry->requests = vcpu->requests;
116 __entry->cpu_nr, __entry->requests)
Dpowerpc.c52 v->requests; in kvm_arch_vcpu_runnable()
101 if (vcpu->requests) { in kvmppc_prepare_to_enter()
228 clear_bit(KVM_REQ_UNHALT, &vcpu->requests); in kvmppc_kvm_pv()
Dbook3s_pr_papr.c312 clear_bit(KVM_REQ_UNHALT, &vcpu->requests); in kvmppc_h_pr()
Dbooke.c577 clear_bit(KVM_REQ_WATCHDOG, &vcpu->requests); in arm_next_watchdog()
680 if (vcpu->requests) { in kvmppc_core_prepare_to_enter()
688 clear_bit(KVM_REQ_UNHALT, &vcpu->requests); in kvmppc_core_prepare_to_enter()
/linux-4.4.14/Documentation/ABI/stable/
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.
Dfirewire-cdev36 link layers, reception of inbound requests to such
38 to inbound requests
Dsysfs-driver-ib_srp164 Description: Number of requests ib_srp can send to the target before it has
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dsnps,dwc-qos-ethernet.txt20 - snps,write-requests: Number of write requests that the AXI port can issue.
22 - snps,read-requests: Number of read requests that the AXI port can issue.
58 snps,write-requests = <2>;
59 snps,read-requests = <16>;
/linux-4.4.14/drivers/base/
Ddevtmpfs.c48 } *requests; variable
109 req.next = requests; in devtmpfs_create_node()
110 requests = &req; in devtmpfs_create_node()
139 req.next = requests; in devtmpfs_delete_node()
140 requests = &req; in devtmpfs_delete_node()
391 while (requests) { in devtmpfsd()
392 struct req *req = requests; in devtmpfsd()
393 requests = NULL; in devtmpfsd()
/linux-4.4.14/Documentation/scsi/
Dhptiop.txt84 All queued requests are handled via inbound/outbound queue port.
99 - Post the packet to IOP by writing it to inbound queue. For requests
101 requests allocated in host memory, write (0x80000000|(bus_addr>>5))
108 For requests allocated in IOP memory, the request offset is posted to
111 For requests allocated in host memory, (0x80000000|(bus_addr>>5))
118 For requests allocated in IOP memory, the host driver free the request
121 Non-queued requests (reset/flush etc) can be sent via inbound message
129 All queued requests are handled via inbound/outbound list.
143 round to 0 if the index reaches the supported count of requests.
160 Non-queued requests (reset communication/reset/flush etc) can be sent via PCIe
Dufs.txt15 3.2 UTP Transfer requests
64 requests which are used to modify and retrieve configuration
74 are done through query requests.
106 3.2 UTP Transfer requests
128 In this version of UFSHCD Query requests and power management
DChangeLog.ips43 4.70.15 - Fix Breakup for very large ( non-SG ) requests
Dst.txt183 5. read_cnt - The number of read requests issued to the tape drive.
185 requests to complete.
187 8. write_cnt - The number of write requests issued to the tape drive.
189 requests to complete.
Daha152x.txt112 as base for requests in C/H/S addressing. SCSI only knows about the
/linux-4.4.14/Documentation/ABI/testing/
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.
Dsysfs-driver-ppi61 for the requests defined by TCG, i.e. requests from 1 to 22.
72 for the verdor specific requests, i.e. requests from 128 to
Dconfigfs-usb-gadget-printer8 q_len - Number of requests per endpoint
Dsysfs-class-pktcdvd46 this mark, accept new bio requests
51 bio write requests from the block
Dsysfs-fs-ext415 requests to a multiple of this tuning parameter if the
37 requests (as a power of 2) where the buddy cache is
Dsysfs-class-scsi_host21 send i/o requests directly to physical devices that are part
Dsysfs-block44 integrity of read requests serviced by devices that
76 generate checksums for write requests bound for
207 a single operation. Discard requests issued to the
Dsysfs-block-zram44 non-page-size-aligned I/O requests issued to this device.
83 because of REQ_DISCARD requests sent by bio. The former ones
Dconfigfs-usb-gadget124 per-interface requests
Dsysfs-class-net148 requests/events.
Dsysfs-bus-usb199 needed inactivity time before host requests the device to go to L1 sleep.
/linux-4.4.14/Documentation/device-mapper/
Dlog-writes.txt9 that is in the WRITE requests is copied into the log to make the replay happen
16 cache. This means that normal WRITE requests are not actually logged until the
21 This works by attaching all WRITE requests to a list once the write completes.
38 Any REQ_FUA requests bypass this flushing mechanism and are logged as soon as
39 they complete as those requests will obviously bypass the device cache.
41 Any REQ_DISCARD requests are treated like WRITE requests. Otherwise we would
42 have all the DISCARD requests, and then the WRITE requests and then the FLUSH
Dstatistics.txt73 number of requests that completed within this range. For
75 report four numbers a:b:c:d. a is the number of requests
76 that took 0-10 ms to complete, b is the number of requests
77 that took 10-20 ms to complete, c is the number of requests
79 requests that took more than 30 ms to complete.
Ddm-crypt.txt57 Block discard requests (a.k.a. TRIM) are passed through the crypt device.
58 The default is to ignore discard requests.
Ddm-log.txt41 logging requests to userspace, where a daemon receives and processes the
Dcache-policies.txt17 Because we map bios, rather than requests it's easy for the policy
/linux-4.4.14/Documentation/vm/
Dbalance10 allocation requests that have order-0 fallback options. In such cases,
13 __GFP_IO allocation requests are made to prevent file system deadlocks.
15 In the absence of non sleepable allocation requests, it seems detrimental
20 That being said, the kernel should try to fulfill requests for direct
22 the dma pool, so as to keep the dma pool filled for dma requests (atomic
25 regular memory requests by allocating one from the dma pool, instead
70 probably because all allocation requests are coming from intr context
84 watermark[WMARK_HIGH]. When low_on_memory is set, page allocation requests will
92 1. Dynamic experience should influence balancing: number of failed requests
Dzsmalloc.txt21 uncompressed form). For allocation requests larger than this size, failure
/linux-4.4.14/Documentation/filesystems/
Dgfs2-glocks.txt16 The gl_holders list contains all the queued lock requests (not
69 grant for which we ignore remote demote requests. This is in order to
150 1. DLM lock time (non-blocking requests)
151 2. DLM lock time (blocking requests)
156 currently means any requests when (a) the current state of
160 lock requests.
163 how many lock requests have been made, and thus how much data
167 of dlm lock requests issued.
185 the average time between lock requests for a glock means we
208 srtt - Smoothed round trip time for non-blocking dlm requests
[all …]
Dfuse.txt110 The default is infinite. Note that the size of read requests is
135 The number of requests which are waiting to be transferred to
143 connection. This means that all waiting requests will be aborted an
144 error returned for all aborted and new requests.
166 INTERRUPT requests take precedence over other requests, so the
169 The userspace filesystem may ignore the INTERRUPT requests entirely,
183 some timeout and/or a number of new requests to arrive, after which it
254 filesystem, the filesystem daemon serving requests can record the
Dcoda.txt157 filesystem, requests are directed at the filesystem layer in the
162 requests it receives from the operating system. When Venus has
166 requests to limit the number of interactions with Venus. Venus
220 such VFS requests by invoking one or more well defined services
255 kernel FS driver handles such requests synchronously.
271 up processes. The Coda FS driver processes VFS- and pioctl-requests
514 Coda specific requests can be made by application through the pioctl
1616 It can expect requests through:
Dbtrfs.txt63 block write requests to ensure on-disk consistency, at a large
/linux-4.4.14/Documentation/hid/
Dhid-transport.txt101 - Control Channel (ctrl): The ctrl channel is used for synchronous requests and
104 events or answers to host requests on this channel.
108 SET_REPORT requests.
116 requiring explicit requests. Devices can choose to send data continuously or
119 to device and may include LED requests, rumble requests or more. Output
127 Feature reports are never sent without requests. A host must explicitly set
138 channel provides synchronous GET/SET_REPORT requests. Plain reports are only
146 simultaneous GET_REPORT requests.
155 GET_REPORT requests can be sent for any of the 3 report types and shall
169 multiple synchronous SET_REPORT requests.
[all …]
Duhid.txt64 Data requests on the control channel are currently limited to GET_REPORT and
66 Those requests are always synchronous. That means, the kernel sends
86 writes are always handled immediately in a non-blocking fashion. Future requests
170 The kernel serializes GET_REPORT requests so there will never be two in
/linux-4.4.14/drivers/iio/adc/
Dtwl4030-madc.c69 struct twl4030_madc_request requests[TWL4030_MADC_NUM_METHODS]; member
432 madc->requests[i].result_pending = 1; in twl4030_madc_threaded_irq_handler()
435 r = &madc->requests[i]; in twl4030_madc_threaded_irq_handler()
462 r = &madc->requests[i]; in twl4030_madc_threaded_irq_handler()
489 p = &madc->requests[req->method]; in twl4030_madc_set_irq()
585 if (twl4030_madc->requests[req->method].active) { in twl4030_madc_conversion()
615 twl4030_madc->requests[req->method].active = 1; in twl4030_madc_conversion()
627 twl4030_madc->requests[req->method].active = 1; in twl4030_madc_conversion()
631 twl4030_madc->requests[req->method].active = 0; in twl4030_madc_conversion()
636 twl4030_madc->requests[req->method].active = 0; in twl4030_madc_conversion()
/linux-4.4.14/Documentation/filesystems/nfs/
Drpc-cache.txt28 - making requests to user-space to fill in cache entries
30 - delaying RPC requests that depend on as-yet incomplete
31 cache entries, and replaying those requests when the cache entry
140 Each cache can treat the write requests differently, but it is
152 user-space. These requests appear in the channel file.
154 Successive reads will return successive requests.
155 If there are no more requests to return, read will return EOF, but a
166 If it dies and needs to be restarted, any requests that have not been
179 active readers for more than 60 seconds, further requests will not be
188 While each cache is free to use its own format for requests
Didmapper.txt33 This will direct all id_resolver requests to the program /usr/sbin/nfs.idmap.
Dnfsroot.txt138 autoconfiguration requests out of all devices,
143 requests are sent using all protocols, and the first one
/linux-4.4.14/Documentation/video4linux/
Duvcvideo.txt61 directly map to the low-level UVC control requests.
70 UVC_GET_LEN requests in order to be able to allocate a sufficiently large buffer
72 UVC_GET_CUR or UVC_SET_CUR are valid requests for a given control, a
74 supported) of the resulting byte indicate which requests are valid.
182 correspond to the low-level control requests described in the UVC
183 specification. These requests are:
200 get/set requests are supported.
213 important for the result of the UVC_GET_LEN requests, which is always
Dcpia2_overview.txt34 the camera. There are three modes for this. Block mode requests a number
Dsh_mobile_ceu_camera.txt43 Such a configuration can be produced by user requests:
Dsoc-camera.txt130 Therefore all camera drivers shall reply to .g_fmt() requests with their current
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.quirks23 The PCI REQ signal is the logical-or of the incoming function requests.
26 the video function at power-up and parks there during no requests for
48 simple logical-or of video and audio requests would violate the rules.
55 internal arbiter may still logical-or the two requests. However, once
/linux-4.4.14/Documentation/networking/
Dxfrm_sysctl.txt4 default 30 - hard timeout in seconds for acquire requests
Dip_dynaddr.txt16 going up. So, the *same* (local AND masqueraded) connections requests that
Dtimestamping.txt44 Supports multiple types of timestamp requests. As a result, this
55 Some bits are requests to the stack to try to generate timestamps. Any
130 have multiple concurrent timestamping requests outstanding. Packets
151 among all possibly concurrently outstanding timestamp requests for
228 In rare cases, a timestamp request can be missed if two requests are
232 the situation by always flushing the TCP stack in between requests,
Dnetdev-features.txt158 This requests that the NIC append the Ethernet Frame Checksum (FCS)
164 This requests that the NIC receive all possible frames, including errored
Drds.txt259 transport, for example, handles all the queue pairs, work requests,
320 allocs work requests from send ring
324 populates work requests
Dip-sysctl.txt359 Maximal number of remembered connection requests, which have not
845 requests sent to it.
850 TIMESTAMP requests sent to it via broadcast/multicast.
1093 0 - (default) The kernel can respond to arp requests with addresses
1106 source IP address from IP packets in ARP requests sent on
1112 address in ARP requests to be part of their logical network
1137 received ARP requests that resolve local target IP addresses:
1156 1 - Generate gratuitous arp requests when device is brought up
1165 Both replies and requests type gratuitous arp will trigger the
/linux-4.4.14/Documentation/blockdev/drbd/
Ddrbd-connection-state-overview.dot39 label="new application (WRITE?) requests blocked\lwhile bitmap is exchanged"
48 …abel="{<any>resynchronisation process running\l'concurrent' application requests allowed|{{<T>Paus…
/linux-4.4.14/Documentation/mmc/
D00-INDEX8 - info on mmc asynchronous requests
Dmmc-async-req.txt9 The intention of non-blocking (asynchronous) MMC requests is to minimize the
12 dma_unmap_sg are processing. Using non-blocking MMC requests makes it
56 The first request in a series of requests can't be prepared in parallel
/linux-4.4.14/include/linux/
Duinput.h72 struct uinput_request *requests[UINPUT_NUM_REQUESTS]; member
Dkvm_host.h234 unsigned long requests; member
995 set_bit(KVM_REQ_MIGRATE_TIMER, &vcpu->requests); in kvm_migrate_timers()
1110 set_bit(req, &vcpu->requests); in kvm_make_request()
1115 if (test_bit(req, &vcpu->requests)) { in kvm_check_request()
1116 clear_bit(req, &vcpu->requests); in kvm_check_request()
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
Dcrossbar.txt1 Some socs have a large number of interrupts requests to service
6 that provides flexibility in muxing the device requests to the controller
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-tape.1995-20028 * we received non serial read-ahead requests from the
34 * requests are relatively fast, and once we are
35 * performing one tape r/w request, a lot of requests
50 * postponed and ide.c is free to handle requests from
75 * requests.
111 * driver will buffer the requests internally and
134 * Abort pending requests at end of media.
Dide-tape.txt7 interface, on the other hand, creates new requests, adds them
50 overlap method which enables ide.c to service requests from the
/linux-4.4.14/drivers/mmc/card/
DKconfig41 send large requests in order to get high performance. Many
47 requests back and forth from a large buffer. You will get
/linux-4.4.14/Documentation/filesystems/caching/
Dfscache.txt227 unc=N Number of uncache page requests seen
228 Acquire n=N Number of acquire cookie requests seen
239 Updates n=N Number of update cookie requests seen
242 Relinqs n=N Number of relinquish cookie requests seen
245 AttrChg n=N Number of attribute changed requests seen
246 ok=N Number of attr changed requests queued
250 Allocs n=N Number of allocation requests seen
258 Retrvls n=N Number of retrieval (read) requests seen
268 Stores n=N Number of storage (write) requests seen
Dobject.txt206 servicing netfs requests:
216 The normal running state. In this state, requests the netfs makes will be
/linux-4.4.14/arch/powerpc/perf/
Dhv-24x7.h53 struct hv_24x7_request requests[1]; member
Dhv-24x7.c1025 req = &request_buffer->requests[0]; in log_24x7_hcall()
1098 req = &request_buffer->requests[i]; in add_event_to_24x7_request()
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt29 * Read request (data read, directory listing, lookup requests) balancing between multiple servers.
30 * Write requests are replicated to multiple servers and completed only when all of them are acked.
43 possible to detach replies from requests and, if the command requires data to be received, the
Dinfo.txt14 trees looking for stale requests, which have to be resent, or if number of
68 Change IO priority to 123 (node with the highest priority gets read requests).
/linux-4.4.14/Documentation/usb/
Dehci.txt53 and interrupt transfers, including requests to USB 1.1 devices through
142 controller can process requests, and how fast devices can respond to
180 of requests. That latency is tunable; there's a module option. By
188 need to keep the EHCI queue full. That means issuing large requests,
189 or using bulk queuing if a series of small requests needs to be issued.
199 I/O be efficient, it's better to just queue up several (bulk) requests
Ddma.txt19 bit saying if it's valid. (Control requests also have "setup_dma", but
128 setup_packet buffers in control requests.
Dmtouchusb.txt59 Implement a control urb again to handle requests to and from the device
DWUSB-Design-overview.txt173 moves the requests from the UWB API to the device [/uwb_rc_ops->cmd()/]
255 to initiate DRP reservation requests through interaction with sysfs. DRP
256 reservation requests from remote UWB devices will also be handled. The
351 prepared (buffers assigned), then we can start queueing requests for
358 requests.
Dfunctionfs.txt29 for receiving events and handling setup requests.
Dproc_usb_info.txt141 | | | |__Number of isochronous requests
142 | | |__Number of interrupt requests
/linux-4.4.14/Documentation/power/
Dpm_qos_interface.txt28 For each parameter a list of performance requests is maintained along with
74 parameter requests in the following way:
93 For each device, there are three lists of PM QoS requests. Two of them are
137 initialized or the list of requests is empty.
141 power.ignore_children flag is unset (for DEV_PM_QOS_RESUME_LATENCY requests)
143 DEV_PM_QOS_LATENCY_TOLERANCE requests).
Druntime_pm.txt189 will cancel any pending requests to execute ->runtime_idle() for the same
196 scheduled requests to execute the other callbacks for the same device,
205 - timer used for scheduling (delayed) suspend and autosuspend requests
213 - work structure used for queuing up requests (i.e. work items in pm_wq)
413 (synchronously) in that case, cancel any other pending runtime PM requests
772 USB devices can go into low-power mode or send wake-up requests, but neither is
840 itself because no suspend requests of any kind are accepted while the device is
845 synchronize ->runtime_suspend() callbacks with the arrival of I/O requests.
906 requests (while holding the private lock) before allowing the suspend to
Dsuspend-and-cpuhotplug.txt169 [Please bear in mind that the kernel requests the microcode images from
204 afresh and then requests the userspace for the appropriate microcode image
/linux-4.4.14/Documentation/spi/
Dspidev2 read() and write() access to SPI slave devices. Using ioctl() requests,
80 Several ioctl() requests let your driver read or override the device's current
142 These requests commonly require that the chip not be deselected between
143 the request and response. Several such requests could be chained into
Dspi-summary134 SPI requests always go into I/O queues. Requests for a given SPI device
377 As soon as it enters probe(), the driver may issue I/O requests to
386 sequence of spi_transfer requests is arranged;
414 - The basic I/O primitive is spi_async(). Async requests may be
428 common RPC-style requests, such as writing an eight bit command
530 that a message is coming in soon, so the subsystem requests the
/linux-4.4.14/Documentation/
Ddebugging-via-ohci1394.txt11 a "Physical Response Unit" which executes specific requests by employing
14 Once properly configured, remote machines can send these requests to
15 ask the OHCI-1394 controller to perform read and write requests on
16 physical system memory and, for read requests, send the result of
Diostats.txt82 The only field that should go to zero. Incremented as requests are
138 typical workload usually contains a lot of successive and adjacent requests,
146 eventual merges. As requests can be merged across partition, this could lead
Dbcache.txt237 If non zero, bcache keeps a list of the last 128 requests submitted to compare
238 against all new requests to determine which new requests are sequential
239 continuations of previous requests for the purpose of determining sequential
Dmd.txt248 When an md array has seen no write requests for a certain period
275 All IO requests will block. The array can be reconfigured.
279 write requests fail
319 When write-mostly devices are active in a RAID1, write requests
367 requests if there are no other options.
Drbtree.txt25 track requests; the packet CD/DVD driver does the same.
27 timer requests. The ext3 filesystem tracks directory entries in a
Ddma-buf-sharing.txt41 4. When needed, buffer-user requests access to the buffer from exporter
75 Userspace entity requests for a file-descriptor (fd) which is a handle to the
115 4. When needed, buffer-user requests access to the buffer
/linux-4.4.14/fs/btrfs/
DKconfig48 Adds code that examines all block write requests (including
60 to verify the integrity of (super)-block write requests
/linux-4.4.14/drivers/acpi/acpica/
Ddbstats.c122 "%8.2X %8.2X %8.2X %8.2X\n", list->requests, list->hits, in acpi_db_list_info()
123 list->requests - list->hits, list->object_size); in acpi_db_list_info()
Dutcache.c259 ACPI_MEM_TRACKING(cache->requests++); in acpi_os_acquire_object()
/linux-4.4.14/drivers/input/misc/
Duinput.c71 if (!udev->requests[id]) { in uinput_request_alloc_id()
73 udev->requests[id] = request; in uinput_request_alloc_id()
90 return udev->requests[id]; in uinput_request_find()
105 udev->requests[request->id] = NULL; in uinput_request_done()
169 request = udev->requests[i]; in uinput_flush_requests()
/linux-4.4.14/drivers/gpu/drm/i915/
Di915_gpu_error.c446 error->ring[i].requests[j].seqno, in i915_error_state_to_str()
447 error->ring[i].requests[j].jiffies, in i915_error_state_to_str()
448 error->ring[i].requests[j].tail); in i915_error_state_to_str()
572 kfree(error->ring[i].requests); in i915_error_state_free()
1062 error->ring[i].requests = in i915_gem_record_rings()
1063 kcalloc(count, sizeof(*error->ring[i].requests), in i915_gem_record_rings()
1065 if (error->ring[i].requests == NULL) { in i915_gem_record_rings()
1074 erq = &error->ring[i].requests[count++]; in i915_gem_record_rings()
Di915_gem.c1553 struct drm_i915_gem_request *requests[I915_NUM_RINGS]; in i915_gem_object_wait_rendering__nonblocking() local
1576 requests[n++] = i915_gem_request_reference(req); in i915_gem_object_wait_rendering__nonblocking()
1585 requests[n++] = i915_gem_request_reference(req); in i915_gem_object_wait_rendering__nonblocking()
1591 ret = __i915_wait_request(requests[i], reset_counter, true, in i915_gem_object_wait_rendering__nonblocking()
1597 i915_gem_object_retire_request(obj, requests[i]); in i915_gem_object_wait_rendering__nonblocking()
1598 i915_gem_request_unreference(requests[i]); in i915_gem_object_wait_rendering__nonblocking()
2688 kmem_cache_free(req->i915->requests, req); in i915_gem_request_free()
2704 req = kmem_cache_zalloc(dev_priv->requests, GFP_KERNEL); in i915_gem_request_alloc()
2752 kmem_cache_free(dev_priv->requests, req); in i915_gem_request_alloc()
4999 dev_priv->requests = in i915_gem_load()
Di915_dma.c1123 kmem_cache_destroy(dev_priv->requests); in i915_driver_load()
1215 kmem_cache_destroy(dev_priv->requests); in i915_driver_unload()
/linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra30-actmon.txt5 which the external memory needs to be clocked in order to serve all requests
/linux-4.4.14/fs/ncpfs/
Dsock.c150 while (!list_empty(&server->tx.requests)) { in __abort_ncp_connection()
151 req = list_entry(server->tx.requests.next, struct ncp_request_reply, req); in __abort_ncp_connection()
342 list_add_tail(&req->req, &server->tx.requests); in ncp_add_request()
356 if (list_empty(&server->tx.requests)) { in __ncp_next_request()
359 req = list_entry(server->tx.requests.next, struct ncp_request_reply, req); in __ncp_next_request()
Dncp_fs_sb.h134 struct list_head requests; /* STREAM only: queued requests */ member
/linux-4.4.14/scripts/coccinelle/misc/
Dirqf_oneshot.cocci1 /// Since commit 1c6c69525b40 ("genirq: Reject bogus threaded irq requests")
/linux-4.4.14/Documentation/devicetree/bindings/spi/
Domap-spi.txt19 is to be "rxN" and "txN" for RX and TX requests,
/linux-4.4.14/Documentation/accounting/
Dcgroupstats.txt13 user space requests for statistics by passing the cgroup path.
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-bus-usb19 free to wake up in response to I/O requests, you should
Dsysfs-block-zram22 non-page-size-aligned I/O requests issued to this device.
48 because of REQ_DISCARD requests sent by bio. The former ones
/linux-4.4.14/drivers/target/
DKconfig39 process to handle requests. This is version 2 of the ABI; version 1
/linux-4.4.14/Documentation/i2c/
Dslave-interface103 The bus driver requests the next byte to be sent to another I2C master in
106 transmission, most hardware requests the next byte when the previous one is
118 reset its state machine for I2C transfers to be able to receive new requests.
Ddev-interface212 After your I2C bus driver has processed these requests, execution runs
/linux-4.4.14/block/
DKconfig.iosched20 CSCAN service with FIFO expiration of requests, switching to
/linux-4.4.14/arch/arm/boot/dts/
Dspear13xx.dtsi115 dma-requests = <32>;
129 dma-requests = <32>;
Ds5pv210.dtsi145 #dma-requests = <32>;
157 #dma-requests = <32>;
542 #dma-requests = <1>;
Dexynos5420.dtsi342 #dma-requests = <16>;
353 #dma-requests = <32>;
364 #dma-requests = <32>;
375 #dma-requests = <1>;
386 #dma-requests = <1>;
Dlpc18xx.dtsi91 dma-requests = <16>;
196 dma-requests = <64>;
Dexynos5250.dtsi680 #dma-requests = <32>;
691 #dma-requests = <32>;
702 #dma-requests = <1>;
713 #dma-requests = <1>;
Dexynos4.dtsi662 #dma-requests = <32>;
673 #dma-requests = <32>;
684 #dma-requests = <1>;
Domap2.dtsi91 dma-requests = <64>;
Dexynos3250.dtsi383 #dma-requests = <32>;
394 #dma-requests = <32>;
Dexynos4415.dtsi397 #dma-requests = <32>;
408 #dma-requests = <32>;
Dzynq-7000.dtsi289 #dma-requests = <4>;
Ddm816x.dtsi479 #dma-requests = <256>;
/linux-4.4.14/Documentation/serial/
Dmoxa-smartio469 spd_hi Use 57.6kb when the application requests 38.4kb.
470 spd_vhi Use 115.2kb when the application requests 38.4kb.
471 spd_shi Use 230.4kb when the application requests 38.4kb.
472 spd_warp Use 460.8kb when the application requests 38.4kb.
473 spd_normal Use 38.4kb when the application requests 38.4kb.
475 application requests 38.4kb.
Dtty.txt60 read() - (optional) A process requests reading data from
66 write() - (optional) A process requests writing data to the
/linux-4.4.14/arch/mips/kernel/
Dentry.S153 # notify-resume requests
/linux-4.4.14/Documentation/cgroups/
Dblkio-controller.txt215 that is no longer true as requests may be served out of order. This
232 (there might be a time lag here due to re-ordering of requests by the
240 - Total number of bios/requests merged into requests belonging to this
245 - Total number of requests queued up at any given instant for this
269 requests when not being served, i.e., it does not include any time
Dcpusets.txt241 Only a small amount of typical kernel memory, such as requests from
251 requests.
410 setting), it requests that all the CPUs in that cpusets allowed 'cpuset.cpus'
574 requests 0 and others are -1 then 0 is used.
660 There is a second exception to the above. GFP_ATOMIC requests are
/linux-4.4.14/drivers/rapidio/
DKconfig33 NWRITE (NWRITE_R, SWRITE) requests to transfer data between local
/linux-4.4.14/Documentation/rapidio/
Dtsi721.txt32 One BDMA channel is reserved for generation of maintenance read/write requests.
/linux-4.4.14/include/uapi/linux/
Ddcbnl.h161 __u64 requests[IEEE_8021QAZ_MAX_TCS]; member
/linux-4.4.14/Documentation/w1/
Dw1.netlink131 requested by the user, i.e. read/write/touch IO requests will not contain
178 Sequence number for userspace requests is set by userspace application.
/linux-4.4.14/drivers/mfd/
Ddb8500-prcmu.c727 static int requests[2]; in prcmu_config_clkout() local
739 if (!div && !requests[clkout]) in prcmu_config_clkout()
776 requests[clkout] += (div ? 1 : -1); in prcmu_config_clkout()
1078 static unsigned int requests; in db8500_prcmu_request_ape_opp_100_voltage() local
1083 if (0 != requests++) in db8500_prcmu_request_ape_opp_100_voltage()
1087 if (requests == 0) { in db8500_prcmu_request_ape_opp_100_voltage()
1090 } else if (1 != requests--) { in db8500_prcmu_request_ape_opp_100_voltage()
/linux-4.4.14/Documentation/dmaengine/
Dclient.txt18 5. Issue pending requests and wait for callback notification
154 5. Issue pending DMA requests and wait for callback notification
Dprovider.txt11 a given number of requests lines.
14 to serve several to any requests. To simplify, channels are the
15 entities that will be doing the copy, and requests what endpoints are
/linux-4.4.14/Documentation/security/
Dkeys-request-key.txt91 from which associated key requests may be satisfied.
102 Kerberos TGT key). It just requests the appropriate key, and the keyring
/linux-4.4.14/drivers/message/fusion/lsi/
Dmpi_history.txt89 * TargetAssistExtended requests.
92 * TargetAssistExtended requests.
197 * requests.
546 * for SCSI IO requests.
642 * 05-31-02 01.02.03 Adding AliasIndex to FC Direct Access requests.
703 * Diagnostic Release requests and replies.
/linux-4.4.14/drivers/net/ethernet/intel/i40e/
Di40e_dcb_nl.c112 pfc->requests[i] = pf->stats.priority_xoff_tx[i]; in i40e_dcbnl_ieee_getpfc()
/linux-4.4.14/drivers/staging/lustre/
Dsysfs-fs-lustre120 Controls how much extra time to request for unfinished requests
133 Controls when to send the early reply for requests that are
256 Controls maximum number of statahead requests to send when
351 requests in the same RPC as the main operation, which results
441 to "high priority" incoming requests.
/linux-4.4.14/arch/arm64/boot/dts/arm/
Djuno-base.dtsi113 #dma-requests = <32>;
/linux-4.4.14/drivers/usb/gadget/udc/
Dnet2280.h189 struct pci_pool *requests; member
Dnet2280.c572 td = pci_pool_alloc(ep->dev->requests, gfp_flags, in net2280_alloc_request()
600 pci_pool_free(ep->dev->requests, req->td, req->td_dma); in net2280_free_request()
3504 if (dev->requests) { in net2280_remove()
3509 pci_pool_free(dev->requests, dev->ep[i].dummy, in net2280_remove()
3512 pci_pool_destroy(dev->requests); in net2280_remove()
3654 dev->requests = pci_pool_create("requests", pdev, in net2280_probe()
3658 if (!dev->requests) { in net2280_probe()
3666 td = pci_pool_alloc(dev->requests, GFP_KERNEL, in net2280_probe()
/linux-4.4.14/Documentation/trace/
Devents-power.txt94 QoS requests.
/linux-4.4.14/Documentation/filesystems/cifs/
DCHANGES53 removes 1 of 2 network requests sent on file create)
83 (readdir) requests do not get invalid results which include the now
99 when sending large SMBWriteX requests). Fix case in which a portion of
241 time out requests if server still responding reasonably fast
242 on requests on other threads. Improve POSIX locking emulation,
310 Timeout stuck requests better (where server has never responded or sent corrupt
342 requests to the server (necessary for certain applications which break with
344 requesting case insensitive matching for path based requests (requesting
443 and for the maximum number of simultaneous requests.
506 amounts of return data. Properly limit requests to MAX_REQ (50
[all …]
DREADME76 and maximum number of simultaneous requests to one server can be configured.
341 After this timeout, the cifs client requests fresh attribute
499 nobrl Do not send byte range lock requests to the server.
505 locking, send only mandatory lock requests. For some
669 system error log with the start of smb requests
696 SMB return codes while 4 enables logging of requests that take longer
697 than one second to complete (except for byte range lock requests).
701 the start of smb requests and responses can be enabled via:
/linux-4.4.14/Documentation/blockdev/
Dzram.txt169 invalid_io RO the number of non-page-size-aligned I/O requests
173 slot free notifications or REQ_DISCARD requests)
/linux-4.4.14/net/ceph/
Ddebugfs.c148 for (p = rb_first(&osdc->requests); p; p = rb_next(p)) { in osdc_show()
Dosd_client.c838 struct rb_node **p = &osdc->requests.rb_node; in __insert_request()
854 rb_insert_color(&new->r_node, &osdc->requests); in __insert_request()
861 struct rb_node *n = osdc->requests.rb_node; in __lookup_request()
880 struct rb_node *n = osdc->requests.rb_node; in __lookup_request_ge()
1258 rb_erase(&req->r_node, &osdc->requests); in __unregister_request()
1983 for (p = rb_first(&osdc->requests); p; ) { in kick_requests()
2623 osdc->requests = RB_ROOT; in ceph_osdc_init()
/linux-4.4.14/arch/um/
DKconfig.um73 possible requests is provided.
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dti-omap-hsmmc.txt30 to be "rx" and "tx" for RX and TX DMA requests, respectively.
/linux-4.4.14/arch/arc/boot/dts/
Dabilis_tb10x.dtsi109 dma-requests = <0>;
/linux-4.4.14/Documentation/frv/
Dconfiguring.txt49 This requests that a uClinux kernel set aside some memory in an uncached
/linux-4.4.14/include/linux/ceph/
Dosd_client.h215 struct rb_root requests; /* pending requests */ member
/linux-4.4.14/Documentation/s390/
Dcds.txt158 SUBCHANNEL (HSCH) command without having pending I/O requests. This function is
181 device driver I/O requests must be issued using this routine. A device driver
350 busy, not being able to process I/O requests for other devices on the same
374 successful completion for all overlapping ccw_device_start() requests that have
/linux-4.4.14/fs/xfs/
DKconfig66 from all other requests, and this can be done quite transparently
/linux-4.4.14/Documentation/hwmon/
Dw8379378 PWM value requests from different temperature channels, but the chip
/linux-4.4.14/Documentation/i2c/busses/
Di2c-ali15x3101 This driver requests the I/O space for only the SMB
/linux-4.4.14/Documentation/powerpc/
Dptrace.txt12 following 3 new ptrace requests.
Dcxlflash.txt56 initial setup before the user application is allowed to send requests
190 requests to use the LUN in a different mode are denied.
207 requests to use the LUN in a different mode are denied.
/linux-4.4.14/drivers/usb/gadget/legacy/
DKconfig23 transfers. It also implements control requests, for "chapter 9"
181 endpoint I/O and control requests that don't relate to enumeration.
479 device. It provides a userspace API to process UVC control requests
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dam33xx-usb.txt195 #dma-requests = <256>;
/linux-4.4.14/Documentation/x86/
Dmtrr.txt21 place other than mtrr_type_lookup() to ensure any OS specific mapping requests
24 requests mtrr_type_lookup() should always return MTRR_TYPE_INVALID.
/linux-4.4.14/drivers/net/wireless/iwlwifi/
DKconfig87 patterns (e.g. incoming arp requests).
/linux-4.4.14/drivers/usb/dwc2/
Dhcd.h154 u8 requests; member
Dcore.c1882 chan->requests++; in dwc2_hc_start_transfer()
1971 chan->requests++; in dwc2_hc_start_transfer_ddma()
2031 chan->requests++; in dwc2_hc_continue_transfer()
2049 chan->requests++; in dwc2_hc_continue_transfer()
/linux-4.4.14/Documentation/networking/caif/
DLinux-CAIF.txt95 control and remote shutdown requests.
/linux-4.4.14/drivers/block/
Dxen-blkfront.c1661 struct list_head requests; in blkif_recover() local
1685 INIT_LIST_HEAD(&requests); in blkif_recover()
1700 list_add(&copy[i].request->queuelist, &requests); in blkif_recover()
1722 list_for_each_entry_safe(req, n, &requests, queuelist) { in blkif_recover()
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dcci.txt186 #dma-requests = <32>;
/linux-4.4.14/Documentation/gpio/
Dsysfs.txt134 After a kernel driver requests a GPIO, it may only be made available in
/linux-4.4.14/Documentation/console/
Dconsole.txt135 impossible for the driver to service console requests. This can happen
/linux-4.4.14/Documentation/isdn/
DINTERFACE.CAPI54 Kernel CAPI forwards registration requests from applications (calls to CAPI
67 Deregistration requests (CAPI operation CAPI_RELEASE) from applications are
DREADME.x25101 initiated when the upper (X.25 packet) layer requests the lapb datalink to
DsyncPPP.FAQ172 With the option 'noipdefault' it requests an address
/linux-4.4.14/Documentation/devicetree/bindings/crypto/
Dfsl-sec4.txt23 SEC 4 h/w can process requests from 2 types of sources.
39 up to 4 JRs can be configured; and all 4 JRs process requests in parallel.
/linux-4.4.14/arch/frv/kernel/
Dbreak.S129 # special break insn requests single-stepping to be turned back on
/linux-4.4.14/arch/arm/mach-tegra/
Dsleep-tegra20.S500 str r2, [r1, #EMC_REQ_CTRL] @ stall incoming DRAM requests
/linux-4.4.14/drivers/usb/gadget/
DKconfig356 It also implements control requests, for "chapter 9" conformance.
437 device. It provides a userspace API to process UVC control requests
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/
Dcom.fuc207 // loop over the mmio list, and send requests to the hw
/linux-4.4.14/net/bridge/netfilter/
DKconfig165 automatically sending arp replies to arp requests.
/linux-4.4.14/arch/mn10300/kernel/
Dentry.S141 # deal with pending signals and notify-resume requests
/linux-4.4.14/Documentation/driver-model/
Ddevres.txt280 devm_ioremap_resource() : checks resource, requests memory region, ioremaps
/linux-4.4.14/include/acpi/
Dactypes.h1247 u32 requests; member
/linux-4.4.14/drivers/s390/scsi/
Dzfcp_sysfs.c588 ZFCP_SHOST_ATTR(requests, "%llu %llu %llu\n",
/linux-4.4.14/Documentation/thermal/
Dpower_allocator.txt163 the exact power that the governor requests. When the temperature
/linux-4.4.14/Documentation/sound/oss/
DOpti96 When any sound device is opened the kernel requests auto-loading
/linux-4.4.14/Documentation/sysctl/
Dvm.txt90 Changing this takes effect whenever an application requests memory.
626 of free memory left when userspace requests more memory.
754 Changing this takes effect whenever an application requests memory.
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei.txt126 requests up to bytes 2k and received responses up to 2k bytes).
/linux-4.4.14/Documentation/PCI/
DPCIEBUS-HOWTO.txt50 PCI Express Ports and distributes all provided service requests

12