Home
last modified time | relevance | path

Searched full:responses (Results 1 – 25 of 509) sorted by relevance

12345678910>>...21

/Linux-v5.15/tools/perf/pmu-events/arch/x86/knightslanding/
Dmemory.json18 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from MCDRAM Far…
29 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from MCDRAM Loc…
40 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from DRAM Far.",
51 …"BriefDescription": "Counts any Prefetch requests that accounts for data responses from DRAM Local…
62 …"BriefDescription": "Counts any Read request that accounts for data responses from MCDRAM Far or …
73 …"BriefDescription": "Counts any Read request that accounts for data responses from MCDRAM Local.",
84 … "BriefDescription": "Counts any Read request that accounts for data responses from DRAM Far.",
95 … "BriefDescription": "Counts any Read request that accounts for data responses from DRAM Local.",
106 …mand code reads and prefetch code read requests that accounts for data responses from MCDRAM Far …
117 …mand code reads and prefetch code read requests that accounts for data responses from MCDRAM Loca…
[all …]
Dcache.json135 …"BriefDescription": "Counts any Prefetch requests that accounts for responses from a snoop request…
146 …"BriefDescription": "Counts any Prefetch requests that accounts for responses from a snoop request…
157 …"BriefDescription": "Counts any Prefetch requests that accounts for responses from a snoop request…
168 …"BriefDescription": "Counts any Prefetch requests that accounts for responses from a snoop request…
201 …"BriefDescription": "Counts any Read request that accounts for responses from a snoop request hit…
212 …"BriefDescription": "Counts any Read request that accounts for responses from a snoop request hit…
223 …"BriefDescription": "Counts any Read request that accounts for responses from a snoop request hit…
234 …"BriefDescription": "Counts any Read request that accounts for responses from a snoop request hit…
267 …ts Demand code reads and prefetch code read requests that accounts for responses from a snoop req…
278 …ts Demand code reads and prefetch code read requests that accounts for responses from a snoop req…
[all …]
/Linux-v5.15/tools/perf/pmu-events/arch/x86/goldmontplus/
Dcache.json269 …ts demand cacheable data reads of full cache lines have any transaction responses from the uncore …
279 …ts demand cacheable data reads of full cache lines have any transaction responses from the uncore …
344 …uests generated by a write to full data cache line have any transaction responses from the uncore …
354 …uests generated by a write to full data cache line have any transaction responses from the uncore …
419 … prefetch requests that miss the instruction cache have any transaction responses from the uncore …
429 … prefetch requests that miss the instruction cache have any transaction responses from the uncore …
494 …ck transactions caused by L1 or L2 cache evictions have any transaction responses from the uncore …
504 …ck transactions caused by L1 or L2 cache evictions have any transaction responses from the uncore …
569 …ne reads generated by hardware L2 cache prefetcher have any transaction responses from the uncore …
579 …ne reads generated by hardware L2 cache prefetcher have any transaction responses from the uncore …
[all …]
/Linux-v5.15/include/uapi/linux/
Dipmi.h33 * send commands, receive responses, etc. The driver keeps track of
34 * commands the user sends and tracks the responses. The responses
92 * requests and responses from the same device would have different
130 * commands and responses. The completion code is always the first
207 * responses back. You can use the msgid value to correlate commands
208 * and responses, the driver will take care of figuring out which
Dvirtio_scmi.h12 /* Device implements some SCMI notifications, or delayed responses. */
/Linux-v5.15/include/xen/interface/io/
Dring.h139 * requests are pushed on to the ring and responses taken off it.
142 * requests are taken off the ring and responses put on.
232 /* Ill-behaved backend determination: Can there be this many responses? */
249 * When queueing requests or responses on a shared ring, it may not always be
253 * responses).
255 * When enqueuing requests or responses:
257 * Use RING_PUSH_{REQUESTS,RESPONSES}_AND_CHECK_NOTIFY(). The second argument
261 * After dequeuing requests or responses (before sleeping the connection):
/Linux-v5.15/Documentation/driver-api/surface_aggregator/
Dssh.rst192 Commands: Requests, Responses, and Events
246 the EC as well as by the EC to send responses and events back to the host.
247 We differentiate between requests (sent by the host), responses (sent by the
265 Responses are matched to their corresponding request via the request ID
288 Furthermore, requests, responses, and events have an associated target ID
295 field, as responses are generally sent from the EC to the host).
Dinternal.rst72 responses of the EC to those requests, and events (sent from EC to host).
73 It, specifically, distinguishes events from request responses, matches
74 responses to their corresponding requests, and implements request timeouts.
77 how request responses and, especially, events are dealt with. It provides an
294 separates responses to requests from events, which are also sent by the EC
295 via a |ssh_command| payload. While responses are handled in this layer,
/Linux-v5.15/Documentation/usb/
Draw-gadget.rst28 2. Raw Gadget allows providing arbitrary data as responses to USB requests,
31 responses to USB requests.
/Linux-v5.15/drivers/net/ethernet/brocade/bna/
Dbfa_cee.c65 * bfa_cee_get_attr_isr - CEE ISR for get-attributes responses from f/w
85 * bfa_cee_get_stats_isr - CEE ISR for get-stats responses from f/w
105 * bfa_cee_reset_stats_isr - CEE ISR for reset-stats responses from f/w
Dbfi_enet.h249 /* Rx Responses */
288 /* Tx Responses */
294 /* Port Responses */
307 /* Statistics Responses */
/Linux-v5.15/sound/firewire/fireworks/
Dfireworks_hwdep.c40 /* write into buffer as many responses as possible */ in hwdep_read_resp_buf()
46 * series of responses. in hwdep_read_resp_buf()
88 * sequence of responses depending on variation of buffer length. in hwdep_read_resp_buf()
/Linux-v5.15/include/linux/platform_data/
Dcros_ec_proto.h31 * Max bus-specific overhead incurred by request/responses.
33 * I2C requires 2 additional bytes for responses.
34 * SPI requires up to 32 additional bytes for responses.
/Linux-v5.15/Documentation/networking/
Dmctp.rst169 implicit local socket address, to allow the socket to receive responses to this
173 Sockets will only receive responses to requests they have sent (with TO=1) and
212 Like the send calls, sockets will only receive responses to requests they have
Dnfc.rst126 commands and their responses.
129 on. In order to allow valid "empty" responses, every data received has a NULL
/Linux-v5.15/Documentation/devicetree/bindings/mmc/
Dmtk-sd.yaml119 If present, HS400 command responses are sampled on rising edges.
120 If not present, HS400 command responses are sampled on falling edges.
/Linux-v5.15/drivers/misc/vmw_vmci/
Dvmci_queue_pair.h115 * commands and responses to B. The other queue is used by B to transmit
116 * commands and responses.
/Linux-v5.15/include/uapi/scsi/fc/
Dfc_ns.h72 __u8 fp_flags; /* flags for responses only */
77 * fp_flags in port ID object, for responses only.
/Linux-v5.15/drivers/misc/ti-st/
DKconfig15 to register themselves with core and send data, the responses
/Linux-v5.15/arch/s390/
DKconfig.debug21 and instruction responses to the CIO layer of Linux kernel. The newly created
/Linux-v5.15/Documentation/ABI/testing/
Ddebugfs-olpc8 reading their responses.
/Linux-v5.15/drivers/crypto/caam/
Dqi.h102 * responses. The request completion callback would be issued from this
126 * or too many CAAM responses are pending to be processed.
/Linux-v5.15/drivers/char/tpm/
Dtpm_vtpm_proxy.c117 * vtpm_proxy_fops_write - Write TPM responses on 'server side'
221 /* no more TPM responses -- wake up anyone waiting for them */ in vtpm_proxy_fops_undo_open()
255 * 'server side' and receive responses from there.
259 * Called when core TPM driver reads TPM responses from 'server side'
/Linux-v5.15/drivers/net/ethernet/chelsio/cxgb3/
Dadapter.h150 unsigned long pure_rsps; /* # of pure (non-data) responses */
151 unsigned long imm_data; /* responses with immediate data */
155 unsigned long nomem; /* # of responses deferred due to no mem */
/Linux-v5.15/drivers/s390/scsi/
Dzfcp_dbf.h108 /** struct zfcp_dbf_san - trace record for SAN requests and responses
126 * struct zfcp_dbf_hba_res - trace record for hba responses
206 * @u.res: data for fsf responses

12345678910>>...21