Searched full:taking (Results 1 – 25 of 141) sorted by relevance
123456
| /Documentation/networking/devlink/ |
| D | index.rst | 21 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
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-bdi | 68 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
|
| /Documentation/driver-api/tty/ |
| D | tty_buffer.rst | 9 Here, we document functions for taking care of tty buffer and their flipping.
|
| /Documentation/filesystems/ |
| D | path-lookup.txt | 25 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,
|
| /Documentation/RCU/ |
| D | lockdep.rst | 89 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
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-event.rst | 10 notified on certain conditions taking place on a device. This might
|
| D | ext-ctrls-image-source.rst | 84 control taking 4 gain values, being the gains for each of the
|
| /Documentation/devicetree/bindings/firmware/ |
| D | cznic,turris-omnia-mcu.yaml | 35 The interrupt numbers correspond sequentially to GPIO numbers, taking the
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | tpo,tpg110.yaml | 28 this can be set up by taking software control of the display
|
| /Documentation/block/ |
| D | biovecs.rst | 28 constructed from the raw biovecs but taking into account bi_bvec_done and
104 taking into account bi_bvec_done (and bi_size).
|
| /Documentation/arch/riscv/ |
| D | uabi.rst | 58 guarantee that the kernel is taking advantage of the extension, or that the
|
| /Documentation/locking/ |
| D | rt-mutex-design.rst | 417 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
|
| /Documentation/sound/soc/ |
| D | jack.rst | 55 be set up by the machine driver, taking configuration for the jack to
|
| /Documentation/core-api/ |
| D | idr.rst | 66 you can call idr_preload() before taking the lock, and then
|
| /Documentation/firmware-guide/acpi/ |
| D | osi.rst | 30 Experience shows that taking untested paths through the BIOS
143 catastrophic failure resulting from the BIOS taking paths that
|
| /Documentation/mm/ |
| D | transhuge.rst | 45 to check head page instead. Taking a reference on any head/tail page would
99 page table lock (pmd_lock()) and re-run pmd_trans_huge. Taking the
|
| D | highmem.rst | 57 them. The only differences between them consist in the first taking a pointer
58 to a struct page and the second taking a pointer to struct folio and the byte
|
| D | active_mm.rst | 7 with CONFIG_MMU_LAZY_TLB_REFCOUNT=n. Taking and releasing these lazy
|
| /Documentation/process/ |
| D | management-style.rst | 223 best way of taking the blame: do it for someone else. You'll feel good
224 for taking the fall, they'll feel good about not getting blamed, and the
235 Taking the blame is also why you get to be manager in the first place.
|
| /Documentation/arch/arm/google/ |
| D | chromebook-boot-flow.rst | 61 It should be noted that, taking into account the above system that
|
| /Documentation/arch/x86/ |
| D | tlb.rst | 59 determine how long the flush operations are taking.
|
| /Documentation/admin-guide/acpi/ |
| D | cppc_sysfs.rst | 66 taking two different snapshots of feedback counters at time T1 and T2.
|
| /Documentation/devicetree/bindings/mtd/ |
| D | raw-nand-chip.yaml | 75 providing the best strength and taking the OOB area size
|
| /Documentation/arch/arm64/ |
| D | cpu-hotplug.rst | 8 CPU hotplug in the arm64 world is commonly used to describe the kernel taking
|
| /Documentation/accounting/ |
| D | delay-accounting.rst | 55 Taking the difference of two successive readings of a given
|
123456