Searched full:responses (Results 1 – 25 of 471) sorted by relevance
12345678910>>...19
/Linux-v5.10/tools/perf/pmu-events/arch/x86/knightslanding/ |
D | memory.json | 18 …"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 …]
|
D | cache.json | 135 …"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.10/include/xen/interface/io/ |
D | ring.h | 110 * 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 */ \
|
/Linux-v5.10/tools/perf/pmu-events/arch/x86/goldmontplus/ |
D | cache.json | 269 …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.10/include/uapi/linux/ |
D | ipmi.h | 33 * 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
|
D | virtio_gpu.h | 89 /* success responses */ 97 /* error responses */
|
D | netfilter.h | 10 /* Responses from hook functions. */
|
/Linux-v5.10/Documentation/devicetree/bindings/mmc/ |
D | mtk-sd.txt | 47 If present,HS400 command responses are sampled on rising edges. 48 If not present,HS400 command responses are sampled on falling edges.
|
/Linux-v5.10/drivers/net/ethernet/brocade/bna/ |
D | bfa_cee.c | 65 * 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
|
D | bfi_enet.h | 249 /* Rx Responses */ 288 /* Tx Responses */ 294 /* Port Responses */ 307 /* Statistics Responses */
|
/Linux-v5.10/sound/firewire/fireworks/ |
D | fireworks_hwdep.c | 40 /* 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.10/include/linux/platform_data/ |
D | cros_ec_proto.h | 31 * 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.10/Documentation/networking/ |
D | nfc.rst | 126 commands and their responses. 129 on. In order to allow valid "empty" responses, every data received has a NULL
|
/Linux-v5.10/include/uapi/scsi/fc/ |
D | fc_ns.h | 72 __u8 fp_flags; /* flags for responses only */ 77 * fp_flags in port ID object, for responses only.
|
/Linux-v5.10/drivers/misc/vmw_vmci/ |
D | vmci_queue_pair.h | 115 * commands and responses to B. The other queue is used by B to transmit 116 * commands and responses.
|
/Linux-v5.10/drivers/misc/ti-st/ |
D | Kconfig | 15 to register themselves with core and send data, the responses
|
/Linux-v5.10/Documentation/ABI/testing/ |
D | debugfs-olpc | 8 reading their responses.
|
/Linux-v5.10/drivers/crypto/caam/ |
D | qi.h | 102 * responses. The request completion callback would be issued from this 126 * or too many CAAM responses are pending to be processed.
|
/Linux-v5.10/drivers/char/tpm/ |
D | tpm_vtpm_proxy.c | 117 * 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.10/drivers/net/ethernet/chelsio/cxgb3/ |
D | adapter.h | 150 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.10/arch/mips/include/asm/ |
D | traps.h | 11 * Possible status responses for a board_be_handler backend.
|
/Linux-v5.10/Documentation/vm/ |
D | index.rst | 25 details ranging from notes and mailing list responses to elaborate
|
/Linux-v5.10/drivers/s390/scsi/ |
D | zfcp_dbf.h | 108 /** 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
|
/Linux-v5.10/kernel/ |
D | Kconfig.hz | 47 systems requiring fast interactive responses to events.
|
/Linux-v5.10/Documentation/filesystems/ |
D | orangefs.rst | 406 Responses to kernel requests are all packaged in pvfs2_downcall_t 473 Userspace uses writev() on /dev/pvfs2-req to pass responses to the requests 490 responses:: 505 Readdir responses initialize the fifth element io_array like this::
|
12345678910>>...19