On 2018/12/02 07:27:09 -0800, Paul E. McKenney wrote: > On Mon, Dec 03, 2018 at 12:11:20AM +0900, Akira Yokosawa wrote: >> Paul, >> >> IIUC, your work on RCU API consolidation seems to affect Section 9.5.4, >> especially Table 9.3. >> >> I'm not sure, but one idea would be to keep Table 9.3 for future >> reference and add a new one representing consolidated set of API. >> >> Just a reminder. > > And a timely one! Please see attached for a possible LWN article. > Though the LWN editors might quite rightly decide that a third > RCU API article is one too many, in which case I will blog it. > > But either way, thoughts? Hi Paul, I took a while to skim through the article. My first thought was "Wow, the big API table has grown too big to view in a single window of the browser!". For perfbook, it would be quite hard to shrink it in an A4 page. On read-side APIs, I could not get what "the RCU-bh and RCU-sched read-side APIs may now be used with the vanilla RCU update-side APIs" really means. Are they also consolidated in their implementation, but kept for code readability and for static analysis? I looked through LWN articles of RCU kernel APIs and see that current Section 9.5.4 has not updated so much since the first version in 2008 (https://lwn.net/Articles/264090/). Do you have plan to reflect all the updates mentioned in the followup articles in 2010, 2014, as well this one in this section? Yes, documentation in linux/Documentation/RCU/ looks already ready for v4.21/5.0 to reflect the update-side consolidation. So I don't think perfbook needs to cover all of the flavors/APIs. Just referencing the kernel Documents and LWN articles for the complete view should be good enough, I suppose. I'll keep posting if I find something to feedback. Thanks, Akira > > Thanx, Paul >
