Appeal No. 2002-0792 Application 08/801,646 The Examiner states that Anderson does not expressly teach a shared arena within the memory, wherein the shared arena includes a register save area and selecting includes the step of reading register context associated with the selected thread from one of the plurality of register save areas. See page 3 of the answer. The Examiner relies on Polychronopoulos for this teaching. The Examiner points us to page 7 and page 9 of Polychronopoulos. Upon our review of Polychronopoulos, we find that in section 3 titled “Scheduler-Kernel Interfaces” found on page 6, Polychronopoulos teaches that in order to properly support the user-level scheduling model, a set of communication points between the user-level scheduler and the kernel must be defined. Polychronopoulos then further states that these interfaces will allow the user-level scheduler to request/release processor resources and reorder run queues. Polychronopoulos then further states that the reference only defines the interface semantic and does not specify the implementation of the communication mechanism. Polychronopoulos then suggests that some implementations may choose to use a block of shared memory used between the user-level scheduler and the kernel as the communication venue while other implementations may be an explicit upcall mechanism as described in Anderson. We agree 7Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 NextLast modified: November 3, 2007