summaryrefslogtreecommitdiffstats
path: root/source3/include/g_lock.h
Commit message (Collapse)AuthorAgeFilesLines
* s3:include: add forward declaration for struct messaging_context; in g_lock.hStefan Metzmacher2013-10-171-0/+1
| | | | | | Signed-off-by: Stefan Metzmacher <metze@samba.org> Reviewed-by: Andrew Bartlett <abartlet@samba.org>
* s3:lib fix compiler warningsChristian Ambach2012-05-031-0/+6
| | | | | g_lock.c:182:20: warning: no previous prototype for ‘g_lock_lock_send’ g_lock.c:270:10: warning: no previous prototype for ‘g_lock_lock_recv’
* s3-g_lock: Use dbwrap_record_watch_send/recvVolker Lendecke2012-04-191-5/+0
| | | | | | | | | | This simplifies the g_lock implementation. The new implementation tries to acquire a lock. If that fails due to a lock conflict, wait for the g_lock record to change. Upon change, just try again. The old logic had to cope with pending records and an ugly hack into ctdb itself. As a bonus, we now get a really clean async g_lock_lock_send/recv that can asynchronously wait for a global lock. This would have been almost impossible to do without the dbwrap_record_watch infrastructure.
* s3: Remove a bunch of calls to procid_self()Volker Lendecke2011-12-121-1/+1
| | | | All callers to messaging_[re]init only used procid_self()
* s3:dbwrap: move all .c and .h files of dbwrap to lib/dbwrap/Michael Adam2011-07-291-1/+1
| | | | | Autobuild-User: Michael Adam <obnox@samba.org> Autobuild-Date: Fri Jul 29 13:34:22 CEST 2011 on sn-devel-104
* s3: Remove the dependency of g_lock on procid_selfVolker Lendecke2010-08-281-1/+1
| | | | procid_self() references global vars, don't depend on them unnecessarily
* s3: Add "g_lock_do" as a convenience wrapper functionVolker Lendecke2010-03-121-0/+4
|
* s3: Fix a commentVolker Lendecke2010-03-121-1/+1
|
* s3: Implement global locks in a g_lock tdbVolker Lendecke2010-02-121-0/+55
This is the basis to implement global locks in ctdb without depending on a shared file system. The initial goal is to make ctdb persistent transactions deterministic without too many timeouts.