// cache_dir with the smallest max-size gets the known-size object
// cache_dir with the largest max-size gets the unknown-size object
if ((objsize != -1 && SD->maxObjectSize() > best_objsize) ||
- (objsize == -1 && SD->maxObjectSize() < best_objsize))
+ (objsize == -1 && SD->maxObjectSize() < best_objsize))
continue;
}
{
const auto accumulated = entry.mem_obj->availableForSwapOut();
- /*
+ /*
* Keep accumulating more bytes until the set of disks eligible to accept
* the entry becomes stable, and, hence, accumulating more is not going to
* affect the cache_dir selection. A stable set is usually reached
if (accumulated <= secondLargestMaximumObjectSize)
return secondLargestMaximumObjectSize - accumulated + 1;
- /*
+ /*
* Checking largestMaximumObjectSize instead eliminates the risk of starting
* to swap out an entry that later grows too big, but also implies huge
* accumulation in most environments. Accumulating huge entries not only
/// slowly calculate (and cache) hi/lo watermarks and similar limits
void updateLimits();
- /// Additional unknown-size entry bytes required by disks in order to
+ /// Additional unknown-size entry bytes required by disks in order to
/// reduce the risk of selecting the wrong disk cache for the growing entry.
int64_t accumulateMore(const StoreEntry&) const;