Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
958114da
Commit
958114da
authored
Mar 12, 2011
by
Poul-Henning Kamp
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Commenting
parent
8838884f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
1 deletion
+17
-1
vsm.c
bin/varnishd/vsm.c
+17
-1
No files found.
bin/varnishd/vsm.c
View file @
958114da
...
...
@@ -27,6 +27,22 @@
*
* VSM stuff common to manager and child.
*
* We have three potential conflicts we need to lock against here:
*
* VSM-studying programs (varnishstat...) vs. everybody else
* The VSM studying programs only have read-only access to the VSM
* so everybody else must use memory barriers, stable storage and
* similar tricks to keep the VSM image in sync (long enough) for
* the studying programs.
*
* Manager process vs child process.
* Will only muck about in VSM when child process is not running
* Responsible for cleaning up any mess left behind by dying child.
*
* Child process threads
* Pthread locking necessary.
*
* XXX: not all of this is in place yet.
*/
#include "config.h"
...
...
@@ -89,7 +105,7 @@ vsm_cleanup(void)
if
(
sha
==
NULL
)
return
;
seq
=
vsm_mark
();
/* First pass, free, and collaps with next if applicable */
/* First pass, free, and collaps
e
with next if applicable */
VSM_ITER
(
sha
)
{
if
(
strcmp
(
sha
->
class
,
VSM_CLASS_COOL
))
continue
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment