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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/linux/tools/perf/pmu-events/arch/x86/lunarlake/
H A D	memory.json	3 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 11 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 17 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 25 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 31 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 39 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 45 …ly selected loads when the latency from first dispatch to completion is greater than 2048 cycles.", 53 …ncy from first dispatch to completion is greater than 2048 cycles. Reported latency may be longer… 59 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 67 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… [all …]
/linux/tools/perf/pmu-events/arch/x86/graniterapids/
H A D	memory.json	68 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 76 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 81 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 89 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 94 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 102 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 107 …ly selected loads when the latency from first dispatch to completion is greater than 2048 cycles.", 115 …ncy from first dispatch to completion is greater than 2048 cycles. Reported latency may be longer… 120 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 128 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… [all …]
/linux/tools/perf/pmu-events/arch/x86/tigerlake/
H A D	memory.json	21 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 29 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 34 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 42 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 47 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 55 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 60 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 68 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … 73 …domly selected loads when the latency from first dispatch to completion is greater than 4 cycles.", 81 …tency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer … [all …]
/linux/tools/perf/pmu-events/arch/x86/meteorlake/
H A D	memory.json	139 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 147 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 153 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 161 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 167 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 175 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 181 …ly selected loads when the latency from first dispatch to completion is greater than 2048 cycles.", 189 …ncy from first dispatch to completion is greater than 2048 cycles. Reported latency may be longer… 195 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 203 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… [all …]
/linux/tools/perf/pmu-events/arch/x86/alderlake/
H A D	memory.json	129 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 137 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 143 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 151 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 157 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 165 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 171 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 179 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 185 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 193 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … [all …]
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	memory.json	59 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 67 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 72 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 80 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 85 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 93 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 98 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 106 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 111 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 119 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … [all …]
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A D	memory.json	59 …ly selected loads when the latency from first dispatch to completion is greater than 1024 cycles.", 67 …ncy from first dispatch to completion is greater than 1024 cycles. Reported latency may be longer… 72 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 80 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 85 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 93 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 98 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 106 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 111 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 119 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … [all …]
/linux/drivers/gpu/drm/vc4/tests/
H A 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/Documentation/ABI/testing/
H A 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/tools/perf/pmu-events/arch/x86/rocketlake/
H A D	memory.json	84 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 92 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 97 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 105 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 110 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 118 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 123 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 131 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … 136 …domly selected loads when the latency from first dispatch to completion is greater than 4 cycles.", 144 …tency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer … [all …]
/linux/tools/perf/pmu-events/arch/x86/icelake/
H A D	memory.json	84 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 92 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 97 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 105 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 110 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 118 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 123 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 131 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … 136 …domly selected loads when the latency from first dispatch to completion is greater than 4 cycles.", 144 …tency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer … [all …]
/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A D	memory.json	21 …mly selected loads when the latency from first dispatch to completion is greater than 128 cycles.", 29 …ency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer… 34 …omly selected loads when the latency from first dispatch to completion is greater than 16 cycles.", 42 …ency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer … 47 …mly selected loads when the latency from first dispatch to completion is greater than 256 cycles.", 55 …ency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer… 60 …omly selected loads when the latency from first dispatch to completion is greater than 32 cycles.", 68 …ency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer … 73 …domly selected loads when the latency from first dispatch to completion is greater than 4 cycles.", 81 …tency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer … [all …]
/linux/tools/perf/pmu-events/arch/powerpc/power8/
H A 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/drivers/net/can/dev/
H A 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/Documentation/filesystems/
H A 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/arch/arm/nwfpe/
H A 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/drivers/net/ethernet/intel/i40e/
H A 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/tools/testing/selftests/net/forwarding/
H A 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/arch/x86/math-emu/
H A 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 …]
H A D	reg_round.S	49 \| smaller than the magnitude of the correct exact result by an amount \| 50 \| greater than zero and less than one ls bit of the significand. \| 53 \| less than 0x80000000 <=> the significand is less than 1/2 an ls \| 54 \| bit smaller than the magnitude of the \| 57 \| smaller than the magnitude of the true \| 59 \| greater than 0x80000000 <=> the significand is more than 1/2 an ls \| 60 \| bit smaller than the magnitude of the \| 214 jc LCheck_truncate_24 /* less than half, no increment needed / 216 jne LGreater_Half_24 / greater than half, increment needed / 220 jnz LGreater_Half_24 / greater than half, increment needed */ [all …]
/linux/Documentation/networking/
H A 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/Documentation/driver-api/thermal/
H A 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
/linux/drivers/gpu/drm/i915/display/
H A D	intel_tv_regs.h	39 /* Selects progressive mode rather than interlaced / 247 / Offset of the start of vsync in field 1, measured in one less than the 253 * Offset of the start of vsync in field 2, measured in one less than the 265 /* Offset of the start of equalization in field 1, measured in one less than 271 * Offset of the start of equalization in field 2, measured in one less than 279 * Offset to start of vertical colorburst, measured in one less than the 285 * Offset to the end of vertical colorburst, measured in one less than the 293 * Offset to start of vertical colorburst, measured in one less than the 299 * Offset to the end of vertical colorburst, measured in one less than the 307 * Offset to start of vertical colorburst, measured in one less than the [all …]
/linux/fs/ntfs3/lib/
H A D	decompress_common.c	43 * a codeword shorter than 'max_codeword_len' will have multiple entries 56 * less than or equal to 'max_codeword_len'. Then, only codewords of 84 * 'lens' array. Must be less than or equal to 2048. 88 * less than or equal to 13. 98 * All entries in 'lens' must be less than or equal to this value. 99 * This must be less than or equal to 23. 179 * max_codeword_len is the number of codewords shorter than 'len' bits. in make_huffman_decode_table() 187 * than 'num_syms' entries in 'sorted_syms' may be filled. in make_huffman_decode_table() 225 * there are codewords longer than table_bits for which we must in make_huffman_decode_table() 248 * fewer than this may actually be needed. in make_huffman_decode_table() [all …]
/linux/drivers/target/iscsi/
H A D	iscsi_target_nodeattrib.c	51 pr_err("Requested DataOut Timeout %u larger than" in iscsit_na_dataout_timeout() 56 pr_err("Requested DataOut Timeout %u smaller than" in iscsit_na_dataout_timeout() 77 " than maximum %u", dataout_timeout_retries, in iscsit_na_dataout_timeout_retries() 82 " than minimum %u", dataout_timeout_retries, in iscsit_na_dataout_timeout_retries() 107 pr_err("Requested NopIn Timeout %u larger than maximum" in iscsit_na_nopin_timeout() 112 pr_err("Requested NopIn Timeout %u smaller than" in iscsit_na_nopin_timeout() 158 " than maximum %u\n", nopin_response_timeout, in iscsit_na_nopin_response_timeout() 163 " than minimum %u\n", nopin_response_timeout, in iscsit_na_nopin_response_timeout()

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