Home
last modified time | relevance | path

Searched refs:rbtree (Results 1 – 19 of 19) sorted by relevance

/Linux-v5.4/Documentation/
Drbtree.txt2 Red-black Trees (rbtree) in Linux
29 The high-resolution timer code uses an rbtree to organize outstanding
35 This document covers use of the Linux rbtree implementation. For more
47 Linux's rbtree implementation lives in the file "lib/rbtree.c". To use it,
48 "#include <linux/rbtree.h>".
50 The Linux rbtree implementation is optimized for speed, and thus has one
56 which call the provided rbtree functions. Locking is also left up to the
57 user of the rbtree code.
59 Creating a new rbtree
62 Data nodes in an rbtree tree are structures containing a struct rb_node member::
[all …]
/Linux-v5.4/scripts/gdb/linux/
Dtimerlist.py10 from linux import rbtree
47 curr = curr.address.cast(rbtree.rb_node_type.get_type().pointer())
51 curr = rbtree.rb_next(curr)
/Linux-v5.4/tools/lib/lockdep/
DBuild1 liblockdep-y += common.o lockdep.o preload.o rbtree.o
/Linux-v5.4/scripts/gdb/
Dvmlinux-gdb.py33 import linux.rbtree
/Linux-v5.4/tools/perf/
DMANIFEST13 tools/lib/rbtree.c
/Linux-v5.4/drivers/base/regmap/
DMakefile6 obj-$(CONFIG_REGMAP) += regcache-rbtree.o regcache-flat.o
Dregcache-rbtree.c176 DEFINE_SHOW_ATTRIBUTE(rbtree);
/Linux-v5.4/tools/perf/util/
Dpython-ext-sources32 ../lib/rbtree.c
DBuild29 perf-y += rbtree.o
237 $(OUTPUT)util/rbtree.o: ../lib/rbtree.c FORCE
/Linux-v5.4/Documentation/locking/
Drt-mutex-design.rst106 the task is blocked on. It also has rbtree node structures to
107 place the task in the waiters rbtree of a mutex as well as the
108 pi_waiters rbtree of a mutex owner task (described below).
200 mutex has a rbtree to store these waiters by priority. This tree is protected
208 To keep track of the PI chains, each process has its own PI rbtree. This is
218 This tree is stored in the task structure of a process as a rbtree called
408 should be at, but the rbtree nodes of the task's waiter have not been updated
474 to the mutex. The rbtree node of waiter are initialized to the processes
/Linux-v5.4/Documentation/timers/
Dhrtimers.rst95 file systems. The rbtree is solely used for time sorted ordering, while
97 queued timers, without having to walk the rbtree.
113 be set without having to touch the rbtree. This also makes the handling
/Linux-v5.4/Documentation/scheduler/
Dsched-design-CFS.rst57 runqueues, but it uses a time-ordered rbtree to build a "timeline" of future
71 CFS maintains a time-ordered rbtree, where all runnable tasks are sorted by the
82 becomes the "leftmost task" of the time-ordered rbtree it maintains (plus a
/Linux-v5.4/Documentation/block/
Ddeadline-iosched.rst69 rbtree front sector lookup when the io scheduler merge function is called.
/Linux-v5.4/Documentation/dev-tools/
Dkmemleak.rst87 information like size and stack trace, are stored in a rbtree.
103 the values against the addresses stored in the rbtree. If
/Linux-v5.4/lib/
DMakefile28 rbtree.o radix-tree.o timerqueue.o xarray.o \
DKconfig419 augmented rbtree.
423 Documentation/rbtree.txt
DKconfig.debug1734 A benchmark measuring the performance of the rbtree library.
1735 Also includes rbtree invariant checks.
/Linux-v5.4/drivers/block/xen-blkback/
Dblkback.c212 #define foreach_grant_safe(pos, n, rbtree, node) \ argument
213 for ((pos) = container_of(rb_first((rbtree)), typeof(*(pos)), node), \
/Linux-v5.4/Documentation/admin-guide/
Dcgroup-v2.rst2483 rbtree and treated like equal peers, regardless where they are located