Commit 7c57ba4b authored by Kirill Smelkov's avatar Kirill Smelkov

.

parent 0c9c5cc6
...@@ -42,6 +42,8 @@ ...@@ -42,6 +42,8 @@
// in separate thread, because wcfs server can also send pins to client that // in separate thread, because wcfs server can also send pins to client that
// trigerred the access. // trigerred the access.
// //
// Wcfs client implements pins handling in so-called "pinner" thread(+).
//
// //
// //
// - need to maintain pinner map registry XXX no need // - need to maintain pinner map registry XXX no need
...@@ -69,6 +71,9 @@ ...@@ -69,6 +71,9 @@
// -------- // --------
// //
// (*) see wcfs.go documentation for WCFS isolation protocol overview and details. // (*) see wcfs.go documentation for WCFS isolation protocol overview and details.
// (+) currently, for simplicity, there is one pinner for each connection. In
// the future, for efficiency, it might be reworked to be one pinner thread
// that serves all connections simultaneously.
// XXX locking -> explain atMu + slaves and refer to "Locking" in wcfs.go // XXX locking -> explain atMu + slaves and refer to "Locking" in wcfs.go
// //
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment