Shut FlexeLint up about SHA256 implementation.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3649 d4fa192b-c00b-0410-8231-f00ffab90ce4

We cannot gain a reference to an object unless it has an objhead,
assert that we have one.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3648 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3647 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3646 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3645 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3644 d4fa192b-c00b-0410-8231-f00ffab90ce4

Make it possible to declare paramters in other source files, and move
the thread-pool related params into a new file mgt_pool.c as proof.

The paramters happen in management process context, and should therefore
not end up in cache_* files for namespace and sanity reasons.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3643 d4fa192b-c00b-0410-8231-f00ffab90ce4

Name that file "vparam.h" instead of "param.h" which is just too
generic for comfort.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3642 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3641 d4fa192b-c00b-0410-8231-f00ffab90ce4

now.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3640 d4fa192b-c00b-0410-8231-f00ffab90ce4

Try to get the endianess optimization working, by including an assortment
of possibly relevant headers and only go with the fast path if we have
credible information that this is a big-endian platform.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3639 d4fa192b-c00b-0410-8231-f00ffab90ce4

This does not do anything yet.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3638 d4fa192b-c00b-0410-8231-f00ffab90ce4

Hook SHA256 into the build

Neuter the FreeBSD specifics of SHA256 implementation.

In the end, it comes down to lack of POSIX definition of a way to find
out byte-endianess, sigh...



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3637 d4fa192b-c00b-0410-8231-f00ffab90ce4

This code was written by Colin Percival for the FreeBSD project.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3636 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3635 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3634 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3633 d4fa192b-c00b-0410-8231-f00ffab90ce4

Rename the write-buffering functions to WRW_*().

Make reservation and release explicit.

Add asserts that this it happens.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3632 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3631 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3630 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3629 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3628 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3627 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3626 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3625 d4fa192b-c00b-0410-8231-f00ffab90ce4

This isolates the mangement process from the compilers bugs
and memory usage.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3624 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3623 d4fa192b-c00b-0410-8231-f00ffab90ce4

The VCL file specified to -f must be read relative to the directory
from which varnishd is started, before we chdir to the workdir.

We used to deal with this by opening the file and passing the file
handle down.  It's simpler to just read the file and pass the actual
VCL code down.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3622 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3621 d4fa192b-c00b-0410-8231-f00ffab90ce4

Move the code for running stuff in a sub-process out to a library
function, and give it the ability to limit how many lines of
output we get back from the subprocess, in order to muzzle the
C-compiler somewhat.




git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3620 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3619 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3618 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3617 d4fa192b-c00b-0410-8231-f00ffab90ce4

Added support for setting read timeouts for backend requests
(first_byte_timeout and between_bytes_timeout), in addition to make the
connect_timeout available for the bereq object in vcl_miss and vcl_fetch.

first_byte_timeout is a read timeout from the connection to the backend is
created to when the first byte arrives. It can be set as a parameter to
varnish, as a field in the backend declaration or as bereq.first_byte_timeout
in vcl_miss and vcl_pass.

between_bytes_timeout is a read timeout between each read from the backend. It
can be set as a parameter to varnish, as a field in the backend declaration or
as bereq.between_bytes_timeout in vcl_miss and vcl_pass.

The time unit for these timeout values are seconds. NOTE: The connect_timeout
previously used milliseconds as time unit, so beware.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3616 d4fa192b-c00b-0410-8231-f00ffab90ce4

Kick the hash_slinger interface around a bit:

Isolate more stuff in hash_slinger.h.

Remove hash_slinger from cache.h, include in .c's as necessary.

Save a malloc per objhead by putting a few fields into the objhead
for the hash_slingers to use.

Preinitialize the refcount when we precreate the objhead.

Move the hash-string allocation into HSH_Copy(), no point in
duplication of mandatory step.



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3615 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3614 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3613 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3612 d4fa192b-c00b-0410-8231-f00ffab90ce4

Fixed compiling on Linux with -Werror set. Added mising prototypes, removed an unused function and added the ATTRIBUTE_UNUSED to the attribute list for the rb_wrap() macro which generated unused functions.

r3430 | tfheen | 2008-11-24 20:08:36 +0100 (ma., 24 nov. 2008) | 4 lines

Include relevant bit of ansidecl.h directly

Avoids build-dependency on binutils-dev



git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3611 d4fa192b-c00b-0410-8231-f00ffab90ce4

git-svn-id: http://www.varnish-cache.org/svn/branches/2.0@3610 d4fa192b-c00b-0410-8231-f00ffab90ce4