Bläddra i källkod

doc: Take tail recursion into account in RCU requirements

This commit classifies tail recursion as an alternative way to write
a loop, with similar limitations.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Paul E. McKenney 8 år sedan
förälder
incheckning
c75e9caaf8
1 ändrade filer med 2 tillägg och 1 borttagningar
  1. 2 1
      Documentation/RCU/Design/Requirements/Requirements.html

+ 2 - 1
Documentation/RCU/Design/Requirements/Requirements.html

@@ -1849,7 +1849,8 @@ mass storage, or user patience, whichever comes first.
 If the nesting is not visible to the compiler, as is the case with
 If the nesting is not visible to the compiler, as is the case with
 mutually recursive functions each in its own translation unit,
 mutually recursive functions each in its own translation unit,
 stack overflow will result.
 stack overflow will result.
-If the nesting takes the form of loops, either the control variable
+If the nesting takes the form of loops, perhaps in the guise of tail
+recursion, either the control variable
 will overflow or (in the Linux kernel) you will get an RCU CPU stall warning.
 will overflow or (in the Linux kernel) you will get an RCU CPU stall warning.
 Nevertheless, this class of RCU implementations is one
 Nevertheless, this class of RCU implementations is one
 of the most composable constructs in existence.
 of the most composable constructs in existence.