aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorLudovic Courtès <ludovic.courtes@inria.fr>2018-04-02 22:25:23 +0200
committerLudovic Courtès <ludovic.courtes@inria.fr>2018-04-02 22:25:23 +0200
commitf090c0f4786c789070e2eae740914e06ab0ab989 (patch)
tree7dc87e888a90233bd20e161af540bb5d5722c4ee /src
parent543709fbca4f20164b30f1dded33442c373fc9d2 (diff)
downloadcuirass-f090c0f4786c789070e2eae740914e06ab0ab989.tar
cuirass-f090c0f4786c789070e2eae740914e06ab0ab989.tar.gz
utils: Add critical sections.
* src/cuirass/utils.scm (make-critical-section) (call-with-critical-section): New procedures. (with-critical-section): New macro. * src/cuirass/http.scm (with-database-access): Remove. (handle-build-request, handle-builds-request, url-handler): Use 'with-critical-section' instead of 'with-database-access'. (run-cuirass-server): Remove 'spawn-fiber' call. Use 'make-critical-section' instead.
Diffstat (limited to 'src')
-rw-r--r--src/cuirass/http.scm40
-rw-r--r--src/cuirass/utils.scm34
2 files changed, 44 insertions, 30 deletions
diff --git a/src/cuirass/http.scm b/src/cuirass/http.scm
index 59a6c57..31960ac 100644
--- a/src/cuirass/http.scm
+++ b/src/cuirass/http.scm
@@ -70,26 +70,17 @@
(#:releasename . #nil)
(#:buildinputs_builds . #nil)))
-(define-syntax-rule (with-database-access channel db exp ...)
- "Evaluate EXP with DB bound to the database. Do that by passing EXP over to
-CHANNEL for execution by the database fiber. This ensures that the database
-handle is only ever accessed from on thread, the thread where the database
-fiber runs (IOW, it creates a critical section.)"
- (begin
- (put-message channel (lambda (db) exp ...))
- (get-message channel)))
-
(define (handle-build-request db-channel build-id)
"Retrieve build identified by BUILD-ID over DB-CHANNEL and convert it to
hydra format. Return #f is not build was found."
- (let ((build (with-database-access db-channel db
+ (let ((build (with-critical-section db-channel (db)
(db-get-build db build-id))))
(and=> build build->hydra-build)))
(define (handle-builds-request db-channel filters)
"Retrieve all builds matched by FILTERS in DB-CHANNEL and convert them to
Hydra format."
- (let ((builds (with-database-access db-channel db
+ (let ((builds (with-critical-section db-channel (db)
(with-time-logging "builds request"
(db-get-builds db filters)))))
(map build->hydra-build builds)))
@@ -165,7 +156,7 @@ Hydra format."
'method-not-allowed)
(((or "jobsets" "specifications") . rest)
(respond-json (object->json-string
- (with-database-access db-channel db
+ (with-critical-section db-channel (db)
(db-get-specifications db)))))
(("build" build-id)
(let ((hydra-build (handle-build-request db-channel
@@ -174,7 +165,7 @@ Hydra format."
(respond-json (object->json-string hydra-build))
(respond-build-not-found build-id))))
(("build" build-id "log" "raw")
- (let ((build (with-database-access db-channel db
+ (let ((build (with-critical-section db-channel (db)
(db-get-build db (string->number build-id)))))
(if build
(match (assq-ref build #:outputs)
@@ -233,20 +224,13 @@ Hydra format."
(let* ((host-info (gethostbyname host))
(address (inet-ntop (hostent:addrtype host-info)
(car (hostent:addr-list host-info))))
- (db-channel (make-channel)))
- (log-message "listening on ~A:~A" address port)
- ;; Spawn a fiber to process database queries sequentially. We need this
- ;; because guile-sqlite3 handles are not thread-safe (caching in
- ;; particular), and creating one new handle for each request would be
- ;; costly and may defeat statement caching.
- (spawn-fiber
- (lambda ()
- (let loop ()
- (match (get-message db-channel)
- ((? procedure? proc)
- (put-message db-channel (proc db))))
- (loop))))
+ ;; Spawn a fiber to process database queries sequentially. We need
+ ;; this because guile-sqlite3 handles are not thread-safe (caching in
+ ;; particular), and creating one new handle for each request would be
+ ;; costly and may defeat statement caching.
+ (db-channel (make-critical-section db)))
+ (log-message "listening on ~A:~A" address port)
;; Here we use our own web backend, call 'fiberized'. We cannot use the
;; 'fibers' backend that comes with Fibers 1.0.0 because it does its own
@@ -274,7 +258,3 @@ Hydra format."
request body '())))
(write-client impl server client response body)))))
(loop)))))
-
-;;; Local Variables:
-;;; eval: (put 'with-database-access 'scheme-indent-function 2)
-;;; End:
diff --git a/src/cuirass/utils.scm b/src/cuirass/utils.scm
index 2e71910..bbecfb6 100644
--- a/src/cuirass/utils.scm
+++ b/src/cuirass/utils.scm
@@ -33,6 +33,11 @@
object->json-string
define-enumeration
unwind-protect
+
+ make-critical-section
+ call-with-critical-section
+ with-critical-section
+
non-blocking
essential-task
bytevector-range))
@@ -87,6 +92,35 @@ delimited continuations and fibers."
(conclusion)
(apply throw args)))))
+(define (make-critical-section . args)
+ "Return a channel used to implement a critical section. That channel can
+then be passed to 'join-critical-section', which will ensure sequential
+ordering. ARGS are the arguments of the critical section.
+
+Critical sections are implemented by passing the procedure to execute to a
+dedicated fiber."
+ (let ((channel (make-channel)))
+ (spawn-fiber
+ (lambda ()
+ (let loop ()
+ (match (get-message channel)
+ ((? procedure? proc)
+ (put-message channel (apply proc args))))
+ (loop))))
+ channel))
+
+(define (call-with-critical-section channel proc)
+ "Call PROC in the critical section corresponding to CHANNEL. Return the
+result of PROC."
+ (put-message channel proc)
+ (get-message channel))
+
+(define-syntax-rule (with-critical-section channel (vars ...) exp ...)
+ "Evaluate EXP... in the critical section corresponding to CHANNEL.
+VARS... are bound to the arguments of the critical section."
+ (call-with-critical-section channel
+ (lambda (vars ...) exp ...)))
+
(define (%non-blocking thunk)
(let ((channel (make-channel)))
(call-with-new-thread