Home
last modified time | relevance | path

Searched full:taking (Results 1 – 25 of 1109) sorted by relevance

12345678910>>...45

/linux-6.12.1/net/mac80211/
DKconfig216 is taking part in a mesh network).
229 is taking part in a mesh network).
242 is taking part in a mesh network).
254 synchronization debugging messages (when mac80211 is taking part in a
265 channel switch debugging messages (when mac80211 is taking part in a
276 powersave debugging messages (when mac80211 is taking part in a
/linux-6.12.1/tools/testing/selftests/livepatch/
Dtest-state.sh46 start_test "taking over system state modification"
72 $MOD_LIVEPATCH2: fix_console_loglevel: taking over the console_loglevel change
117 $MOD_LIVEPATCH3: fix_console_loglevel: taking over the console_loglevel change
128 $MOD_LIVEPATCH2: fix_console_loglevel: taking over the console_loglevel change
/linux-6.12.1/arch/powerpc/include/asm/
Ddbell.h49 /* sync after taking message interrupt */
52 /* sync is not required when taking messages from the same core */ in ppc_msgsync()
85 /* sync after taking message interrupt */
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-class-bdi68 situations where we want to avoid one device taking all or
82 one device taking all or most of the write-back cache. For example
109 situations where we want to avoid one device taking all or
/linux-6.12.1/fs/ocfs2/
Dmmap.c66 * 2) pagecache truncates when another is taking EX lock against in __ocfs2_page_mkwrite()
71 * taking the page lock inside of ocfs2_write_begin_nolock(). in __ocfs2_page_mkwrite()
127 * node. Taking the data lock will also ensure that we don't in ocfs2_page_mkwrite()
/linux-6.12.1/fs/xfs/
Dxfs_hooks.h16 * code patching to eliminate the overhead of taking the rwsem in
21 * Note: Patching the kernel code requires taking the cpu hotplug lock. Other
/linux-6.12.1/Documentation/filesystems/
Dpath-lookup.txt25 All the above algorithms required taking a lock and reference count on the
48 (usually the final element, or parent of final element). This is done by taking
179 taking a reference count (the reference count then gives a stable place to
182 As explained above, we would like to do path walking without taking locks or
206 With this two parts of the puzzle, we can do path lookups without taking
273 Taking a refcount on a dentry from rcu-walk mode, by taking its d_lock,
/linux-6.12.1/Documentation/networking/devlink/
Dindex.rst21 Drivers need to be cautious when taking devlink instance lock and
22 taking RTNL lock at the same time. Devlink instance lock needs to be taken
/linux-6.12.1/tools/perf/pmu-events/arch/x86/jaketown/
Duncore-interconnect.json532 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
542 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
552 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
562 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
572 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
582 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
592 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
602 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
612 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
622 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
[all …]
/linux-6.12.1/drivers/macintosh/
Dwindfarm_smu_sensors.c102 /* Ok, we have to scale & adjust, taking units into account */ in smu_cputemp_get()
124 /* Ok, we have to scale & adjust, taking units into account */ in smu_cpuamp_get()
145 /* Ok, we have to scale & adjust, taking units into account */ in smu_cpuvolt_get()
166 /* Ok, we have to scale & adjust, taking units into account */ in smu_slotspow_get()
/linux-6.12.1/kernel/bpf/
Dreuseport_array.c117 * Hence, due to the above, taking "reuseport_lock" is not in reuseport_array_free()
132 * no one is reading it without taking the in reuseport_array_free()
269 /* Quick checks before taking reuseport_lock */ in bpf_fd_reuseport_array_update_elem()
/linux-6.12.1/drivers/misc/lkdtm/
Dcfi.c10 /* Function taking one argument, without a return value. */
16 /* Function taking one argument, returning int. */
/linux-6.12.1/Documentation/RCU/
Dlockdep.rst89 any change from taking place, and finally, in case (3) the current task
91 from taking place. If the above statement was invoked only from updater
/linux-6.12.1/net/ipv4/
Dtcp_vegas.c76 /* Begin taking Vegas samples next time we send something. */ in vegas_enable()
86 /* Stop taking Vegas samples for now. */
208 * last RTT. Taking the min filters out the effects in tcp_vegas_cong_avoid()
/linux-6.12.1/include/asm-generic/
Dsimd.h10 * taking an interrupt, !in_interrupt() should be a reasonable default.
/linux-6.12.1/include/linux/
Drational.h9 * pll configuration taking into account restricted register size
/linux-6.12.1/drivers/gpu/drm/amd/amdgpu/
Damdgpu_mes.h481 * The problem with taking locks in the MMU notifier is, that MMU
500 * 2. avoid taking reservation locks under the MES lock.
504 * solution is to avoid taking other locks under the MES lock.
Damdgpu_mes.c297 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_create_process()
339 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_destroy_process()
421 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_add_gang()
471 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_remove_gang()
514 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_suspend()
538 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_resume()
642 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_add_hw_queue()
746 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_remove_hw_queue()
795 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_reset_hw_queue()
1154 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_add_ring()
/linux-6.12.1/fs/btrfs/
Dlocking.c246 * Loop around taking references on and locking the root node of the tree until
269 * Loop around taking references on and locking the root node of the tree until
292 * Loop around taking references on and locking the root node of the tree in
/linux-6.12.1/fs/bcachefs/
Dreflink_format.h14 * range we were taking a reference on.
/linux-6.12.1/Documentation/locking/
Drt-mutex-design.rst417 Taking of a mutex (The walk through)
421 taking a mutex.
423 The first thing that is tried is the fast taking of the mutex. This is
424 done when we have CMPXCHG enabled (otherwise the fast taking automatically
518 CMPXCHG. Since the taking of a mutex on contention always sets the
/linux-6.12.1/drivers/staging/fieldbus/anybuss/
Dhms-profinet.c13 /* move to <linux/fieldbus_dev.h> when taking this out of staging */
16 /* move to <linux/anybuss-client.h> when taking this out of staging */
/linux-6.12.1/fs/reiserfs/
DREADME74 aggressive in taking advantage of the commercial possibilities of
105 Konstantin Shvachko was taking part in the early days.
/linux-6.12.1/sound/aoa/soundbus/i2sbus/
Dinterface.h81 * It is derived by taking only every 'divisor' tick of the clock.
109 * derived from the MClk above by taking only every 'divisor' tick
/linux-6.12.1/drivers/gpu/drm/i915/
Di915_scatterlist.c74 * taking a maximum segment length into account, splitting into segments
157 * taking a maximum segment length into account, splitting into segments

12345678910>>...45