Home
last modified time | relevance | path

Searched full:feasible (Results 1 – 25 of 70) sorted by relevance

123

/linux-6.14.4/Documentation/admin-guide/LSM/
DSafeSetID.rst29 generally feasible way in Linux to restrict the potential UIDs that a user can
73 Unfortunately, it is not generally feasible to use user namespaces in isolation,
/linux-6.14.4/Documentation/filesystems/ext4/
Dallocators.rst39 same block group as the directory, when feasible. The working assumption
/linux-6.14.4/scripts/dummy-tools/
Dgcc17 # However, it is not feasible to get a full-featured compiler for every arch.
/linux-6.14.4/Documentation/admin-guide/
Dkernel-per-CPU-kthreads.rst300 the need for RCU priority boosting. This approach is feasible
304 is feasible only if your workload never requires RCU priority
/linux-6.14.4/Documentation/hwmon/
Dhwmon-kernel-api.rst330 DEVICE_ATTR_{RW,RO,WO} to declare such attributes. This is feasible if an
341 feasible. Standard permissions are 0644 for SENSOR_DEVICE_ATTR[_2]_RW,
/linux-6.14.4/Documentation/arch/arm/nwfpe/
Dtodo.rst36 determine if it is feasible.
/linux-6.14.4/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.yaml20 standard multimaster mode not feasible.
/linux-6.14.4/Documentation/filesystems/
Dinotify.rst34 more fd's than are feasible to manage, and more fd's than are optimally
/linux-6.14.4/tools/testing/selftests/bpf/progs/
Dexceptions.c142 * but if the need arises this restriction is technically feasible to relax in
/linux-6.14.4/Documentation/driver-api/surface_aggregator/clients/
Ddtx.rst209 - Detachment not feasible due to low clipboard battery.
345 * ``SDTX_DETACH_NOT_FEASIBLE``: Detachment not feasible due to low clipboard
/linux-6.14.4/include/linux/
Dhugetlb.h878 * and still feasible enough to be migratable. Just the presence
879 * in movable zone does not make the migration feasible.
883 * feasible to migrate them from movable zone.
Dpage_ref.h23 * feasible. Instead we have to open code the static key functions.
Drbtree.h153 * on-stack dummy object, which might not be feasible due to object size.
/linux-6.14.4/arch/arm/include/asm/
Dopcodes.h170 * Before using these macros, consider carefully whether it is feasible
/linux-6.14.4/Documentation/gpu/
Ddrm-usage-stats.rst12 feasible `top(1)` like userspace monitoring tools.
/linux-6.14.4/sound/soc/spear/
Dspdif_out.c123 * The clock is multiplied by 10 to bring it to feasible range in spdif_out_hw_params()
/linux-6.14.4/Documentation/networking/
Dmsg_zerocopy.rst215 Copy avoidance is not always feasible. Devices that do not support
/linux-6.14.4/drivers/watchdog/
Dshwdt.c51 * feasible are the 4096 and the 2048 divisors, which yield 5.25 and 2.62ms
/linux-6.14.4/arch/powerpc/perf/
Dcore-book3s.c963 * and see if any combination of alternative codes is feasible.
964 * The feasible set is returned in event_id[].
1055 * No feasible alternative, backtrack in power_check_constraints()
1063 * Found a feasible alternative for event_id i, in power_check_constraints()
1078 /* OK, we have a feasible combination, tell the caller the solution */ in power_check_constraints()
1635 * and check whether the total set is still feasible. in power_pmu_add()
/linux-6.14.4/arch/mips/math-emu/
Ddsemul.c32 * - Actually emulating all instructions isn't feasible. We would need to
/linux-6.14.4/tools/include/linux/
Drbtree.h168 * on-stack dummy object, which might not be feasible due to object size.
/linux-6.14.4/arch/arc/include/asm/
Dentry-compact.h159 * The only feasible way is to make sure this L2 happened in
/linux-6.14.4/Documentation/power/
Dfreezing-of-tasks.rst235 However, if that is not feasible, and grabbing 'system_transition_mutex' is
/linux-6.14.4/Documentation/security/
Dself-protection.rst108 without ``CONFIG_COMPAT``. However, this is rarely a feasible scenario.
/linux-6.14.4/net/mac80211/
Dlink.c401 * not really feasible. in _ieee80211_set_active_links()

123