| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/alderlake/ |
| D | frontend.json | 65 …ecoded instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of …
113 …delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.",
119 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
125 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
131 …nt-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.",
137 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
149 …elivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.",
155 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
161 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
167 …ad at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | frontend.json | 51 …ecoded instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of …
95 …delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.",
100 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
106 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
111 …nt-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.",
117 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
128 …elivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.",
133 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
139 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
144 …ad at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.",
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 38 total write-back cache that relates to its current average
42 percentage of the write-back cache to a particular device.
52 total write-back cache that relates to its current average
56 of the write-back cache to a particular device. The value is
67 given percentage of the write-back cache. This is useful in
69 most of the write-back cache. For example in case of an NFS
80 given value of the write-back cache. The value is given as part
82 one device taking all or most of the write-back cache. For example
93 total write-back cache that relates to its current average
97 percentage of the write-back cache to a particular device
[all …]
|
| D | sysfs-bus-surface_aggregator-tabletsw | 18 - "folded-canvas": The type-cover has been folded back
19 part-ways, but does not lie flush with the back side of the
23 - "folded-back": The type cover has been fully folded back and
24 lies flush with the back side of the device.
47 back and the device operates mainly based on touch input.
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/meteorlake/ |
| D | frontend.json | 85 …ecoded instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of …
142 …delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.",
148 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
154 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
160 …nt-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.",
166 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
178 …elivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.",
184 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
190 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
196 …ad at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelake/ |
| D | frontend.json | 54 …ecoded instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of …
98 …delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.",
103 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
109 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
114 …nt-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.",
120 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
131 …elivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.",
136 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
142 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
147 …ad at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/rocketlake/ |
| D | frontend.json | 54 …ecoded instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of …
98 …delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.",
103 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
109 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
114 …nt-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.",
120 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
131 …elivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.",
136 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
142 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
147 …ad at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | frontend.json | 54 …ecoded instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of …
98 …delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.",
103 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
109 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
114 …nt-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.",
120 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
131 …elivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.",
136 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
142 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
147 …ad at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.",
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | frontend.json | 54 …ecoded instruction-cache) miss. Critical means stalls were exposed to the back-end as a result of …
98 …delivered no uops for a period of at least 1 cycle which was not interrupted by a back-end stall.",
103 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
109 …t-end delivered no uops for a period of 128 cycles which was not interrupted by a back-end stall.",
114 …nt-end delivered no uops for a period of 16 cycles which was not interrupted by a back-end stall.",
120 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
131 …elivered no uops for a period of at least 2 cycles which was not interrupted by a back-end stall.",
136 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
142 …t-end delivered no uops for a period of 256 cycles which was not interrupted by a back-end stall.",
147 …ad at least 1 bubble-slot for a period of 2 cycles which was not interrupted by a back-end stall.",
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/md/ |
| D | raid5-cache.rst | 8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since
11 in write-through mode. A user can switch it to write-back mode by::
13 echo "write-back" > /sys/block/md0/md/journal_mode
15 And switch it back to write-through mode by::
30 tries to resync the array to bring it back to normal state. But before the
47 write-back mode
50 write-back mode fixes the 'write hole' issue too, since all write data is
51 cached on cache disk. But the main goal of 'write-back' cache is to speed up
56 overhead too. Write-back cache will aggregate the data and flush the data to
61 In write-back mode, MD reports IO completion to upper layer (usually
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/md/ |
| D | raid5-cache.rst | 8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since
11 in write-through mode. A user can switch it to write-back mode by::
13 echo "write-back" > /sys/block/md0/md/journal_mode
15 And switch it back to write-through mode by::
30 tries to resync the array to bring it back to normal state. But before the
47 write-back mode
50 write-back mode fixes the 'write hole' issue too, since all write data is
51 cached on cache disk. But the main goal of 'write-back' cache is to speed up
56 overhead too. Write-back cache will aggregate the data and flush the data to
61 In write-back mode, MD reports IO completion to upper layer (usually
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | amd-iommu.h | 14 * This is mainly used to communicate information back-and-forth
94 * amd_iommu_set_invalid_ppr_cb() - Register a call-back for failed
96 * @pdev: The PCI device the call-back should be registered for
97 * @cb: The call-back function
99 * The IOMMUv2 driver invokes this call-back when it is unable to
102 * the call-back are:
104 * - AMD_IOMMU_INV_PRI_RSP_SUCCESS - Send SUCCESS back to the device
105 * - AMD_IOMMU_INV_PRI_RSP_INVALID - Send INVALID back to the device
106 * - AMD_IOMMU_INV_PRI_RSP_FAIL - Send Failure back to the device,
158 * amd_iommu_set_invalidate_ctx_cb() - Register a call-back for invalidating
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | amd-iommu.h | 16 * This is mainly used to communicate information back-and-forth
77 * amd_iommu_set_invalid_ppr_cb() - Register a call-back for failed
79 * @pdev: The PCI device the call-back should be registered for
80 * @cb: The call-back function
82 * The IOMMUv2 driver invokes this call-back when it is unable to
85 * the call-back are:
87 * - AMD_IOMMU_INV_PRI_RSP_SUCCESS - Send SUCCESS back to the device
88 * - AMD_IOMMU_INV_PRI_RSP_INVALID - Send INVALID back to the device
89 * - AMD_IOMMU_INV_PRI_RSP_FAIL - Send Failure back to the device,
141 * amd_iommu_set_invalidate_ctx_cb() - Register a call-back for invalidating
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/icelake/ |
| D | frontend.json | 154 …ered to by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no ba…
165 …livered by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no ba…
177 …livered by the Instruction Decode Queue (IDQ) to the back-end of the pipeline when there was no ba…
185 …ption": "Cycles when optimal number of uops was delivered to the back-end when the back-end is not…
277 …ont-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end stall.",
286 …ont-end delivered no uops for a period of 2 cycles which was not interrupted by a back-end stall.",
292 …ont-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end stall.",
301 …ont-end delivered no uops for a period of 4 cycles which was not interrupted by a back-end stall.",
307 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
316 …ont-end delivered no uops for a period of 8 cycles which was not interrupted by a back-end stall.",
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/intel/ice/ |
| D | ice_fltr.c | 61 struct ice_pf *pf = hw->back; in ice_fltr_set_vlan_vsi_promisc()
85 struct ice_pf *pf = hw->back; in ice_fltr_clear_vlan_vsi_promisc()
108 struct ice_pf *pf = hw->back; in ice_fltr_clear_vsi_promisc()
131 struct ice_pf *pf = hw->back; in ice_fltr_set_vsi_promisc()
150 return ice_add_mac(&vsi->back->hw, list); in ice_fltr_add_mac_list()
160 return ice_remove_mac(&vsi->back->hw, list); in ice_fltr_remove_mac_list()
170 return ice_add_vlan(&vsi->back->hw, list); in ice_fltr_add_vlan_list()
181 return ice_remove_vlan(&vsi->back->hw, list); in ice_fltr_remove_vlan_list()
191 return ice_add_eth_mac(&vsi->back->hw, list); in ice_fltr_add_eth_list()
201 return ice_remove_eth_mac(&vsi->back->hw, list); in ice_fltr_remove_eth_list()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/netronome/nfp/crypto/ |
| D | tls.c | 189 return &req->back; in nfp_net_tls_set_ipv4()
209 return &req->back; in nfp_net_tls_set_ipv6()
214 struct nfp_crypto_req_add_back *back, struct sock *sk, in nfp_net_tls_set_l4() argument
222 back->src_port = 0; in nfp_net_tls_set_l4()
223 back->dst_port = 0; in nfp_net_tls_set_l4()
225 back->src_port = inet->inet_dport; in nfp_net_tls_set_l4()
226 back->dst_port = inet->inet_sport; in nfp_net_tls_set_l4()
273 struct nfp_crypto_req_add_back *back; in nfp_net_tls_add() local
328 back = nfp_net_tls_set_ipv6(nn, req, sk, direction); in nfp_net_tls_add()
330 back = nfp_net_tls_set_ipv4(nn, req, sk, direction); in nfp_net_tls_add()
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/netronome/nfp/crypto/ |
| D | tls.c | 189 return &req->back; in nfp_net_tls_set_ipv4()
209 return &req->back; in nfp_net_tls_set_ipv6()
214 struct nfp_crypto_req_add_back *back, struct sock *sk, in nfp_net_tls_set_l4() argument
222 back->src_port = 0; in nfp_net_tls_set_l4()
223 back->dst_port = 0; in nfp_net_tls_set_l4()
225 back->src_port = inet->inet_dport; in nfp_net_tls_set_l4()
226 back->dst_port = inet->inet_sport; in nfp_net_tls_set_l4()
273 struct nfp_crypto_req_add_back *back; in nfp_net_tls_add() local
328 back = nfp_net_tls_set_ipv6(nn, req, sk, direction); in nfp_net_tls_add()
330 back = nfp_net_tls_set_ipv4(nn, req, sk, direction); in nfp_net_tls_add()
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/benchs/ |
| D | run_bench_ringbufs.sh | 19 header "Single-producer, back-to-back mode"
25 header "Ringbuf back-to-back, effect of sample rate"
29 header "Perfbuf back-to-back, effect of sample rate"
34 header "Ringbuf back-to-back, reserve+commit vs output"
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | viafb.modes | 19 # Back Porch 1.907 us 1.048 ms
44 # Back Porch 3.810 us 0.427 ms
65 # Back Porch 2.222 us 0.578 ms
86 # Back Porch 2.409 us 0.475 ms
107 # Back Porch 1.984 us 0.496 ms
128 # Back Porch 3.274 us 0.462 ms
149 # Back Porch 3.245 us 435.949 us
170 # Back Porch 2.939 us 0.459 ms
191 # Back Porch 2.200 us 0.607 ms
213 # Back Porch 3.232 us 0.448 ms
[all …]
|
| /kernel/linux/linux-6.6/Documentation/fb/ |
| D | viafb.modes | 19 # Back Porch 1.907 us 1.048 ms
44 # Back Porch 3.810 us 0.427 ms
65 # Back Porch 2.222 us 0.578 ms
86 # Back Porch 2.409 us 0.475 ms
107 # Back Porch 1.984 us 0.496 ms
128 # Back Porch 3.274 us 0.462 ms
149 # Back Porch 3.245 us 435.949 us
170 # Back Porch 2.939 us 0.459 ms
191 # Back Porch 2.200 us 0.607 ms
213 # Back Porch 3.232 us 0.448 ms
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/intel/ice/ |
| D | ice_fltr.c | 57 return ice_add_mac(&vsi->back->hw, list); in ice_fltr_add_mac_list()
68 return ice_remove_mac(&vsi->back->hw, list); in ice_fltr_remove_mac_list()
79 return ice_add_vlan(&vsi->back->hw, list); in ice_fltr_add_vlan_list()
90 return ice_remove_vlan(&vsi->back->hw, list); in ice_fltr_remove_vlan_list()
101 return ice_add_eth_mac(&vsi->back->hw, list); in ice_fltr_add_eth_list()
112 return ice_remove_eth_mac(&vsi->back->hw, list); in ice_fltr_remove_eth_list()
121 ice_remove_vsi_fltr(&vsi->back->hw, vsi->idx); in ice_fltr_remove_all()
145 return ice_fltr_add_entry_to_list(ice_pf_to_dev(vsi->back), &info, in ice_fltr_add_mac_to_list()
169 return ice_fltr_add_entry_to_list(ice_pf_to_dev(vsi->back), &info, in ice_fltr_add_vlan_to_list()
199 return ice_fltr_add_entry_to_list(ice_pf_to_dev(vsi->back), &info, in ice_fltr_add_eth_to_list()
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/benchs/ |
| D | run_bench_ringbufs.sh | 43 header "Single-producer, back-to-back mode"
49 header "Ringbuf back-to-back, effect of sample rate"
53 header "Perfbuf back-to-back, effect of sample rate"
58 header "Ringbuf back-to-back, reserve+commit vs output"
|
| /kernel/linux/linux-6.6/drivers/mmc/host/ |
| D | sdhci-bcm-kona.c | 43 struct mutex write_lock; /* protect back to back writes */
72 * Back-to-Back register write needs a delay of 1ms at bootup (min 10uS) in sdhci_bcm_kona_sd_reset()
73 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_reset()
97 * Back-to-Back register write needs a delay of 1ms at bootup (min 10uS) in sdhci_bcm_kona_sd_init()
98 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_init()
119 * Back-to-Back register write needs a delay of min 10uS. in sdhci_bcm_kona_sd_card_emulate()
120 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_card_emulate()
|
| /kernel/linux/linux-5.10/drivers/mmc/host/ |
| D | sdhci-bcm-kona.c | 54 struct mutex write_lock; /* protect back to back writes */
83 * Back-to-Back register write needs a delay of 1ms at bootup (min 10uS) in sdhci_bcm_kona_sd_reset()
84 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_reset()
108 * Back-to-Back register write needs a delay of 1ms at bootup (min 10uS) in sdhci_bcm_kona_sd_init()
109 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_init()
130 * Back-to-Back register write needs a delay of min 10uS. in sdhci_bcm_kona_sd_card_emulate()
131 * Back-to-Back writes to same register needs delay when SD bus clock in sdhci_bcm_kona_sd_card_emulate()
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/hisilicon/hns3/hns3pf/ |
| D | hclge_mbx.c | 36 struct hclge_dev *hdev = vport->back; in hclge_gen_resp_to_vf()
95 struct hclge_dev *hdev = vport->back; in hclge_send_mbx_msg()
142 struct hclge_dev *hdev = vport->back; in hclge_inform_reset_assert_to_vf()
186 struct hclge_dev *hdev = vport->back; in hclge_get_ring_chain_from_mbx()
265 struct hclge_dev *hdev = vport->back; in hclge_query_ring_vector_map()
338 struct hclge_dev *hdev = vport->back; in hclge_set_vf_promisc_mode()
360 struct hclge_dev *hdev = vport->back; in hclge_set_vf_uc_mac_addr()
402 struct hclge_dev *hdev = vport->back; in hclge_set_vf_mc_mac_addr()
443 struct hclge_dev *hdev = vport->back; in hclge_set_vf_vlan_cfg()
494 struct hnae3_ae_dev *ae_dev = vport->back->ae_dev; in hclge_get_basic_info()
[all …]
|