Remember the assignment 3 performance graphs?
While this year it was just the current students' kernels and the
solution set, we actually have an archive of kernels from past years
that are supposed to serve as extra points of comparison. This year,
because I was called away at exactly the wrong moment, no data from
those kernels was ever collected or posted. (But next year we hope to
do better.)
There's also a similar archive for assignment 4 performance.
We want more kernels for the archive. For this, we want your
permission (just to be on the safe side). We will then import your
kernel into the course staff's CVS repository and take care of keeping
it more or less up to date with respect to future changes in OS/161.
(This lets us generate meaningful performance numbers.)
So, if you're willing to let us do this, with either your assignment 3
and/or your assignment 4 submissions, please mail cs161@fas and tell
us which submissions to save. (If you did copy-on-write VM for
assignment 5, we'll take that too.)
You don't have to do any work for this... although of course I'll take
any fixes you want to provide - or even just bug reports. :-)
It DOES NOT MATTER if your code was fast or slow - in fact, since
future students will be seeing these and maybe implicitly comparing
their code, we'd rather the archive didn't get biased in favor of
faster submissions. (Although we do prefer submissions that actually
run most of the tests.)
And of course neither your group name nor your own names will be
attached to any performance stats we post.
Finally, if you have any comments about how the assignment 3 graph was
handled (this includes stuff like "it intimidated me" or "it induced
me to get started on the assignment earlier"), and whether you think
we should do the same thing for assignment 4, please let me know.
We've submitted grades so nothing you say can be used against you,
even if we were so inclined. :-)
--
- David A. Holland / dholland(a)eecs.harvard.edu
Show replies by date