]> err.no Git - varnish/commit
projects / varnish / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c1d9ed0) | patch
A better solution than mutexes: give the thread that listens to
authorphk <phk@d4fa192b-c00b-0410-8231-f00ffab90ce4>
Sun, 22 Jun 2008 21:40:21 +0000 (21:40 +0000)
committerphk <phk@d4fa192b-c00b-0410-8231-f00ffab90ce4>
Sun, 22 Jun 2008 21:40:21 +0000 (21:40 +0000)
commitd10a12d66452d8ad6912e08ff6f8885366844b41
tree00eca7ff1a74a7c8c8ec17577f61efb9c4bf2c1atree | snapshot
parentc1d9ed0143a340f7217428d58549fcc54cfbc367commit | diff
A better solution than mutexes: give the thread that listens to
varnish debugging output a separate log handle.

(The point here is to maximize the amount of concurrency we can
simulate.  Down the road, the logging may become pre thread with
a final sorting pass to get all the messages correctly interleaved.)

git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@2775 d4fa192b-c00b-0410-8231-f00ffab90ce4
varnish-cache/bin/varnishtest/vtc_log.c diff | blob | history
varnish-cache/bin/varnishtest/vtc_varnish.c diff | blob | history
Varnish, the HTTP accelerator