mirror of
https://github.com/samba-team/samba.git
synced 2024-12-28 07:21:54 +03:00
07ade5e488
The problem we have is this:
- we want the client smbd processes to be able to 'shortcut' access
to the ltdb, by directly accessing the ltdb, and if the header of
the record shows we are the dmaster then process immediately, with
no overhead of talking across the unix domain socket
- a client doing a shortcut will use tdb_chainlock() to lock the
record while processing
- we want the main ctdb daemon to be able to set locks on the
record, and when those locks collide with a 'shortcut' fcntl lock,
we want the ctdb daemon to keep processing other operations
- we don't want to have to send a message from a smbd client to the
ctdbd each time it releases a lock
The solution is shown in this example. Note that the expensive fork()
and blocking lock is only paid in case of contention, so in the median
case I think this is zero cost.
(This used to be ctdb commit a3248c3e2b740cd2403acffd3c1f6a33dca0ea03)
|
||
|---|---|---|
| .. | ||
| 1node.txt | ||
| 4nodes.txt | ||
| bench1.sh | ||
| bench-ssh.sh | ||
| bench.sh | ||
| cmdline.c | ||
| cmdline.h | ||
| ctdb_bench.c | ||
| ctdb_fetch1.c | ||
| ctdb_fetch.c | ||
| ctdb_messaging.c | ||
| ctdb_test.c | ||
| fetch1.sh | ||
| fetch.sh | ||
| lockwait.c | ||
| messaging.sh | ||
| nodes.txt | ||
| test1.sh | ||
| test.sh | ||