summaryrefslogtreecommitdiffstats
path: root/net/disk_cache/block_files.cc
diff options
context:
space:
mode:
authorrvargas@google.com <rvargas@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-08-27 17:49:42 +0000
committerrvargas@google.com <rvargas@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2010-08-27 17:49:42 +0000
commit67b09ecdd8769cd291dbd0e52e73826771cf29b5 (patch)
tree7d11e7c41d0f448767a0676091f714a2d6712991 /net/disk_cache/block_files.cc
parent0bad9b1895f6f0264527a9986044d9d1ee9152b1 (diff)
downloadchromium_src-67b09ecdd8769cd291dbd0e52e73826771cf29b5.zip
chromium_src-67b09ecdd8769cd291dbd0e52e73826771cf29b5.tar.gz
chromium_src-67b09ecdd8769cd291dbd0e52e73826771cf29b5.tar.bz2
Disk cache: For an AppCache, now we only update the
LRU list when an entry is created. This means that we don't update the list anymore when an entry is accessed, even if we are writing to the entry. The general idea is that now we should be able to open an AppCache and read from it without modifying the contents of the cache, so that if the browser crashes, we won't find "dirty" entries to discard. By minimizing writes to the LRU list, we reduce the chances that the list will get corrupt beyond the point where we cannot trust it anymore if the whole system crashes (and not just the browser). BUG=51870 TEST=net_unittests Review URL: http://codereview.chromium.org/3186032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57697 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/disk_cache/block_files.cc')
-rw-r--r--net/disk_cache/block_files.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/net/disk_cache/block_files.cc b/net/disk_cache/block_files.cc
index 48e5be3..9f6c489 100644
--- a/net/disk_cache/block_files.cc
+++ b/net/disk_cache/block_files.cc
@@ -503,7 +503,7 @@ bool BlockFiles::FixBlockFileHeader(MappedFile* file) {
return true;
}
-// We are interested in the total number of block used by this file type, and
+// We are interested in the total number of blocks used by this file type, and
// the max number of blocks that we can store (reported as the percentage of
// used blocks). In order to find out the number of used blocks, we have to
// substract the empty blocks from the total blocks for each file in the chain.