mirror of
https://git.openafs.org/openafs.git
synced 2025-01-31 05:27:44 +00:00
doc: Add introduction and credits to ubik.txt
Credit where it's due. And the remainder of the introduction may provide some useful context too. Reviewed-on: https://gerrit.openafs.org/12644 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Benjamin Kaduk <kaduk@mit.edu> (cherry picked from commit d0b64a4a1b61b5e22f0e3fe509f8facd30bc2b74) Change-Id: I786bf17b58d0f666bf12f94341ee02a56e0baa71 Reviewed-on: https://gerrit.openafs.org/12646 Tested-by: BuildBot <buildbot@rampaginggeek.com> Reviewed-by: Michael Meffie <mmeffie@sinenomine.net> Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
This commit is contained in:
parent
c7eab69f2a
commit
99f96074cb
@ -1,8 +1,20 @@
|
||||
This file contains a threading analysis of Ubik prepared by
|
||||
Jeffrey Hutzelman and sent ot the openafs-devel@openafs.org
|
||||
Jeffrey Hutzelman and sent to the openafs-devel@openafs.org
|
||||
mailing list in February 2011, archived at:
|
||||
https://lists.openafs.org/pipermail/openafs-devel/2011-February/018329.html
|
||||
|
||||
A while ago, Jeff Altman asked me to do an analysis of the Ubik code with
|
||||
repsect to threading, to try to determine how ready the code is to be moved
|
||||
from an LWP-based environment to one using preemptive POSIX threads, and
|
||||
what it will take to get it the rest of the way there. Now that the work
|
||||
is complete, I'm posting the complete analysis and my recommendations for
|
||||
discussion and as a backdrop for changes I expect to see proposed in the
|
||||
near future.
|
||||
|
||||
This work was funded by Your File System, Inc.
|
||||
|
||||
-- Jeff
|
||||
|
||||
INTRODUCTION
|
||||
|
||||
This document describes the structure of Ubik, with an eye toward
|
||||
|
Loading…
x
Reference in New Issue
Block a user