diff options
| author | hclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-02 20:13:57 +0000 |
|---|---|---|
| committer | hclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-02 20:13:57 +0000 |
| commit | 790656e31f441404fa57944ca1a69890052a7828 (patch) | |
| tree | 37e5c7a8bdc2eea8044c8eda4d5fdd9d253694ae /net/disk_cache/stats_histogram.cc | |
| parent | e741b941959feba1e0d7317aefad6f948219dc8a (diff) | |
| download | chromium_src-790656e31f441404fa57944ca1a69890052a7828.zip chromium_src-790656e31f441404fa57944ca1a69890052a7828.tar.gz chromium_src-790656e31f441404fa57944ca1a69890052a7828.tar.bz2 | |
Fixing bugs in sparse cache when dealing with GetAvailableRange queries not aligned
TEST=net_unittests --gtest_filter=DiskCacheEntryTest.PartialSparseEntry
In handling GetAvailableRange() queries, if the start offset is not aligned to 1KB,
there was some strange behaviors:
1. The start offset found is smaller than the input offset
2. Number of continus bytes doesn't take into account offset in a block.
This patch will fix the above problems.
Review URL: http://codereview.chromium.org/186002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25225 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/disk_cache/stats_histogram.cc')
0 files changed, 0 insertions, 0 deletions