Searched refs:suboptimal (Results 1 – 16 of 16) sorted by relevance
128 struct cpufreq_frequency_table suboptimal = { in cpufreq_table_index_unsorted() local142 suboptimal.frequency = ~0; in cpufreq_table_index_unsorted()167 if (freq <= suboptimal.frequency) { in cpufreq_table_index_unsorted()168 suboptimal.frequency = freq; in cpufreq_table_index_unsorted()169 suboptimal.driver_data = i; in cpufreq_table_index_unsorted()180 if (freq >= suboptimal.frequency) { in cpufreq_table_index_unsorted()181 suboptimal.frequency = freq; in cpufreq_table_index_unsorted()182 suboptimal.driver_data = i; in cpufreq_table_index_unsorted()198 if (suboptimal.driver_data > i) { in cpufreq_table_index_unsorted()203 index = suboptimal.driver_data; in cpufreq_table_index_unsorted()
9 static library generates a slightly suboptimal code, this is what all
42 + # linker jobs. This is still suboptimal to a potential dynamic
178 boundary, it is currently possibly suboptimal to read or execute files
78 Aside from the clipped coordinates right above there's a few suboptimal things
1050 to suboptimal I/O performance for drivers using coherent DMA.
342 may lead to suboptimal results in some cases).
2898 barriers for this use-case would be possible but is often suboptimal.
2412 the same local network. This mode is likely to be suboptimal
3168 suboptimal code can result if this hook returns true for the corresponding\n\
33106 which includes both of them. Otherwise you will get suboptimal code, or41577 suboptimal code can result if this hook returns true for the
14567 switch. Additionally, it makes the code suboptimal. Use it to
9110 let know the client that the buffer format/modifier is suboptimal.34894 That's clearly suboptimal, given Xwayland is generally designed149741 xkb: mixing up src and dst in a memcpy is suboptimal.