svn commit: r955034 - /subversion/branches/1.6.x/STATUS

[da...@apache.org]

Author: danielsh
Date: Tue Jun 15 20:10:07 2010
New Revision: 955034

URL: http://svn.apache.org/viewvc?rev=955034&view=rev
Log:
* STATUS: Clarify description of the FSFS rep-cache entries.

Suggested by: julianfoad

Modified:
    subversion/branches/1.6.x/STATUS

Modified: subversion/branches/1.6.x/STATUS
URL: http://svn.apache.org/viewvc/subversion/branches/1.6.x/STATUS?rev=955034&r1=955033&r2=955034&view=diff
==============================================================================
--- subversion/branches/1.6.x/STATUS (original)
+++ subversion/branches/1.6.x/STATUS Tue Jun 15 20:10:07 2010
@@ -34,11 +34,13 @@ Candidate changes:
  * r879966, r879971
    Reduce the lifetime of the rep-sharing database handles in FSFS to avoid
    having writers blocking readers, and update that database outside the
-   general FSFS write lock.  This address issue #3506.
+   general FSFS write lock.  This addresses issue #3506.
    Justification:
      The performance problems and outright failures of the current code
      are hurting the ASF repository, and presumably other high-concurrency
      repositories, too, when large commits occur.
+   Justification:
+     Pre-requisite for the r934599 group.
    Branch:
      ^/subversion/branches/1.6.x-issue3506
    Votes:
@@ -48,7 +50,9 @@ Candidate changes:
    Fix a concurrency issue in the FSFS rep-cache code.  This indirectly
    concerns issue #3506.
    Justification:
-     Opening the DB twice (and overwriting the handle) is undesired.
+     Thread safety.
+   Thread:
+     http://article.gmane.org/gmane.comp.version-control.subversion.devel/119483
    Notes:
      r934599 updates the svn_atomic__init_once() interface.
      r934603 is the actual fix.