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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:generally (Results 1 – 25 of 699) sorted by relevance

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

/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-interconnect.json	28 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 38 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 706 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 864 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 873 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 883 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 893 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 903 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 913 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 923 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
/linux/Documentation/rust/
H A D	quick-start.rst	`33 Arch Linux provides recent Rust releases and thus it should generally work out 43 recent Rust releases and thus they should generally work out of the box, e.g.:: 51 Fedora Linux provides recent Rust releases and thus it should generally work out 61 and thus it should generally work out of the box, e.g.:: 72 generally work out of the box, e.g.:: 85 they should generally work out of the box, e.g.:: 97 generally work out of the box, e.g.::`
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-interconnect.json	666 "PublicDescription": "Counts the number of times that an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into the Egress. This is a latency optimization, and should generally be the common case. If this value is less than the number of flits transferred, it implies that there was queueing getting onto the ring, and thus the transactions saw higher latency.", 824 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy.", 833 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors DRS flits only.", 843 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors DRS flits only.", 853 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors HOM flits only.", 863 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors HOM flits only.", 873 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCB flits only.", 883 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCB flits only.", 893 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCS flits only.", 903 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, whe [all...]
/linux/Documentation/admin-guide/pm/
H A D	intel_pstate.rst	81 names of some of those governors. Moreover, confusingly enough, they generally 182 registers of the CPU. It generally selects P-states proportional to the 266 In turn, the P-states below the turbo threshold generally are sustainable. In 273 but the maximum P-state that can be set for them generally depends on the number 291 generally causes turbo P-states to be set more often when ``intel_pstate`` is 320 Generally, ways to obtain that information are specific to the processor model 350 causes the CPU scheduler to generally prefer more performant CPUs, so the less 359 playback, which is not generally desirable. While there is no other viable 370 ``intel_pstate`` by default on hybrid processors without SMT. CAS generally 381 balanced because the more performant CPUs are generally less energy-efficient [all …]
H A D	cpufreq.rst	42 the utilization of the system generally changes over time, that has to be done 160 scheduler tick or generally whenever the CPU utilization may change (from the 215 and their behavior generally does not depend on what scaling driver is in use 409 generally is regarded as a part of the CPU scheduler, so it can access the 451 This governor generally is regarded as a replacement for the older `ondemand`_ 481 It generally selects CPU frequencies proportional to the estimated load, so that 665 The frequency boost mechanism is generally intended to help to achieve optimum 676 conditions. Generally, the processor's energy consumption increases
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-interconnect.json	666 "PublicDescription": "Counts the number of times that an incoming flit was able to bypass the flit buffer and pass directly across the BGF and into the Egress. This is a latency optimization, and should generally be the common case. If this value is less than the number of flits transferred, it implies that there was queueing getting onto the ring, and thus the transactions saw higher latency.", 823 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy.", 832 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors DRS flits only.", 842 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors DRS flits only.", 852 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors HOM flits only.", 862 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors HOM flits only.", 872 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCB flits only.", 882 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCB flits only.", 892 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCS flits only.", 902 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, whe [all...]
/linux/Documentation/power/
H A D	suspend-and-interrupts.rst	`12 Device interrupt request lines (IRQs) are generally disabled during system 61 System wakeup interrupts generally need to be configured to wake up the system 72 After wakeup, it generally is better to disable that input to prevent the 128 interrupt source and an IRQF_NO_SUSPEND interrupt source does not generally`
H A D	freezing-of-tasks.rst	`38 tasks are generally frozen before kernel threads. 115 Generally speaking, there is a couple of reasons to use the freezing of tasks: 134 devices are deactivated, because we generally need them for swapping out. 217 tasks, since it generally exists anyway.`
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-interconnect.json	28 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 38 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 425 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 523 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 692 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 701 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 710 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 719 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 728 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 737 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … [all …]
/linux/Documentation/devicetree/bindings/memory-controllers/ddr/
H A D	jedec,lpddr-props.yaml	`10 Different LPDDR types generally use the same properties and only differ in the 12 reused for each type. Nodes using this schema should generally be nested under`
/linux/Documentation/i2c/busses/
H A D	i2c-ali15x3.rst	`61 - Gigabyte GA-5AX (Generally doesn't work because the BIOS doesn't 121 SMBus. Therefore the SMBus hangs can generally be avoided`
/linux/Documentation/mm/
H A D	active_mm.rst	`80 should generally just do 85 we have a user context", and is generally done by the page fault handler`
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	uncore-interconnect.json	2690 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2723 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2756 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2767 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2800 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2833 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2932 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… 2965 …mote UPI credits : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2998 … lack of remote UPI credits : Data Response (WB) messages on BL. WB is generally used to transmit… 3009 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… [all …]
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A D	uncore-interconnect.json	2690 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2723 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2756 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2767 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2800 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2833 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2932 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… 2965 …mote UPI credits : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2998 … lack of remote UPI credits : Data Response (WB) messages on BL. WB is generally used to transmit… 3009 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… [all …]
/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A D	uncore-io.json	13 …equest for 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 29 …request of 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 516 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 528 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 540 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 552 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 590 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 602 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 614 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 626 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an… [all …]
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	uncore-io.json	13 …equest for 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 29 …request of 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 516 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 528 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 540 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 552 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 590 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 602 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 614 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 626 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an… [all …]
/linux/Documentation/process/
H A D	volatile-considered-harmful.rst	`71 waiting is generally an anti-social act to begin with. 104 Patches to remove volatile variables are generally welcome - as long as`
/linux/drivers/thermal/ti-soc-thermal/
H A D	TODO	`9 generally:`
/linux/arch/x86/include/uapi/asm/
H A D	posix_types_64.h	`6 * This file is generally used by user-level software, so you need to`
H A D	posix_types_x32.h	`10 * These types should generally match the ones used by the 64-bit kernel,`
/linux/arch/powerpc/include/uapi/asm/
H A D	posix_types.h	`6 * This file is generally used by user-level software, so you need to`
/linux/arch/alpha/include/uapi/asm/
H A D	posix_types.h	`6 * This file is generally used by user-level software, so you need to`
/linux/include/linux/
H A D	pm.h	68 * subsystem and generally the rest of the kernel is supposed to prevent 87 * starting to invoke suspend callbacks for any of them, so generally 119 * type), but generally the device must be quiescent after subsystem-level 130 * depends on the device's subsystem, but generally the driver is expected 187 * It generally is expected that the device will be in a low-power state 194 * wakeup signals, in which case it generally is not necessary to define 280 * actions to be performed by a device driver's callbacks generally depend on
/linux/arch/parisc/include/uapi/asm/
H A D	posix_types.h	`6 * This file is generally used by user-level software, so you need to`
/linux/Documentation/w1/slaves/
H A D	w1_therm.rst	`135 GX20MH01 device shares family number 0x28 with DS18*20. The device is generally 142 MAX31850 device shares family number 0x3B with DS1825. The device is generally`

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