From: Ben Pfaff Date: Thu, 13 Jan 2005 06:23:32 +0000 (+0000) Subject: Improve comment. X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=546d8bf36bae548643722e1f5d55fd0fcc1c4262;p=pintos-anon Improve comment. --- diff --git a/src/threads/thread.c b/src/threads/thread.c index 01ce7d3..1e5a7d2 100644 --- a/src/threads/thread.c +++ b/src/threads/thread.c @@ -118,13 +118,15 @@ thread_print_stats (void) /* Creates a new kernel thread named NAME with the given initial PRIORITY, which executes FUNCTION passing AUX as the argument, - and adds it to the ready queue. If thread_start() has been - called, then the new thread may be scheduled before - thread_create() returns. It could even exit before - thread_create() returns. Use a semaphore or some other form - of synchronization if you need to ensure ordering. Returns - the thread identifier for the new thread, or TID_ERROR if - creation fails. + and adds it to the ready queue. Returns the thread identifier + for the new thread, or TID_ERROR if creation fails. + + If thread_start() has been called, then the new thread may be + scheduled before thread_create() returns. It could even exit + before thread_create() returns. Contrariwise, the original + thread may run for any amount of time before the new thread is + scheduled. Use a semaphore or some other form of + synchronization if you need to ensure ordering. The code provided sets the new thread's `priority' member to PRIORITY, but no actual priority scheduling is implemented.