Stitch comprises four communicating processes
and many communicating threads, organized as
described below.

We assume that someone else is taking care of
providing us a 9P conversation; this might be
a network connection to a real file server or
perhaps just a connection to a local exportfs.

We then speak 9P as well.

Process 1: 9P server (provides stitched server)
	Reads requests from wire, sends them over a chan(Req*).

Process 2: 9P client #1 (talks to top server)
	Reads replies from wire, sends them over a chan(Req*).

Process 3: 9P client #2 (talks to bottom server)
	Reads replies from wire, sends them over a chan(Rep).

Process 4: The real work
	Thread 4.1: 9P request launcher
		Reads reqc, creates a new thread for each request.
	Thread 4.2, 4.3: 9P reader/writer for client #1
		The writer reads requests over a chan(Req, chan(Rep)),
		allocates a tag, saves a map from the tag to the chan(Rep),
		and sends the request.
		The reader waits for a reply over a chan(Rep) from Proc 2,
		looks up where the reply should go, and sends it along.
	Thread 4.4, 4.5: 9P reader/writer for client #2
	Thread 4.x: Work thread for an outstanding request.

