git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5587 d4fa192b-c00b-0410-8231-f00ffab90ce4

reflect the sum of obj.ttl and obj.grace.

Obj.grace if not set, default to $default_grace, which might have
a different value when we open the silo in a new run.

Solve this, by saving the ttl as the negative sum of (obj.ttl + obj.grace)
if obj.grace is set, or the positive obj.ttl if it is not, and by
adding $default_grace to obj.ttl in the latter case.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5586 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5585 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5584 d4fa192b-c00b-0410-8231-f00ffab90ce4

of work to do, this timestamp could get behind times, and send the
thread to sleep, despite being behind on work.

Fix this, by updating the timestamp whenever we run out of work.

Add a parameter ("expiry_sleep") to control how long time the thread
will sleep so this can be tuned down on high-load servers.

Inspired by:	sky



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5583 d4fa192b-c00b-0410-8231-f00ffab90ce4

a change of key value.

Contrary to the previous comment in cache_expire.c, this process is
guaranteed to work because the shuffle will always terminate either
in the root position or in the bottom row.

Use this function when we adjust ttl on an object.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5582 d4fa192b-c00b-0410-8231-f00ffab90ce4

Various minor nits



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5581 d4fa192b-c00b-0410-8231-f00ffab90ce4

Fixes: #817


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5580 d4fa192b-c00b-0410-8231-f00ffab90ce4

Move HSH_Freestore() to STV_Freestore(), it's a better fit.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5579 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5578 d4fa192b-c00b-0410-8231-f00ffab90ce4

Split up the hitrate chapter into four and added a introduction to ESI. ESI needs a bit of work wrt params and operational factors.

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5577 d4fa192b-c00b-0410-8231-f00ffab90ce4

Split up the hitrate chapter into four and added a introduction to ESI. ESI needs a bit of work wrt params and operational factors.

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5576 d4fa192b-c00b-0410-8231-f00ffab90ce4

Seed the RAND48 generator when we seed the RANDOM generator.

This eats up one random number, so test-cases relying on order
needs to shift one down.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5575 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5574 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5573 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5572 d4fa192b-c00b-0410-8231-f00ffab90ce4

sp->objcore and we can find the objhead from the objcore.

Rename it to match its remaining functionality:  recording which
busy objhead we are sleeping on.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5571 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5570 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5569 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5568 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5567 d4fa192b-c00b-0410-8231-f00ffab90ce4

Only -spersistent needs it yet and we can generalize should the need
ever materialize.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5566 d4fa192b-c00b-0410-8231-f00ffab90ce4

rather than the pointer, otherwise a number of nasty issues appear.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5565 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5564 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5563 d4fa192b-c00b-0410-8231-f00ffab90ce4

simplifies stuff somewhat for the main code and remains the same
tricky business for -spersistent.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5562 d4fa192b-c00b-0410-8231-f00ffab90ce4

does not require it any more.




git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5561 d4fa192b-c00b-0410-8231-f00ffab90ce4

of the default method for now.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5560 d4fa192b-c00b-0410-8231-f00ffab90ce4

non-cacheable objects, rather than direct mallocs.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5559 d4fa192b-c00b-0410-8231-f00ffab90ce4

the gunk:

A persistent storage method, needs to know about "struct object" in
addition to regular storage allocations, in order to track ttl and
ban information etc.

Therefore, when we create an object, we call into the stevedore.c
to do so with STV_NewObject(), it picks an stevedore, and calls
the ->allocobj() method, which will allocate some storage, call
STV_MkObject() to turn it into an object, which can then be
fondled, before passing it back to STV_NewObject() an from there
to cache_center.c::cnt_fetch().

Non-persistent stevedores, don't define ->allocobj() and when
initialized by stevedore.c, get a suitable default function.

XXX: next steps, remove objcore argument from stv->alloc() and
remove stv->object() method entirely, now that we have a proper
calling order.





git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5558 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5557 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5556 d4fa192b-c00b-0410-8231-f00ffab90ce4

it belongs (more)



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5555 d4fa192b-c00b-0410-8231-f00ffab90ce4

more extensive work to it.

[1] If I wanted to be buzzword compliant, I'd say "refactor" :-)



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5554 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5553 d4fa192b-c00b-0410-8231-f00ffab90ce4

Clean up assert for proper use of busy flag



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5552 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5551 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5550 d4fa192b-c00b-0410-8231-f00ffab90ce4

Make it possible to add a hit/miss item to varnishncsa as well as a
hit/miss/pass/pipe item.


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5549 d4fa192b-c00b-0410-8231-f00ffab90ce4

Default to a parallelism of 3, and just use our own test driver


git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@5548 d4fa192b-c00b-0410-8231-f00ffab90ce4