Searched full:further (Results 1 – 25 of 2131) sorted by relevance
12345678910>>...86
/Linux-v5.15/tools/perf/pmu-events/arch/x86/skylakex/ |
D | virtual-memory.json | 39 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 49 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 59 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 69 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 120 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 130 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 140 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 150 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 190 …2M/4M/1G) caused by a code fetch. This implies it missed in the ITLB and further levels of TLB, bu… 220 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
/Linux-v5.15/tools/perf/pmu-events/arch/x86/cascadelakex/ |
D | virtual-memory.json | 39 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 49 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 59 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 69 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 120 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 130 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 140 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 150 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 190 …2M/4M/1G) caused by a code fetch. This implies it missed in the ITLB and further levels of TLB, bu… 220 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… [all …]
|
/Linux-v5.15/tools/perf/pmu-events/arch/x86/skylake/ |
D | virtual-memory.json | 18 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 38 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 120 …2M/4M/1G) caused by a code fetch. This implies it missed in the ITLB and further levels of TLB, bu… 140 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 150 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 160 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 170 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 180 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 199 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 239 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… [all …]
|
/Linux-v5.15/tools/perf/pmu-events/arch/x86/icelake/ |
D | virtual-memory.json | 21 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 58 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 70 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 82 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 107 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 131 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 143 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 155 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 179 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th…
|
/Linux-v5.15/tools/perf/pmu-events/arch/x86/icelakex/ |
D | virtual-memory.json | 9 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 21 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 33 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 82 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 94 …nd data stores. This implies address translations missed in the DTLB and further levels of TLB. Th… 106 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 155 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 167 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 179 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th…
|
/Linux-v5.15/Documentation/admin-guide/cgroup-v1/ |
D | blkio-controller.rst | 152 are further divided by the type of operation - read or write, sync 159 are further divided by the type of operation - read or write, sync 172 io_service_time > actual time elapsed. This time is further divided by 188 devices too. This time is further divided by the type of operation - 195 cgroup. This is further divided by the type of operation - read or 200 cgroup. This is further divided by the type of operation - read or 285 are further divided by the type of operation - read or write, sync 292 are further divided by the type of operation - read or write, sync
|
/Linux-v5.15/tools/perf/pmu-events/arch/x86/tigerlake/ |
D | virtual-memory.json | 32 …zes) caused by demand data loads. This implies it missed in the DTLB and further levels of TLB. Th… 43 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 54 …and data loads. This implies address translations missed in the DTLB and further levels of TLB. Th… 99 …es) caused by demand data stores. This implies it missed in the DTLB and further levels of TLB. Th… 166 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 177 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th… 188 …y a code fetch. This implies it missed in the ITLB (Instruction TLB) and further levels of TLB. Th…
|
/Linux-v5.15/Documentation/ABI/testing/ |
D | evm | 28 31 Disable further runtime modification of EVM policy 42 HMAC creation and disable all further modification of policy. 50 disable all further modification of policy. This option is now 106 a single period (.) will lock the xattr list from any further
|
/Linux-v5.15/arch/s390/include/uapi/asm/ |
D | dasd.h | 50 unsigned int reserved0; /* reserved for further use ,... */ 51 unsigned int reserved1; /* reserved for further use ,... */ 52 unsigned int reserved2; /* reserved for further use ,... */ 53 unsigned int reserved3; /* reserved for further use ,... */ 54 unsigned int reserved4; /* reserved for further use ,... */ 55 unsigned int reserved5; /* reserved for further use ,... */ 56 unsigned int reserved6; /* reserved for further use ,... */ 57 unsigned int reserved7; /* reserved for further use ,... */
|
/Linux-v5.15/drivers/staging/wfx/ |
D | Kconfig | 2 tristate "Silicon Labs wireless chips WF200 and further" 7 This is a driver for Silicons Labs WFxxx series (WF200 and further)
|
/Linux-v5.15/include/uapi/scsi/ |
D | scsi_bsg_ufs.h | 38 * @index: Index to further identify data B-2 39 * @selector: Index to further identify data B-3 93 * be no further reply information supplied.
|
/Linux-v5.15/drivers/net/ethernet/hisilicon/ |
D | Kconfig | 80 Hi1610 and further ICT SoC 111 SoCs and further upcoming SoCs. 129 SoCs and further upcoming SoCs.
|
/Linux-v5.15/Documentation/process/ |
D | embargoed-hardware-issues.rst | 17 mitigations can depend on microcode or firmware updates, which need further 100 response team can bring in further developers (domain experts) to address 135 further disclosure and coordination. 173 a sufficient starting point and further technical clarification is best 193 The initial response team will identify further experts from the Linux 242 reporting process and further handling. Ambassadors are not involved in the
|
/Linux-v5.15/drivers/net/ethernet/freescale/fman/ |
D | Kconfig | 22 internal resource leak thus stopping further packet processing. 27 stall further packet processing. The issue can occur with any
|
/Linux-v5.15/scripts/kconfig/tests/preprocess/escape/ |
D | Kconfig | 23 # The following should print "$(X)". It should not be expanded further. 33 # The following should print "$(X)". It should not be expanded further.
|
/Linux-v5.15/Documentation/userspace-api/media/v4l/ |
D | v4l2-selection-flags.rst | 46 - The configuration must not be propagated to any further processing 48 inside the subdevice to all further processing steps.
|
/Linux-v5.15/Documentation/core-api/ |
D | memory-hotplug.rst | 81 NOTIFY_DONE and NOTIFY_OK have no effect on the further processing. 85 further processing of the notification queue. 87 NOTIFY_STOP stops further processing of the notification queue.
|
/Linux-v5.15/block/partitions/ |
D | Kconfig | 133 here allows you to read these disklabels and further mount FreeBSD 152 to read these partition tables and further mount Solaris x86 163 VTOC and further mount UnixWare partitions read-only from within 232 read these partition tables and further mount SunOS partitions from
|
/Linux-v5.15/drivers/i2c/ |
D | Kconfig | 118 read Documentation/i2c/slave-interface.rst for further details. 126 Documentation/i2c/slave-eeprom-backend.rst for further details. 134 Documentation/i2c/slave-testunit-backend.rst for further details.
|
/Linux-v5.15/drivers/net/ethernet/sfc/ |
D | tx.h | 31 * packet, it must be one of them; no further checking required. in efx_tx_csum_type_skb() 43 * so it must be one of them. No need for further checks. in efx_tx_csum_type_skb()
|
/Linux-v5.15/include/linux/ |
D | lru_cache.h | 101 is moved further over the available indices with each such transaction. 217 /* annotate that the set is "dirty", possibly accumulating further 221 /* Locked, no further changes allowed. 227 * further references, to guarantee that eventually some refcnt will 279 * lock, which means there are no pending changes, and any further attempt to
|
/Linux-v5.15/drivers/usb/serial/ |
D | kobil_sct.h | 67 * PP = Further Attributes 75 * PP = Further Attributes
|
/Linux-v5.15/Documentation/networking/ |
D | dctcp.rst | 20 but might need further careful tweaking. 26 The algorithm is further described in detail in the following two
|
/Linux-v5.15/net/rxrpc/ |
D | misc.c | 38 * further packets aren't immediately received to decide when to send an IDLE 46 * limit is hit, we should generate an EXCEEDS_WINDOW ACK and discard further
|
/Linux-v5.15/Documentation/hwmon/ |
D | adt7462.rst | 31 response to the measured temperatures without further host intervention. This 39 the registers more often than once every other second. Further,
|
12345678910>>...86