Lines Matching full:sections

74 of all pre-existing RCU read-side critical sections. An RCU read-side
387 #. Wait for all pre-existing RCU read-side critical sections to complete
517 | Given that multiple CPUs can start RCU read-side critical sections at |
604 | critical sections. Given such rearrangement, if a given RCU read-side |
606 | read-side critical sections are done? Won't the compiler              |
618 | sections, no matter how aggressively the compiler scrambles the code. |
685 infinitely long, however, the following sections list a few
692 #. `Grace Periods Don't Partition Read-Side Critical Sections`_
693 #. `Read-Side Critical Sections Don't Partition Grace Periods`_
809 Grace Periods Don't Partition Read-Side Critical Sections
817 partition the set of RCU read-side critical sections. An example of this
860 If it is necessary to partition RCU read-side critical sections in this
902 the two RCU read-side critical sections cannot overlap, guaranteeing
914 Read-Side Critical Sections Don't Partition Grace Periods
982 | read-side critical sections at the beginning and end of the chain?    |
1045 These sections list quality-of-implementation requirements. Although an
1057 These classes is covered in the following sections.
1084 primitives be legal within RCU read-side critical sections, including
1096 | sections because it is not legal to place a quiescent state (in this  |
1099 | read-side critical sections, and also within Linux-kernel sleepable   |
1100 | RCU `(SRCU) <Sleepable RCU_>`__ read-side critical sections. In       |
1102 | that the corresponding critical sections can be preempted, which also |
1105 | sections.                                                             |
1231 critical sections are short. There are currently no special latency
1495 use. And in theory, RCU read-side critical sections may be composed, and
1519 critical sections between which there is an operation that waits for a
1531 sections can be composed surprisingly freely, but only if deadlock is
1534 In short, although RCU read-side critical sections are highly
1542 read-side critical sections, perhaps even so intense that there was
1545 block grace periods: As long as all the RCU read-side critical sections
1549 RCU read-side critical sections being preempted for long durations,
1563 rates should not delay RCU read-side critical sections, although some
1654    read-side critical sections, there is currently no good way of doing
1701 notable Linux-kernel complications. Each of the following sections
1821 The Linux kernel has interrupts, and RCU read-side critical sections are
1834 critical sections are legal within NMI handlers. Thankfully, RCU
1924 critical sections. This requirement was present from day one in
1995 read-side critical sections implicitly avoids earlier issues that used
2060 of RCU read-side critical sections.
2155    critical sections, and RCU believes this CPU to be idle, you will get
2161    sections, and RCU believes this CPU to be idle, no problem. This
2169    fact joking about not doing RCU read-side critical sections.
2290 approach of disabling preemption across RCU read-side critical sections
2292 an RCU implementation that allows RCU read-side critical sections to be
2381 local_bh_disable() across its read-side critical sections, and which
2467 sections almost never sleep, but sometimes need to. This resulted in the
2490 sections, however, with great power comes great responsibility. If you
2492 sections, then that domain's grace periods will also be blocked forever.
2517 Unlike the other RCU flavors, SRCU read-side critical sections can run
2609 critical sections that are delimited by voluntary context switches, that
2612 userspace execution also delimit tasks-RCU read-side critical sections.