responses (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...20

/linux/tools/perf/pmu-events/arch/x86/knightslanding/
H A D	memory.json	11 …ts Demand code reads and prefetch code read requests that accounts for responses from DDR (local … 21 …emand code reads and prefetch code read requests that accounts for data responses from DRAM Far.", 31 …mand code reads and prefetch code read requests that accounts for data responses from DRAM Local.… 41 …ts Demand code reads and prefetch code read requests that accounts for responses from MCDRAM (loc… 51 …mand code reads and prefetch code read requests that accounts for data responses from MCDRAM Far … 61 …mand code reads and prefetch code read requests that accounts for data responses from MCDRAM Loca… 71 …nd cacheable data and L1 prefetch data read requests that accounts for responses from DDR (local … 81 …acheable data and L1 prefetch data read requests that accounts for data responses from DRAM Far.", 91 …cheable data and L1 prefetch data read requests that accounts for data responses from DRAM Local.… 101 …nd cacheable data and L1 prefetch data read requests that accounts for responses from MCDRAM (loc… [all …]
H A D	cache.json	135 …ts Demand code reads and prefetch code read requests that accounts for responses from snoop reque… 145 …ts Demand code reads and prefetch code read requests that accounts for responses from a snoop req… 155 …ts Demand code reads and prefetch code read requests that accounts for responses from a snoop req… 165 …ts Demand code reads and prefetch code read requests that accounts for responses from snoop reque… 175 …ts Demand code reads and prefetch code read requests that accounts for responses from a snoop req… 185 …ts Demand code reads and prefetch code read requests that accounts for responses from a snoop req… 195 …ts Demand code reads and prefetch code read requests that accounts for responses which hit its ow… 205 …ts Demand code reads and prefetch code read requests that accounts for responses which hit its ow… 215 …ts Demand code reads and prefetch code read requests that accounts for responses which hit its ow… 225 …ts Demand code reads and prefetch code read requests that accounts for responses which hit its ow… [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	uncore-interconnect.json	276 "PublicDescription": "Counts the number of allocations into the AK Ingress. This queue is where the IRP receives responses from R2PCIe (the ring).", 361 "BriefDescription": "Snoop Responses; Hit E or S", 366 "PublicDescription": "Snoop Responses : Hit E or S", 371 "BriefDescription": "Snoop Responses; Hit I", 376 "PublicDescription": "Snoop Responses : Hit I", 381 "BriefDescription": "Snoop Responses; Hit M", 386 "PublicDescription": "Snoop Responses : Hit M", 391 "BriefDescription": "Snoop Responses; Miss", 396 "PublicDescription": "Snoop Responses : Miss", 401 "BriefDescription": "Snoop Responses; SnpCod [all...]
H A D	uncore-cache.json	486 "BriefDescription": "Number of LLC responses that bounced on the Ring.; AD", 495 "BriefDescription": "Number of LLC responses that bounced on the Ring.; AK", 504 "BriefDescription": "Number of LLC responses that bounced on the Ring.; BL", 513 "BriefDescription": "Number of LLC responses that bounced on the Ring.; Snoops of processor's cache.", 761 "PublicDescription": "Number of times a snoop (probe) request had to retry. Filters exist to cover some of the common cases retries.; Counts the number of times that a request form the IPQ was retried because of a TOR reject from the Egress being full. IPQ requests make use of the AD Egress for regular responses, the BL egress to forward data, and the AK egress to return credits.", 901 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.; Counts the total number of times that a request from the ISMQ retried because of a TOR reject. ISMQ requests generally will not need to retry (or at least ISMQ retries are less common than IRQ retries). ISMQ requests will retry if they are not able to acquire a needed Egress credit to get onto the ring, or for cache evictions that need to acquire an RTID. Most ISMQ requests already have an RTID, so eviction retries will be less common here.", 911 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.; Counts the number of times that a request from the ISMQ retried because of a TOR reject caused by a lack of Egress credits. The egress is the buffer that queues up for allocating onto the ring. If any of the Egress queues that a given request needs to make use of are full, the request will be retried.", 921 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses fo [all...]
/linux/tools/perf/pmu-events/arch/x86/goldmontplus/
H A D	cache.json	217 …"BriefDescription": "Counts data reads (demand & prefetch) have any transaction responses from the… 223 …"PublicDescription": "Counts data reads (demand & prefetch) have any transaction responses from th… 272 …ounts data reads generated by L1 or L2 prefetchers have any transaction responses from the uncore … 278 …ounts data reads generated by L1 or L2 prefetchers have any transaction responses from the uncore … 327 …d for ownership (RFO) requests (demand & prefetch) have any transaction responses from the uncore … 333 …d for ownership (RFO) requests (demand & prefetch) have any transaction responses from the uncore … 382 …"BriefDescription": "Counts requests to the uncore subsystem have any transaction responses from t… 388 …ription": "Counts requests to the uncore subsystem have any transaction responses from the uncore … 437 …s for ownership (RFO) requests (demand & prefetch) have any transaction responses from the uncore … 443 …s for ownership (RFO) requests (demand & prefetch) have any transaction responses from the uncore … [all …]
/linux/drivers/net/wireless/intel/iwlwifi/mld/
H A D	ftm-initiator.h	`13 * @responses: the number of responses received for the current FTM session. 19 int responses[IWL_TOF_MAX_APS]; member`
H A D	ftm-initiator.c	`271 memset(mld->ftm_initiator.responses, 0, in iwl_mld_ftm_reset() 272 sizeof(mld->ftm_initiator.responses)); in iwl_mld_ftm_reset() 394 result.ftm.burst_index = mld->ftm_initiator.responses[peer_idx]; in iwl_mld_handle_ftm_resp_notif() 395 mld->ftm_initiator.responses[peer_idx]++; in iwl_mld_handle_ftm_resp_notif()`
/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-cache.json	579 "BriefDescription": "Number of LLC responses that bounced on the Ring.", 588 … "BriefDescription": "Number of LLC responses that bounced on the Ring.; Acknowledgements to core", 597 … "BriefDescription": "Number of LLC responses that bounced on the Ring.: Acknowledgements to core", 606 … "BriefDescription": "Number of LLC responses that bounced on the Ring.; Data Responses to core", 615 … "BriefDescription": "Number of LLC responses that bounced on the Ring.: Data Responses to core", 624 …"BriefDescription": "Number of LLC responses that bounced on the Ring.; Snoops of processor's cach… 633 …"BriefDescription": "Number of LLC responses that bounced on the Ring.: Snoops of processor's cach… 848 … Egress being full. IPQ requests make use of the AD Egress for regular responses, the BL egress t… 928 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 938 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … [all …]
/linux/include/xen/interface/io/
H A D	ring.h	121 * requests are pushed on to the ring and responses taken off it. 124 * requests are taken off the ring and responses put on. 224 /* Ill-behaved backend determination: Can there be this many responses? / 241 When queueing requests or responses on a shared ring, it may not always be 245 * responses). 247 * When enqueuing requests or responses: 249 * Use RING_PUSH_{REQUESTS,RESPONSES}_AND_CHECK_NOTIFY(). The second argument 253 * After dequeuing requests or responses (before sleeping the connection):
/linux/include/uapi/linux/
H A 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 106 * requests and responses from the same device would have different 144 * commands and responses. The completion code is always the first 221 * responses back. You can use the msgid value to correlate commands 222 * and responses, the driver will take care of figuring out which`
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-cache.json	690 "BriefDescription": "Number of LLC responses that bounced on the Ring.; AD", 699 "BriefDescription": "Number of LLC responses that bounced on the Ring.; AK", 708 "BriefDescription": "Number of LLC responses that bounced on the Ring.; BL", 717 "BriefDescription": "Number of LLC responses that bounced on the Ring.; Snoops of processor's cache.", 965 "PublicDescription": "Number of times a snoop (probe) request had to retry. Filters exist to cover some of the common cases retries.; Counts the number of times that a request form the IPQ was retried because of a TOR reject from the Egress being full. IPQ requests make use of the AD Egress for regular responses, the BL egress to forward data, and the AK egress to return credits.", 1105 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.; Counts the total number of times that a request from the ISMQ retried because of a TOR reject. ISMQ requests generally will not need to retry (or at least ISMQ retries are less common than IRQ retries). ISMQ requests will retry if they are not able to acquire a needed Egress credit to get onto the ring, or for cache evictions that need to acquire an RTID. Most ISMQ requests already have an RTID, so eviction retries will be less common here.", 1115 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.; Counts the number of times that a request from the ISMQ retried because of a TOR reject caused by a lack of Egress credits. The egress is the buffer that queues up for allocating onto the ring. If any of the Egress queues that a given request needs to make use of are full, the request will be retried.", 1125 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses fo [all...]
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-cache.json	680 "BriefDescription": "Number of LLC responses that bounced on the Ring.; AD", 689 "BriefDescription": "Number of LLC responses that bounced on the Ring.; AK", 698 "BriefDescription": "Number of LLC responses that bounced on the Ring.; BL", 707 "BriefDescription": "Number of LLC responses that bounced on the Ring.; Snoops of processor's cache.", 955 "PublicDescription": "Number of times a snoop (probe) request had to retry. Filters exist to cover some of the common cases retries.; Counts the number of times that a request form the IPQ was retried because of a TOR reject from the Egress being full. IPQ requests make use of the AD Egress for regular responses, the BL egress to forward data, and the AK egress to return credits.", 1095 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.; Counts the total number of times that a request from the ISMQ retried because of a TOR reject. ISMQ requests generally will not need to retry (or at least ISMQ retries are less common than IRQ retries). ISMQ requests will retry if they are not able to acquire a needed Egress credit to get onto the ring, or for cache evictions that need to acquire an RTID. Most ISMQ requests already have an RTID, so eviction retries will be less common here.", 1105 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.; Counts the number of times that a request from the ISMQ retried because of a TOR reject caused by a lack of Egress credits. The egress is the buffer that queues up for allocating onto the ring. If any of the Egress queues that a given request needs to make use of are full, the request will be retried.", 1115 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses fo [all...]
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	uncore-cache.json	2243 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2254 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2265 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2276 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2287 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2298 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2309 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2320 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2331 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2342 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … [all …]
/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A D	uncore-cache.json	1875 "BriefDescription": "Messages that bounced on the Vertical Ring.; Data Responses to core", 1967 "BriefDescription": "Sink Starvation on Vertical Ring; Data Responses to core", 2397 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.", 2408 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.", 2419 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.", 2430 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses com [all...]
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	uncore-cache.json	1987 "BriefDescription": "Messages that bounced on the Vertical Ring.; Data Responses to core", 2079 "BriefDescription": "Sink Starvation on Vertical Ring; Data Responses to core", 2509 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.", 2520 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.", 2531 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses come back from the cores.", 2542 "PublicDescription": "Number of times a transaction flowing through the ISMQ had to retry. Transaction pass through the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when data is returned or when snoop responses com [all...]
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A D	uncore-cache.json	2243 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2254 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2265 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2276 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2287 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2298 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2309 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2320 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2331 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 2342 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … [all …]
/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A D	uncore-cache.json	2753 "BriefDescription": "Messages that bounced on the Vertical Ring. : Data Responses to core", 2759 …"PublicDescription": "Messages that bounced on the Vertical Ring. : Data Responses to core : Numbe… 2855 "BriefDescription": "Sink Starvation on Vertical Ring : Data Responses to core", 3105 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 3116 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 3127 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 3138 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 3149 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 3160 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … 3171 …gh the ISMQ as responses for requests that already exist in the Cbo. Some examples include: when … [all …]
/linux/include/linux/
H A D	ipmi_smi.h	`57 * And responses, similarly, with an completion code added (NetFn must 64 * With normal messages, only commands are sent and only responses are 74 * Responses will using the following format: 84 * IPMB messages can be commands and responses in both directions.`
/linux/drivers/net/ethernet/brocade/bna/
H A D	bfa_cee.c	`65 * 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`
/linux/Documentation/usb/
H A D	raw-gadget.rst	`28 2. Raw Gadget allows providing arbitrary data as responses to USB requests, 31 responses to USB requests.`
/linux/drivers/iommu/intel/
H A D	prq.c	`46 * intel_iommu_drain_pasid_prq - Drain page requests and responses for a pasid 50 * Drain all pending page requests and responses related to @pasid in both 58 * responses pending in the hardware. 105 * requests and responses in hardware. in intel_iommu_drain_pasid_prq()`
/linux/Documentation/userspace-api/netlink/
H A D	genetlink-legacy.rst	109 responses share the same message ID. Notifications have separate 130 Requests and responses for operation ``a`` will have the ID of 1, 131 the requests and responses of ``b`` - 2 (since there is no explicit
/linux/sound/firewire/fireworks/
H A D	fireworks_hwdep.c	`41 /* 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()`
/linux/tools/perf/pmu-events/arch/arm64/arm/cmn/sys/
H A D	cmn.json	`118 …nd RREADY) dispatched on port 0. This event measures the read bandwidth, including CMO responses.", 126 …nd RREADY) dispatched on port 1. This event measures the read bandwidth, including CMO responses.", 134 …nd RREADY) dispatched on port 2. This event measures the read bandwidth, including CMO responses.",`
/linux/Documentation/ABI/testing/
H A D	debugfs-driver-qat	`5 Description: (RO) Read returns the number of requests sent to the FW and the number of responses 9 <N>: Number of requests sent from Acceleration Engine N to FW and responses`

12 3 4 5 6 7 8 9 10 >>...20