We need to handle REQUESTPAGE CONFIRMATION messages from the server.

We should log output to a file instead of printf, so we can look at it later.

We should at least write a matrix multiplication program.

We should record time required to do the multiplication on multiple machines with 1..n machines, and plot the times to determine the actual speedup.

We need this for the writeup.

Right now we just randomly return negative ints, and don't handle most of them.

We should give them meaningful names and handle each one appropriately eventually.

libdsmu should send a message to the manager of the form "REQUESTPAGE WRITE PAGENUMBER" on a write fault.

Steps to reproduce:

1. Start a manager
2. Start a client
3. Close the client
4. The manager endlessly loops printing "FUCK BAD PROTOCOL"

Unclear if the problem is in client or manager, but in any case, progress halts.

To reproduce:

1. Set size of matrix to 300 in matrixmultiply.c
2. Start manager
3. Recompile
4. ./matrixmultiply 127.0.0.1 4444 1 1

matrixmultiply will hang, and not always at the same page.

libdsmu should send a message of form REQUESTPAGE READ PAGENUMBER to the manager on a read fault.

We should actually handle faults for all heap addresses.