| 
|
QuoteRef: cherDR3_1988
topics >
all references >
ThesaHelp:
ACM references a-e
ThesaHelp:
references c-d
Group:
distributed systems
Topic:
a single system image
Topic:
implementing distributed systems and applications
Topic:
group names
Topic:
file input/output
Topic:
file directory
Topic:
name server or name directory
Topic:
object-defined names
Topic:
names independent of objects
Topic:
binding of names to objects
Topic:
locating named objects by broadcast
Topic:
hierarchical naming
Topic:
unique names
Topic:
data caching
Topic:
information as a hint
Topic:
optimistic update for concurrency control
Topic:
unique numeric names as surrogates
Topic:
using an address as a name
Topic:
communication port
Topic:
timestamps
Topic:
reliability of distributed systems
Topic:
renaming
Topic:
client-server model for distributed systems
Topic:
security by secure domains
Topic:
memory management for programs and modules
Topic:
managing shared memory
Reference
Cheriton, D.R., "The V distributed system", Communications of the ACM, 31, 3, March 1988, pp. 314-333. Google
Notes
V was based on Thoth
315 ;;Quote: the critical facility for distributed systems is high-performance communication similar to file access
315 ;;Quote: the primary challenge of distributed systems is shared state; shared memory is the most natural model
315 ;;Quote: a distributed system needs to deal with groups of entities as well as individual ones
316 ;;Quote: V's get-byte first checks the invoker's I/O buffer; compiled in-line for speed
325 ;;Quote: in V, each object manager implements names for its objects; since name lookup is only one step of an operation; also simpler consistency
325 ;;Quote: each object directory is in a name handling process group; responds to multicasts of its name prefix (also cached)
325+;;Quote: each object directory has a unique global name prefix
325 ;;Quote: V uses a highly resilient global naming system; otherwise a failed multicast for a name may only indicate an inaccessible server
325 ;;Quote: V's name cache flushes stale data when detected by using that data
326 ;;Quote: V's object identifiers consist of an object-manager-IPC-id (changes on reboot) and a local-object-id (transient name)
326+;;Quote: permanent V objects are named with a character-string and object manager prefix
326 ;;Quote: V has globally unique, entity ids for processes, process groups, and ports; now 32-bits, will be 64-bits
327 ;;Quote: Thoth depended on T-stability (ids not reused in <T seconds); difficult to implement in a distributed environment
327+;;Quote: V went from 32-bit ids to 64-bit ids to reduce expected frequency of reuse
328 ;;Quote: with V, users can run interactive editors on any node without performance problems
328+;;Quote: with a workstation per user have a very low average load; no need for computation servers
328 ;;Quote: for remote processing, the kernel must encapsulate a program in an address space; prevents damage to other programs
ThesaHelp: ACM references a-e (259 items)
ThesaHelp: references c-d (337 items)
Group: distributed systems (14 topics, 344 quotes)
Topic: a single system image (30 items)
Topic: implementing distributed systems and applications (41 items)
Topic: group names (16 items)
Topic: file input/output (21 items)
Topic: file directory (42 items)
Topic: name server or name directory (40 items)
Topic: object-defined names (15 items)
Topic: names independent of objects (34 items)
Topic: binding of names to objects (16 items)
Topic: locating named objects by broadcast (9 items)
Topic: hierarchical naming (28 items)
Topic: unique names (57 items)
Topic: data caching (28 items)
Topic: information as a hint (18 items)
Topic: optimistic update for concurrency control (35 items)
Topic: unique numeric names as surrogates (67 items)
Topic: using an address as a name (22 items)
Topic: communication port (40 items)
Topic: timestamps (19 items)
Topic: reliability of distributed systems (33 items)
Topic: renaming (10 items)
Topic: client-server model for distributed systems (25 items)
Topic: security by secure domains (42 items)
Topic: memory management for programs and modules (12 items)
Topic: managing shared memory (74 items)