Home
last modified time | relevance | path

Searched full:concurrently (Results 1 – 25 of 358) sorted by relevance

12345678910>>...15

/kernel/linux/linux-5.10/include/linux/
Drculist.h109 * However, it is perfectly legal to run concurrently with
130 * However, it is perfectly legal to run concurrently with
155 * However, it is perfectly legal to run concurrently with
187 * perfectly legal to run concurrently with the _rcu list-traversal
224 * concurrently with this function.
312 * This primitive may safely run concurrently with the _rcu list-mutation
348 * This primitive may safely run concurrently with the _rcu list-mutation
367 * This primitive may safely run concurrently with the _rcu list-mutation
386 * This list-traversal primitive may safely run concurrently with
403 * This list-traversal primitive may safely run concurrently with
[all …]
Drculist_nulls.h30 * perfectly legal to run concurrently with the _rcu list-traversal
70 * However, it is perfectly legal to run concurrently with
93 * However, it is perfectly legal to run concurrently with
124 * However, it is perfectly legal to run concurrently with
Dfsverity.h68 * called by multiple processes concurrently on the same inode.
87 * called by multiple processes concurrently, even with the same page.
120 * I.e., another task may publish ->i_verity_info concurrently, in fsverity_get_info()
214 * a race condition where the file is being read concurrently with
Drcupdate_wait.h35 * synchronize_rcu_mult - Wait concurrently for multiple grace periods
38 * This macro waits concurrently for multiple types of RCU grace periods.
Dkcsan-checks.h396 * Use this for variables, where some bits must not be modified concurrently,
397 * yet other bits are expected to be modified concurrently.
400 * but other bits may still be modified concurrently. A reader may wish to
424 * be modified concurrently. Writers, where other bits may change concurrently,
Drculist_bl.h42 * However, it is perfectly legal to run concurrently with
65 * However, it is perfectly legal to run concurrently with
Ddma-resv.h101 * that the lock is only against other writers, readers will run concurrently
123 * will run concurrently with a writer under RCU. The seqlock is used to
174 * concurrently with a writer under RCU. The seqlock is used to notify readers
Dradix-tree.h126 * concurrently with other readers.
141 * running concurrently.
154 * delete nodes running concurrently with it may affect its result such that
168 * held (ie. items cannot be concurrently inserted).
/kernel/linux/linux-5.10/include/asm-generic/bitops/
Dinstrumented-non-atomic.h22 * region of memory concurrently, the effect may be that only one operation
37 * region of memory concurrently, the effect may be that only one operation
52 * region of memory concurrently, the effect may be that only one operation
Dinstrumented-lock.h36 * concurrently modify other bits in the word.
/kernel/linux/linux-5.10/Documentation/dev-tools/
Dkcsan.rst191 they happen concurrently in different threads, and at least one of them is a
223 manifest as data races. Race conditions occur if concurrently executing
236 KCSAN relies on observing that two accesses happen concurrently. Crucially, we
267 marked operations, if all accesses to a variable that is accessed concurrently
/kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/tc-tests/filters/
Dconcurrency.json77 "name": "Concurrently replace same range of 100k flower filters from 10 tc instances",
102 "name": "Concurrently delete same range of 100k flower filters from 10 tc instances",
/kernel/linux/linux-5.10/drivers/gpu/drm/panfrost/
Dpanfrost_devfreq.h28 * because these can be updated concurrently between multiple jobs.
/kernel/linux/linux-5.10/drivers/gpu/drm/lima/
Dlima_devfreq.h29 * because these can be updated concurrently, for example by the GP
/kernel/linux/linux-5.10/fs/nilfs2/
DKconfig18 snapshot is mountable as a read-only file system concurrently with
/kernel/linux/linux-5.10/Documentation/driver-api/
Dedac.rst86 sets of memory devices. The two rows cannot be accessed concurrently.
93 of memory devices. The two rows cannot be accessed concurrently.
/kernel/linux/linux-5.10/arch/arm/mach-tango/
Dplatsmp.c16 * cpu_kill() and cpu_die() run concurrently on different cores.
/kernel/linux/linux-5.10/tools/memory-model/scripts/
Dcheckalllitmus.sh16 # This script makes no attempt to run the litmus tests concurrently.
/kernel/linux/linux-5.10/tools/testing/selftests/cpufreq/
Dspecial-tests.sh65 # this is called concurrently from governor_race
/kernel/linux/linux-5.10/arch/csky/abiv2/
Dcacheflush.c74 * Flush the I$ of other harts concurrently executing, and mark them as in flush_icache_mm_range()
/kernel/linux/linux-5.10/drivers/ptp/
Dptp_private.h55 * that a writer might concurrently increment the tail does not
/kernel/linux/linux-5.10/arch/riscv/mm/
Dcacheflush.c54 * Flush the I$ of other harts concurrently executing, and mark them as in flush_icache_mm()
/kernel/linux/linux-5.10/mm/
Dcleancache.c66 * Since filesystems can be mounted concurrently with cleancache in cleancache_register_ops()
102 * function is called or even concurrently with it, but since in cleancache_register_ops()
/kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/creating-plugins/
DAddingPlugins.txt93 concurrently.
/kernel/linux/linux-5.10/drivers/remoteproc/
Dmtk_common.h97 /* To prevent multiple ipi_send run concurrently. */

12345678910>>...15