Home
last modified time | relevance | path

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

12345678910>>...37

/kernel/linux/linux-4.19/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/include/xen/interface/io/
Dring.h110 * requests are pushed on to the ring and responses taken off it.
113 * requests are taken off the ring and responses put on.
208 virt_wmb(); /* front sees responses /before/ updated producer index */ \
215 * When queueing requests or responses on a shared ring, it may not always be
219 * responses).
221 * When enqueuing requests or responses:
223 * Use RING_PUSH_{REQUESTS,RESPONSES}_AND_CHECK_NOTIFY(). The second argument
227 * After dequeuing requests or responses (before sleeping the connection):
255 virt_wmb(); /* front sees responses /before/ updated producer index */ \
257 virt_mb(); /* front sees new responses /before/ we check rsp_event */ \
/kernel/linux/linux-4.19/include/xen/interface/io/
Dring.h110 * requests are pushed on to the ring and responses taken off it.
113 * requests are taken off the ring and responses put on.
219 virt_wmb(); /* front sees responses /before/ updated producer index */ \
226 * When queueing requests or responses on a shared ring, it may not always be
230 * responses).
232 * When enqueuing requests or responses:
234 * Use RING_PUSH_{REQUESTS,RESPONSES}_AND_CHECK_NOTIFY(). The second argument
238 * After dequeuing requests or responses (before sleeping the connection):
266 virt_wmb(); /* front sees responses /before/ updated producer index */ \
268 virt_mb(); /* front sees new responses /before/ we check rsp_event */ \
/kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/goldmontplus/
Dcache.json255 …ts demand cacheable data reads of full cache lines have any transaction responses from the uncore …
265 …ts demand cacheable data reads of full cache lines have any transaction responses from the uncore …
330 …uests generated by a write to full data cache line have any transaction responses from the uncore …
340 …uests generated by a write to full data cache line have any transaction responses from the uncore …
405 … prefetch requests that miss the instruction cache have any transaction responses from the uncore …
415 … prefetch requests that miss the instruction cache have any transaction responses from the uncore …
480 …ck transactions caused by L1 or L2 cache evictions have any transaction responses from the uncore …
490 …ck transactions caused by L1 or L2 cache evictions have any transaction responses from the uncore …
555 …ne reads generated by hardware L2 cache prefetcher have any transaction responses from the uncore …
565 …ne reads generated by hardware L2 cache prefetcher have any transaction responses from the uncore …
[all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-4.19/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
Dnetfilter.h10 /* Responses from hook functions. */
37 /* Generic cache responses from hook functions.
/kernel/linux/linux-5.10/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
/kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/goldmont/
Dcache.json305 … ownership (RFO) requests (demand & prefetch) that have any transaction responses from the uncore …
313 … ownership (RFO) requests (demand & prefetch) that have any transaction responses from the uncore …
396 … ownership (RFO) requests (demand & prefetch) that have any transaction responses from the uncore …
404 … ownership (RFO) requests (demand & prefetch) that have any transaction responses from the uncore …
487 …tion": "Counts data reads (demand & prefetch) that have any transaction responses from the uncore …
495 …tion": "Counts data reads (demand & prefetch) that have any transaction responses from the uncore …
578 … data reads generated by L1 or L2 prefetchers that have any transaction responses from the uncore …
586 … data reads generated by L1 or L2 prefetchers that have any transaction responses from the uncore …
669 …on": "Counts requests to the uncore subsystem that have any transaction responses from the uncore …
677 …on": "Counts requests to the uncore subsystem that have any transaction responses from the uncore …
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/mmc/
Dmtk-sd.txt42 If present,HS400 command responses are sampled on rising edges.
43 If not present,HS400 command responses are sampled on falling edges.
/kernel/linux/linux-4.19/drivers/isdn/i4l/
Disdn_tty.h33 #define REG_RESPNUM 12 /* show numeric responses register */
34 #define BIT_RESPNUM 2 /* show numeric responses bit */
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/
Dmtk-sd.txt47 If present,HS400 command responses are sampled on rising edges.
48 If not present,HS400 command responses are sampled on falling edges.
/kernel/linux/linux-4.19/drivers/net/ethernet/brocade/bna/
Dbfa_cee.c73 * bfa_cee_get_attr_isr - CEE ISR for get-attributes responses from f/w
93 * bfa_cee_get_attr_isr - CEE ISR for get-stats responses from f/w
115 * @brief CEE ISR for reset-stats responses from f/w
/kernel/linux/linux-5.10/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_attr_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
/kernel/linux/linux-4.19/sound/firewire/fireworks/
Dfireworks_hwdep.c41 /* write into buffer as many responses as possible */ in hwdep_read_resp_buf()
47 * series of responses. in hwdep_read_resp_buf()
89 * sequence of responses depending on variation of buffer length. in hwdep_read_resp_buf()
/kernel/linux/linux-5.10/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()
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-5.10/Documentation/networking/
Dnfc.rst126 commands and their responses.
129 on. In order to allow valid "empty" responses, every data received has a NULL
/kernel/linux/linux-4.19/Documentation/networking/
Dnfc.txt124 commands and their responses.
127 on. In order to allow valid "empty" responses, every data received has a NULL
/kernel/linux/linux-4.19/drivers/misc/ti-st/
DKconfig14 to register themselves with core and send data, the responses
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-5.10/include/uapi/scsi/fc/
Dfc_ns.h72 __u8 fp_flags; /* flags for responses only */
77 * fp_flags in port ID object, for responses only.

12345678910>>...37