Paul E. McKenney
Posts
81Following
49Followers
197
Paul E. McKenney
paulmckrcu
@tobinbaker @pkhuong @jwseigh OK, that does make a lot of sense!
Do you also have the update side flag the offending thread when a grace period extends for too long? (AKA thread keeping epoch open for too long.)
Do you also have the update side flag the offending thread when a grace period extends for too long? (AKA thread keeping epoch open for too long.)
1
0
0
Paul E. McKenney
paulmckrcu
@tobinbaker @pkhuong @jwseigh OK, I will bite... Why do you need them "everywhere" instead of only on the update side?
1
0
0
Paul E. McKenney
paulmckrcu
@jwseigh @tobinbaker @pkhuong One way of looking at RCU (of which EBR is a set of implementations) is as a replacement for reader-writer locking. Staying in an RCU reader for too long is just as bad as staying in a reader-writer-locking reader for too long. In the Linux kernel, we use stall warnings to catch these usage bugs, but user-mode implementations seem slow to adopt this approach.
1
0
1
Paul E. McKenney
paulmckrcu
@ptesarik @clankgy1 @kernellogger Looking forward to it! But why wait? Valentine's day is on February 14th over here, and what better day for a heart of spaces? ;-)
0
0
2
Paul E. McKenney
paulmckrcu
@clankgy1 @kernellogger What Marcus Müller said! Perhaps the "fmt" command needs help in this regard? Or perhaps the "fmt" developers decided to have a bit of fun. ;-)
0
0
1
Paul E. McKenney
paulmckrcu
@keithp Then Linux-kernel tools/include/nolibc will provide you with even more irritation!!! ;-)
1
0
0
Paul E. McKenney
paulmckrcu
@kunev Agreed, but are they more stupid or less stupid than human beings?
0
0
0
Paul E. McKenney
paulmckrcu
@ljs Yes, it is necessary to make conscious and careful tradeoffs. Necessary, but not necessarily popular. Sound bites are much more fun, after all! ;-)
0
0
2
Paul E. McKenney
paulmckrcu
@ljs In some cases, short term vs. long term viewpoint. Given a reasonably stable environment, long term normally wins.
But if, and only if, you survive the short term. ;-)
But if, and only if, you survive the short term. ;-)
1
0
3
Paul E. McKenney
paulmckrcu
@geert Glad you like it! I am now working on some changes to better handle more corner cases.
0
0
2
Paul E. McKenney
paulmckrcu
@dvim I don't see any marking, but to be fair, given that it does involve Duplos and Legos, "for kids" might not be entirely inappropriate. ;-)
0
0
0
Paul E. McKenney
paulmckrcu
And my Kernel Recipes talk is now available: https://youtu.be/qYPCL1KGdQA
A big "Thank you!" to everyone involved!
A big "Thank you!" to everyone involved!
1
10
18
Paul E. McKenney
paulmckrcu
For those interested in lifetime-end pointer zap, now feature-complete citing the most recent working papers: https://people.kernel.org/paulmck/what-on-earth-does-lifetime-end-pointer-zap-have-to-do-with-rcu
0
5
12
Paul E. McKenney
paulmckrcu
0
0
2
Paul E. McKenney
paulmckrcu
@ljs @brauner @cyphar LaTeX is not perfect, and it has a learning curve, but it is quite capable. Especially if you cheat like I do and so some of the work in other scripting languages.
As to the LaTeX build times, I suspect that they are much more tolerable when your book is less than 700 pages. ;-)
As to the LaTeX build times, I suspect that they are much more tolerable when your book is less than 700 pages. ;-)
0
0
3
Paul E. McKenney
paulmckrcu
@brauner @cyphar The original nroff and troff from which groff descends had to do typesetting (and in troff's case, phtoto-typesetting) on systems having a 64Kbyte address space. So Moses simply did not have sufficient space to record nroff and troff as sins on his tablets. Plus there is not a huge number of people who, like me, are older than nroff and troff, but I am here to tell you that both nroff and troff seemed pretty nice to me back in the day.
So who knows? It just might be time for a change in format. After all, I long ago made the switch from nroff/troff to LaTeX. ;-)
So who knows? It just might be time for a change in format. After all, I long ago made the switch from nroff/troff to LaTeX. ;-)
0
0
8
Paul E. McKenney
paulmckrcu
@jwseigh This stuff is tricky, and thank you for introducing me to the memory-to-memory single-instruction copy trick for Hazard Pointers.
1
0
0