Home
last modified time | relevance | path

Searched full:excessive (Results 1 – 25 of 307) sorted by relevance

12345678910>>...13

/linux-6.14.4/fs/quota/
Dquotaio_v2.h46 __le64 dqb_btime; /* time limit for excessive disk use */
47 __le64 dqb_itime; /* time limit for excessive inode use */
59 __le64 dqb_btime; /* time limit for excessive disk use */
60 __le64 dqb_itime; /* time limit for excessive inode use */
Dquotaio_v1.h30 unsigned long dqb_btime; /* time limit for excessive disk use */
31 unsigned long dqb_itime; /* time limit for excessive inode use */
/linux-6.14.4/drivers/crypto/intel/qat/qat_common/
Dadf_clock.c62 dev_err(&GET_DEV(accel_dev), "Excessive clock measure delay\n"); in measure_clock()
81 dev_err(&GET_DEV(accel_dev), "Excessive clock measure delay\n"); in measure_clock()
/linux-6.14.4/Documentation/scheduler/
Dsched-nice-design.rst45 we felt to be a bit excessive. Excessive _not_ because it's too small of
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-bus-iio-thermocouple6 is protected from excessive voltages applied to the thermocouple
/linux-6.14.4/Documentation/admin-guide/thermal/
Dintel_powerclamp.rst164 When an excessive amount of wakeups occurs during idle, an
213 To compensate for excessive amounts of wakeup during idle, additional
238 forced idle time, excessive interrupts could result in less
/linux-6.14.4/Documentation/accounting/
Dpsi.rst16 excessive overcommit.
109 window size must be a multiple of 2s, in order to prevent excessive resource
/linux-6.14.4/kernel/sched/
DMakefile11 # Disable KCSAN to avoid excessive noise and performance degradation. To avoid
/linux-6.14.4/drivers/net/ethernet/marvell/octeon_ep/
Doctep_tx.h76 /* Packets dropped due to excessive collisions */
79 /* Packets dropped due to excessive deferral */
/linux-6.14.4/drivers/scsi/elx/libefc/
Defclib.c12 * influence the I/O path, so excessive locking doesn't impact I/O performance.
/linux-6.14.4/Documentation/process/
D7.AdvancedTopics.rst79 Excessive use of this capability can lead to other problems, though, beyond
181 will check for problematic locking, excessive stack usage, possible
/linux-6.14.4/drivers/gpu/drm/i915/gt/uc/
Dintel_guc_fw.c260 guc_warn(guc, "excessive init time: %lldms! [status = 0x%08X, count = %d, ret = %d]\n", in guc_wait_ucode()
262 …guc_warn(guc, "excessive init time: [freq = %dMHz, before = %dMHz, perf_limit_reasons = 0x%08X]\n", in guc_wait_ucode()
/linux-6.14.4/Documentation/core-api/
Dgfp_mask-from-fs-io.rst24 deeper consideration which leads to problems because an excessive use
/linux-6.14.4/drivers/net/ethernet/pasemi/
Dpasemi_mac_ethtool.c42 { "tx-excessive-collisions" },
/linux-6.14.4/Documentation/arch/x86/
Dintel-hfi.rst35 excessive heat, the HFI may reflect reduced performance on specific CPUs.
/linux-6.14.4/drivers/net/arcnet/
DKconfig65 1=excessive nak
/linux-6.14.4/arch/x86/crypto/
Dtwofish_glue_3way.c130 * implementation because excessive uses of 64bit rotate and in is_blacklisted_cpu()
/linux-6.14.4/arch/sparc/kernel/
Dpsycho_common.c329 "Excessive Retries" : in psycho_pcierr_intr()
350 printk("(Excessive Retries)"); in psycho_pcierr_intr()
/linux-6.14.4/include/linux/
Dxz.h175 * decoded to avoid allocating excessive amount of memory for the dictionary.
180 * headers. This way excessive allocations can be avoided while still
/linux-6.14.4/arch/x86/realmode/rm/
Dreboot.S90 * Most of this work is probably excessive, but it is what is tested.
/linux-6.14.4/include/acpi/
Dnhlt.h94 * initialization and removal respectively to avoid excessive mapping
/linux-6.14.4/tools/include/linux/
Doverflow.h20 * The slightly excessive casting in type_min is to make sure the
/linux-6.14.4/fs/ext4/
Dfsync.c19 * and excessive __inline__s.
/linux-6.14.4/lib/
DKconfig.kasan160 With Clang, stack instrumentation has a problem that causes excessive
/linux-6.14.4/include/net/
Drstreason.h160 * This code indicates that there is an excessive amount of data

12345678910>>...13