From: Ben Pfaff Date: Tue, 16 May 2006 16:08:39 +0000 (+0000) Subject: Don't refer to user memory access as "copying". Some of the students X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=38c9c4b999e8dc097481815bb8972e3540afd2d7;p=pintos-anon Don't refer to user memory access as "copying". Some of the students don't see it that way. --- diff --git a/doc/userprog.tmpl b/doc/userprog.tmpl index 07183db..a8b4269 100644 --- a/doc/userprog.tmpl +++ b/doc/userprog.tmpl @@ -59,8 +59,7 @@ FirstName LastName ---- ALGORITHMS ---- ->> Describe your code for copying data from user programs into the kernel ->> and vice versa. +>> Describe your code for reading and writing user data from the kernel. >> Suppose a system call causes a full page (4,096 bytes) of data to be >> copied from user space into the kernel. What is the least and the @@ -100,8 +99,8 @@ FirstName LastName ---- RATIONALE ---- ->> Why did you choose to implement user-to-kernel copying the way you ->> did? +>> Why did you choose to implement access to user memory from the +>> kernel in the way that you did? >> What advantages or disadvantages can you see to your design for file >> descriptors?