lkml.org 
[lkml]   [2008]   [Aug]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH, RFC, tip/core/rcu] scalable classic RCU implementation
    From
    Date
    On Fri, 2008-08-22 at 16:29 -0700, Josh Triplett wrote:

    > > @@ -26,8 +27,10 @@
    > > * http://lse.sourceforge.net/locking/rclock_OLS.2001.05.01c.sc.pdf (OLS2001)
    > > *
    > > * For detailed explanation of Read-Copy Update mechanism see -
    > > - * Documentation/RCU
    > > - *
    > > + * Documentation/RCU
    > > + * http://lwn.net/Articles/262464/ (What is RCU, Fundamentally?)
    > > + * http://lwn.net/Articles/263130/ (What is RCU's Usage?)
    > > + * http://lwn.net/Articles/264090/ (What is RCU's API? + references)
    > > */
    >
    > Why put these references here rather than in Documentation/RCU? It
    > seems easier to keep documentation up to date in one place. If you
    > think these represent a good "getting started" set of documents, how
    > about a Documentation/RCU/ReadTheseFirst with links to them, or how
    > about linking to them from whatisRCU.txt?

    I actually like in code comments and 'documentation' more than
    Documentation/ stuff. Mostly because Documentation/ is:
    - far away from the code
    - therefore, more easily bitrotted
    - and easily forgotten





    \
     
     \ /
      Last update: 2008-08-25 12:37    [W:0.022 / U:1.468 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site