Home
last modified time | relevance | path

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

12345678910>>...39

/Linux-v6.1/net/mac80211/
DKconfig206 is taking part in a mesh network).
219 is taking part in a mesh network).
232 is taking part in a mesh network).
244 synchronization debugging messages (when mac80211 is taking part in a
255 channel switch debugging messages (when mac80211 is taking part in a
266 powersave debugging messages (when mac80211 is taking part in a
/Linux-v6.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-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
Duncore-interconnect.json208 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
218 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
228 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
239 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
250 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
261 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
272 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
283 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
294 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
305 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
[all …]
/Linux-v6.1/fs/
Dmount.h13 * - taking namespace_sem for write, OR
14 * - taking namespace_sem for read AND taking .ns_lock.
/Linux-v6.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-v6.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-v6.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,
Ddirectory-locking.rst10 When taking the i_rwsem on multiple non-directory objects, we
118 means that cross-directory rename is taking locks out of order. Due
/Linux-v6.1/arch/arm/mach-pxa/
Dcolibri-pxa3xx.c54 printk(KERN_INFO "%s(): taking MAC from serial boot tag\n", in colibri_pxa3xx_init_eth()
59 "taking MAC from device\n", __func__); in colibri_pxa3xx_init_eth()
/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/
Duncore-interconnect.json446 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
456 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
466 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
477 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
488 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
499 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
510 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
521 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
532 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
543 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits*80b/time. …
[all …]
/Linux-v6.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-v6.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()
272 /* Quick checks before taking reuseport_lock */ in bpf_fd_reuseport_array_update_elem()
/Linux-v6.1/drivers/misc/lkdtm/
Dcfi.c10 /* Function taking one argument, without a return value. */
16 /* Function taking one argument, returning int. */
/Linux-v6.1/Documentation/RCU/
Dlockdep.rst86 any change from taking place, and finally, in case (3) the current task
88 from taking place. If the above statement was invoked only from updater
/Linux-v6.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-v6.1/drivers/gpu/drm/amd/amdgpu/
Damdgpu_mes.h395 * The problem with taking locks in the MMU notifier is, that MMU
414 * 2. avoid taking reservation locks under the MES lock.
418 * solution is to avoid taking other locks under the MES lock.
Damdgpu_mes.c301 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_create_process()
355 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_destroy_process()
439 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_add_gang()
489 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_remove_gang()
529 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_suspend()
558 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_resume()
656 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_add_hw_queue()
761 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_remove_hw_queue()
991 * Avoid taking any other locks under MES lock to avoid circular in amdgpu_mes_add_ring()
/Linux-v6.1/include/asm-generic/
Dsimd.h10 * taking an interrupt, !in_interrupt() should be a reasonable default.
/Linux-v6.1/include/linux/
Drational.h9 * pll configuration taking into account restricted register size
/Linux-v6.1/tools/testing/selftests/bpf/progs/
Dbtf_dump_test_case_syntax.c47 * - `fn_ptr2_t`: function, taking anonymous struct as a first arg and pointer
65 * - fn_ptr_arr2_t: array of const pointers to a function taking no arguments
/Linux-v6.1/drivers/gpu/drm/i915/
Di915_scatterlist.c74 * taking a maximum segment length into account, splitting into segments
150 * taking a maximum segment length into account, splitting into segments
/Linux-v6.1/fs/btrfs/
Dlocking.c243 * Loop around taking references on and locking the root node of the tree until
266 * Loop around taking references on and locking the root node of the tree until
289 * Loop around taking references on and locking the root node of the tree in
/Linux-v6.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-v6.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-v6.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

12345678910>>...39