aboutsummaryrefslogtreecommitdiffstats
path: root/tools/xenstore/xenstored_core.h
diff options
context:
space:
mode:
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>2005-10-09 18:52:54 +0100
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>2005-10-09 18:52:54 +0100
commit4657d174aba23168b14408dc59a3ec181154b833 (patch)
tree3583ca3442f564bc3ec97ffacf16aef72af2d656 /tools/xenstore/xenstored_core.h
parentb1f64c5b903b3b99972e9d76e00159b4c5fcd02e (diff)
downloadxen-4657d174aba23168b14408dc59a3ec181154b833.tar.gz
xen-4657d174aba23168b14408dc59a3ec181154b833.tar.bz2
xen-4657d174aba23168b14408dc59a3ec181154b833.zip
Refactor xenbus to break up the xenbus_lock and permit watches
to fire concurrently with request/reply pairs. Remove watch_ack message: no longer needed. Signed-off-by: Keir Fraser <keir@xensource.com>
Diffstat (limited to 'tools/xenstore/xenstored_core.h')
-rw-r--r--tools/xenstore/xenstored_core.h3
1 files changed, 0 insertions, 3 deletions
diff --git a/tools/xenstore/xenstored_core.h b/tools/xenstore/xenstored_core.h
index e0e4d58886..e017bddf42 100644
--- a/tools/xenstore/xenstored_core.h
+++ b/tools/xenstore/xenstored_core.h
@@ -71,9 +71,6 @@ struct connection
/* Is this a read-only connection? */
bool can_write;
- /* Are we waiting for a watch event ack? */
- struct watch *waiting_for_ack;
-
/* Buffered incoming data. */
struct buffered_data *in;