summaryrefslogtreecommitdiff
path: root/src/libostree/ostree-async-progress.h
diff options
context:
space:
mode:
authorPhilip Withnall <withnall@endlessm.com>2017-04-28 16:18:55 +0100
committerAtomic Bot <atomic-devel@projectatomic.io>2017-04-29 11:50:15 +0000
commitc27b66de80ee09077b770b8059a15e5c541e70e3 (patch)
tree65600640ea2a4f019bfac08ce6a744197b951c11 /src/libostree/ostree-async-progress.h
parentf74e52a3a0c441f8e56b796d99c492b1a0a2072c (diff)
downloadostree-c27b66de80ee09077b770b8059a15e5c541e70e3.tar.gz
libostree: Add multiple getter/setter support to OstreeAsyncProgress
OstreeAsyncProgress is thread-safe: it can have keys changed by one thread while another is getting the same keys (modulo some locking contention). However, the thread safety is done at the function call level: if some code calls an OstreeAsyncProgress getter several times, the key fetches are not atomic with respect to each other. In the case of contention on the lock, this can result in consumers of OstreeAsyncProgress data seeing an inconsistent state between the properties they query, which could result in progress reporting inaccuracies. In the uncontested case, this results in the OstreeAsyncProgress lock being locked and unlocked many times more than necessary. Try to improve this by adding new API, which supports getting and setting multiple keys atomically: • ostree_async_progress_get() • ostree_async_progress_set() The new API uses GVariants and varargs: keys are passed as a GVariantType string followed by arguments as for g_variant_new() or g_variant_get(), followed by the next key, etc. Signed-off-by: Philip Withnall <withnall@endlessm.com> Closes: #819 Approved by: cgwalters
Diffstat (limited to 'src/libostree/ostree-async-progress.h')
-rw-r--r--src/libostree/ostree-async-progress.h8
1 files changed, 8 insertions, 0 deletions
diff --git a/src/libostree/ostree-async-progress.h b/src/libostree/ostree-async-progress.h
index 62bdcff8..55ac591c 100644
--- a/src/libostree/ostree-async-progress.h
+++ b/src/libostree/ostree-async-progress.h
@@ -54,6 +54,10 @@ _OSTREE_PUBLIC
char *ostree_async_progress_get_status (OstreeAsyncProgress *self);
_OSTREE_PUBLIC
+void ostree_async_progress_get (OstreeAsyncProgress *self,
+ ...) G_GNUC_NULL_TERMINATED;
+
+_OSTREE_PUBLIC
guint ostree_async_progress_get_uint (OstreeAsyncProgress *self,
const char *key);
_OSTREE_PUBLIC
@@ -68,6 +72,10 @@ void ostree_async_progress_set_status (OstreeAsyncProgress *self,
const char *status);
_OSTREE_PUBLIC
+void ostree_async_progress_set (OstreeAsyncProgress *self,
+ ...) G_GNUC_NULL_TERMINATED;
+
+_OSTREE_PUBLIC
void ostree_async_progress_set_uint (OstreeAsyncProgress *self,
const char *key,
guint value);