From: Paul E. McKenney Date: Thu, 27 Apr 2017 20:25:41 +0000 (-0700) Subject: doc: Take tail recursion into account in RCU requirements X-Git-Tag: v4.13-rc1~209^2^2~55 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=c75e9caaf85f1fc4ed32e510b259d67ec3c4c603;p=karo-tx-linux.git 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 --- diff --git a/Documentation/RCU/Design/Requirements/Requirements.html b/Documentation/RCU/Design/Requirements/Requirements.html index 8bbf0bb18389..cb614f2a69c2 100644 --- a/Documentation/RCU/Design/Requirements/Requirements.html +++ b/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 mutually recursive functions each in its own translation unit, 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. Nevertheless, this class of RCU implementations is one of the most composable constructs in existence.