X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fthreads.texi;h=e6e64f14532360ce098fc85670e053d3b4ebcede;hb=effe2893afdc6c4f8507f81dd36cd08ef3833ede;hp=0bc1534eb9c207e8166da68c8da37d2bc288a405;hpb=1c9362e5a55a4e1778f0e3bd81518ca6b05936cf;p=pintos-anon

diff --git a/doc/threads.texi b/doc/threads.texi
index 0bc1534..e6e64f1 100644
--- a/doc/threads.texi
+++ b/doc/threads.texi
@@ -531,6 +531,12 @@ Here's a summary of our reference solution, produced by the
 @command{diffstat} program.  The final row gives total lines inserted
 and deleted; a changed line counts as both an insertion and a deletion.
 
+The reference solution represents just one possible solution.  Many
+other solutions are also possible and many of those differ greatly from
+the reference solution.  Some excellent solutions may not modify all the
+files modified by the reference solution, and some may modify files not
+modified by the reference solution.
+
 @verbatim
  devices/timer.c       |   42 +++++-
  threads/fixed-point.h |  120 ++++++++++++++++++
@@ -721,6 +727,8 @@ scheduler at the same time.
 @item Can I use one queue instead of 64 queues?
 
 Yes, that's fine.  It's easiest to describe the algorithm in terms of 64
-separate queues, but that may not be the best implementation.  If you
-use a single queue, it should probably be sorted.
+separate queues, but that doesn't mean you have to implement it that
+way.
+
+If you use a single queue, it should probably be sorted.
 @end table