Advanced Operating Systems
M5: File System
In this milestone, you will:
The SOS file system features a flat directory structure, containing
files and the terminal device
You may want to maintain file descriptors containing a present read position in the file. This requires some minimal Process Control Block (PCB) data structure. Again, you will need to modify this structure as you go on, so do not waste too much time on the full details right now. You may wish to initially only deal with a single client process, data on which is kept in a single PCB variable. This avoids dealing with process IDs for the time being.
The low-level file system is implemented by the NFS file system on your host machine. You are provided with an NFS client library for accessing files on your host Linux machine. Once again, it is your responsibility to understand the working of the provided code.
IP stack and NFS
You need to update the 100ms tick you implemented in milestone
1 to call
Apart from the initialisation and mounting filesystems, the NFS library provides an asynchronous interface, which means when you call the function, you must also provide a callback function which will be called when the transaction is completed. This should make it easy to provide a blocking interface to clients, without blocking the whole system.
The NFS server you will be talking to is your host machine. The
filesytem you mount is /var/tftpboot/$USER where
One of the major issues you will need to deal with in this milestone is
converting an asynchronous interface (as provided by
If you are planning on doing the file system caching, or dynamic file system advanced component you should probably consider them in your design now.
For file descriptor allocation, we recommend implementing the lowest-available policy, i.e., returning the lowest numbered currently unused file descriptor. This will simplify later milestones.
Once you have a your file system up and running, you must use your timer to benchmark your filesystem I/O performance. Don't leave this until the last minute as it tends to be more time consuming than you expect (e.g. it finds bugs).
The most obvious (and required) metric is achieved bandwidth for reads and writes. This is simply the maximum number of bytes per second you can transfer from the remote host to your user address space.
Given that you are likely to max-out the slow ethernet adapter in the kit, CPU utilisation is also a useful metric to measure. Given two systems that both max-out the Ethernet adapter, the one with lower CPU utilisation is more efficient. If you decide to look at CPU utilisation, ask your demonstrator or the forum how best to tackle measuring it.
When benchmarking you may find it useful to measure other costs such as latency, copying costs, etc. You may use a spreadsheet program, the gnuplot utility or any other chart generation program.
Note: we expect any reported results to be the average of multiple runs (e.g. >= 5, ideally > 9). Standard deviations are expected for any reported results.
Some things you may like to think about while you're benchmarking are:
Feel free to discuss benchmarking methodologies etc. and post interim results on the forum. Which group has the most efficient design?
You must demonstrate that you have implemented the
You will need to present at least two graphs to your tutor. The two required graphs show bandwidth for file I/O while varying I/O request size and underlying NFS packet size (for appropriately large I/O requests). You must be able to explain why the graphs look the way they do. Your numbers must be taken using your timer driver. You can also show more (pertinent) graphs if you like. The results need to be an average of multiple samples. Standard deviations should be shown if significant.
NOTE: The achieved bandwidth on the graph will not be assessed directly. However, clearly better performance shows a better filesystem implementation. Your tutor is interested in your ability to explain what & how you measured.
As always you should be able to explain any design decisions you made, specifically, the design of your open file table and how you dealt with the asynchronous/synchronous problem.
Last modified: 29 Aug 2014.