than (full) in projects: linux-6.6 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:than (Results 1 – 25 of 5443) sorted by relevance

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

/linux-6.15/tools/perf/pmu-events/arch/x86/tigerlake/
D	memory.json	21 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 28 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 33 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 40 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 45 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 52 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 57 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 64 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … 69 …domly selected loads when the latency from first dispatch to completion is greater than 4 cycles.", 76 …tency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer … [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/meteorlake/
D	memory.json	139 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 146 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 152 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 159 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 165 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 172 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 178 …ly selected loads when the latency from first dispatch to completion is greater than 2048 cycles.", 185 …ncy from first dispatch to completion is greater than 2048 cycles. Reported latency may be longer… 191 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 198 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/graniterapids/
D	memory.json	68 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 75 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 80 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 87 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 92 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 99 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 104 …ly selected loads when the latency from first dispatch to completion is greater than 2048 cycles.", 111 …ncy from first dispatch to completion is greater than 2048 cycles. Reported latency may be longer… 116 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 123 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/arrowlake/
D	memory.json	159 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 166 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 172 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 179 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 185 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 192 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 198 …ly selected loads when the latency from first dispatch to completion is greater than 2048 cycles.", 205 …ncy from first dispatch to completion is greater than 2048 cycles. Reported latency may be longer… 211 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 218 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/alderlake/
D	memory.json	129 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 136 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 142 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 149 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 155 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 162 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 168 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 175 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 181 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 188 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/lunarlake/
D	memory.json	159 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 166 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 172 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 179 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 185 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 192 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 198 …ly selected loads when the latency from first dispatch to completion is greater than 2048 cycles.", 205 …ncy from first dispatch to completion is greater than 2048 cycles. Reported latency may be longer… 211 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 218 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/emeraldrapids/
D	memory.json	59 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 66 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 71 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 78 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 83 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 90 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 95 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 102 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 107 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 114 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/sapphirerapids/
D	memory.json	59 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 66 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 71 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 78 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 83 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 90 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 95 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 102 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 107 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 114 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … [all …]
/linux-6.15/drivers/gpu/drm/vc4/tests/
D	vc4_test_pv_muxing.c	295 VC4_PV_MUXING_TEST("More than 3 outputs: DSI0, HDMI0, DSI1, TXP", 300 VC4_PV_MUXING_TEST("More than 3 outputs: DSI0, VEC, DSI1, TXP", 305 VC4_PV_MUXING_TEST("More than 3 outputs: DPI, HDMI0, DSI1, TXP", 310 VC4_PV_MUXING_TEST("More than 3 outputs: DPI, VEC, DSI1, TXP", 490 VC5_PV_MUXING_TEST("More than 3 outputs: DPI, VEC, TXP, DSI1", 495 VC5_PV_MUXING_TEST("More than 3 outputs: DPI, VEC, TXP, HDMI0", 500 VC5_PV_MUXING_TEST("More than 3 outputs: DPI, VEC, TXP, HDMI1", 505 VC5_PV_MUXING_TEST("More than 3 outputs: DPI, VEC, DSI1, HDMI0", 510 VC5_PV_MUXING_TEST("More than 3 outputs: DPI, VEC, DSI1, HDMI1", 515 VC5_PV_MUXING_TEST("More than 3 outputs: DPI, VEC, HDMI0, HDMI1", [all …]
/linux-6.15/Documentation/ABI/testing/
D	sysfs-tty	`30 sysfs rather than via ioctls. 39 sysfs rather than via ioctls. 48 sysfs rather than via ioctls. 57 sysfs rather than via ioctls. 66 sysfs rather than via ioctls. 75 sysfs rather than via ioctls. 84 sysfs rather than via ioctls. 93 sysfs rather than via ioctls. 105 sysfs rather than via ioctls. 114 sysfs rather than via ioctls. [all …]`
/linux-6.15/tools/perf/pmu-events/arch/x86/icelake/
D	memory.json	84 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 91 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 96 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 103 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 108 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 115 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 120 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 127 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … 132 …domly selected loads when the latency from first dispatch to completion is greater than 4 cycles.", 139 …tency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer … [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/rocketlake/
D	memory.json	84 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 91 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 96 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 103 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 108 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 115 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 120 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 127 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … 132 …domly selected loads when the latency from first dispatch to completion is greater than 4 cycles.", 139 …tency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer … [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/icelakex/
D	memory.json	21 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 28 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 33 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 40 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 45 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 52 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 57 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 64 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … 69 …domly selected loads when the latency from first dispatch to completion is greater than 4 cycles.", 76 …tency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer … [all …]
/linux-6.15/tools/perf/pmu-events/arch/powerpc/power8/
D	memory.json	53 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump … 54 …"PublicDescription": "Final Pump Scope(Group) to get data sourced, ended up larger than Initial Pu… 59 …"BriefDescription": "Final Pump Scope (Group) ended up larger than Initial Pump Scope (Chip) for a… 60 …"PublicDescription": "Final Pump Scope(Group) to get data sourced, ended up larger than Initial Pu… 84 …"PublicDescription": "Final Pump Scope(system) to get data sourced, ended up larger than Initial P… 89 …"BriefDescription": "Final Pump Scope (system) ended up larger than Initial Pump Scope (Chip/Group… 90 …"PublicDescription": "Final Pump Scope(system) to get data sourced, ended up larger than Initial P… 119 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump … 120 …"PublicDescription": "Final Pump Scope(Group) to get data sourced, ended up larger than Initial Pu… 125 …"BriefDescription": "Final Pump Scope (Group) ended up larger than Initial Pump Scope (Chip) for a… [all …]
/linux-6.15/drivers/net/can/dev/
D	bittiming.c	22 NL_SET_ERR_MSG_FMT(extack, "sjw: %u greater than max sjw: %u", in can_sjw_check() 29 "sjw: %u greater than phase-seg1: %u", in can_sjw_check() 36 "sjw: %u greater than phase-seg2: %u", in can_sjw_check() 59 NL_SET_ERR_MSG_FMT(extack, "prop-seg + phase-seg1: %u less than tseg1-min: %u", in can_fixup_bittiming() 64 NL_SET_ERR_MSG_FMT(extack, "prop-seg + phase-seg1: %u greater than tseg1-max: %u", in can_fixup_bittiming() 69 NL_SET_ERR_MSG_FMT(extack, "phase-seg2: %u less than tseg2-min: %u", in can_fixup_bittiming() 74 NL_SET_ERR_MSG_FMT(extack, "phase-seg2: %u greater than tseg2-max: %u", in can_fixup_bittiming() 95 NL_SET_ERR_MSG_FMT(extack, "resulting brp: %u less than brp-min: %u", in can_fixup_bittiming() 100 NL_SET_ERR_MSG_FMT(extack, "resulting brp: %u greater than brp-max: %u", in can_fixup_bittiming()
/linux-6.15/tools/perf/pmu-events/arch/arm64/arm/neoverse-n3/
D	tlb.json	28 …the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD. … 32 …the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD. … 44 …the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD. … 48 … the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD." 52 …the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD. … 56 … the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD." 60 …. The set of large pages is defined as all pages with a final size higher than or equal to 2MB. Tr… 64 …. The set of large pages is defined as all pages with a final size higher than or equal to 2MB. Tr… 68 …e. The set of small pages is defined as all pages with a final size lower than 2MB. Translation ta… 72 …e. The set of small pages is defined as all pages with a final size lower than 2MB. Translation ta…
/linux-6.15/Documentation/filesystems/
D	inotify.rst	`33 An fd-per-watch quickly consumes more file descriptors than are allowed, 34 more fd's than are feasible to manage, and more fd's than are optimally 37 A watch consumes less memory than an open file, separating the number 72 Additionally, it _is_ possible to more than one instance and 73 juggle more than one queue and thus more than one associated fd. There 75 process can easily want more than one queue.`
/linux-6.15/tools/perf/pmu-events/arch/arm64/arm/neoverse-v3/
D	tlb.json	28 …the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD. … 32 …the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD. … 92 …the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD. … 96 … the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD." 100 …the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD. … 104 … the translation ended up taking a translation fault for reasons different than EPD, E0PD and NFD." 108 …. The set of large pages is defined as all pages with a final size higher than or equal to 2MB. Tr… 112 …. The set of large pages is defined as all pages with a final size higher than or equal to 2MB. Tr… 116 …e. The set of small pages is defined as all pages with a final size lower than 2MB. Translation ta… 120 …e. The set of small pages is defined as all pages with a final size lower than 2MB. Translation ta… [all …]
/linux-6.15/drivers/net/ethernet/intel/i40e/
D	i40e_lan_hmc.h	`16 * The sizes of the variables may be larger than needed due to crossing byte 23 u16 cpuid; /* bigger than needed, see above for reason / 27 u16 dbuff; / bigger than needed, see above for reason / 29 u16 hbuff; / bigger than needed, see above for reason / 38 u32 rxmax; / bigger than needed, see above for reason / 43 u16 lrxqthresh; / bigger than needed, see above for reason / 49 The sizes of the variables may be larger than needed due to crossing byte`
/linux-6.15/arch/arm/nwfpe/
D	fpa11_cprt.c	34 /* Hint to GCC that we'd like a jump table rather than a load of CMPs / in EmulateCPRT() 157 comparison (cheaper than an 80-bit one). / in PerformComparison() 221 /* test for less than condition / in PerformComparison() 229 / test for greater than or equal condition / in PerformComparison() 247 / test for less than condition / in PerformComparison() 255 / test for greater than or equal condition / in PerformComparison() 268 / test for less than condition / in PerformComparison() 276 / test for greater than or equal condition / in PerformComparison() 294 / test for less than condition / in PerformComparison() 302 / test for greater than or equal condition */ in PerformComparison() [all …]
/linux-6.15/tools/testing/selftests/net/forwarding/
D	tc_tunnel_key.sh	119 check_err $? "packet smaller than MTU was not tunneled" 123 check_err $? "packet bigger than MTU matched nofrag (nofrag was set)" 125 check_err $? "packet bigger than MTU matched firstfrag (nofrag was set)" 127 check_err $? "packet bigger than MTU matched nofirstfrag (nofrag was set)" 133 check_err $? "packet bigger than MTU matched nofrag (nofrag was unset)" 135 check_err $? "packet bigger than MTU didn't match firstfrag (nofrag was unset) " 137 check_err $? "packet bigger than MTU didn't match nofirstfrag (nofrag was unset) "
/linux-6.15/Documentation/networking/
D	ipsec.rst	`20 defined in section 3, is not smaller than the size of the original 26 datagram fragmentation when the expanded datagram is larger than the 31 where IP datagrams of size smaller than the threshold are sent in the 37 is smaller than the threshold or the compressed len is larger than original`
/linux-6.15/arch/x86/math-emu/
D	README	74 a value of pi which is accurate to more than 128 bits. As a consequence, 75 the reduced argument is accurate to more than 64 bits for arguments up 76 to a few pi, and accurate to more than 64 bits for most arguments, 96 therefore now fully re-entrant, rather than having just the restricted 103 are fewer than those which applied to the 1.xx series of the emulator. 113 (a) the operands have a higher precision than the current setting of the 116 (c) the magnitude of the exact result (before rounding) is less than 2^-16382. 146 greater than 0xffff appear to be illegal in vm86 mode but are quite 229 than that of an Intel 80486 FPU. 241 arguments greater than pi/4 can be thought of as being related to the [all …]
/linux-6.15/tools/perf/Documentation/
D	perf-ftrace.txt	89 by using this option more than once. The function argument also 96 argument. Like -T option, this can be used more than once to 111 than once to specify multiple functions. It will be passed to 119 executed from the given function. This can be used more than once to 160 -n/--use-nsec). The setting is ignored if the value results in more than 169 Multiple functions can be given by using this option more than once. 176 can be used more than once to specify multiple functions (or glob 183 can be used more than once to specify multiple functions. It will be 191 can be used more than once to specify multiple functions. It will be
/linux-6.15/Documentation/driver-api/thermal/
D	cpu-idle-cooling.rst	26 budget lower than the requested one and under-utilize the CPU, thus 28 with a power less than the requested power budget and the next OPP 48 belong to the same cluster, with a duration greater than the cluster 132 - It is less than or equal to the latency we tolerate when the 137 - It is greater than the idle state’s target residency we want to go 148 ... which is more than the sustainable power (or there is something 177 Practically, if the running power is less than the targeted power, we 180 running power greater than the targeted power. 192 * The injected idle duration must be greater than the idle state

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