Cooper, E.C. and Draves, R.P. C Threads. Technical Report, School of Computer Science, Carnegie Mellon University, Nov. 1990.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....(e.g. in the absence of Scheduler Activations: Effective Kernel Support l 55 ACM Transactions on Computer Systems, Vol. 10, No. 1, February 1992. multiprogramming and I O) As a result, user level threads have ultimately been implemented on top of the kernel threads of both Mach (C Threads [8]) and Topaz (WorkCrews [24] User level threads are built on top of kernel threads exactly as they are built on top of traditional processes; they have exactly the same performance, and they suffer exactly the same problems. The parallel programmer, then, has been faced with a difficult dilemma: ....

DRAVES, R., AND COOPER, E. C Threads. Tech. Rep. CMU-CS-88-154, School of Computer Science, Carnegie Mellon Univ., June 1988.

....used, perhaps by providing student modifiable lower level device routines for the keyboard. 3 Other Large Projects Students have done other kinds of systems programming projects. 3. 1 Mach Threads The idea was to take the publicly available code for the Mach user level C threads package from CMU [2] and replace the Mach systems interface with a Unix, VMS, or Windows one. The C threads code can use multiple kernel threads, but doesn t require them. It uses Mach memory management primitives to assign data structures, and includes some machine dependent assembly language code for context ....

E. C. Cooper and R. P. Draves, "Cthreads, " Tech. Rep. CMU--CS--88--154, School of Computer Science, Carnegie Mellon University, February 1988.

....in a single address space, as independent trace pages are allocated for each thread. Context switching code in the kernel maps the correct per thread pages when a new thread is activated. Mach 3. 0 supports two kinds of threads: Mach threads, implemented in the kernel, and user level threads [28], implemented by a user level library. User level threads do not require special handing by the tracing system. Voluntary transfers of control between user level threads occur at basic block boundaries and use standard mechanisms that do not require special support. Involuntary transfers of ....

Eric C. Cooper and Richard P. Draves. C Threads. Tech. Rept. CMU-CS-88-154, Carnegie-Mellon University, School of Computer Science, February, 1988.

....very good support for the debugging of logic programs. 21 4.9. PIE PIE [6] the Parallel Programming and Instrumentation Environment, is a visualization system implemented on the Mach operating system to support the visualization of programs written in languages such as C, MPC [36] C threads [37], Ada and Fortran. It is not an architecture specific system and hence may be ported. Its basic platform is a workstation running the X Window System [38] When using PIE, the programmer enters a program textually and a basic visualization showing the code s principle constructs, e.g. syncs, ....

E. C. Cooper and R. P. Draves. C Threads. Technical Report, CMU-CS-88-154, School of Computer Science, Carnegie Mellon University, 1988.

....protein folding, graphic rendering, backtrack search, and the Socrates chess program, which won second prize in the 1995 ICCA World Computer Chess Championship. 1 Introduction Multithreading has become an increasingly popular way to implement dynamic, highly asynchronous, concurrent programs [1, 9, 10, 11, 12, 13, 16, 21, 23, 24, 26, 27, 30, 36, 37, 39, 42, 43]. This research was supported in part by the Advanced Research Projects Agency under Grants N00014 94 1 0985 and N00014 92 J 1310. Robert Blumofe was supported in part by an ARPA High Performance Computing Graduate Fellowship. Keith Randall is supported in part by a Department of Defense NDSEG ....

Cooper, E. C. and Draves, R. P. C Threads. Tech. Rep. CMU-CS-88-154, School of Computer Science, Carnegie-Mellon University, Jun. 1988.

....group termination operations is to predictably manage the latency inherent in the multiprocessor architecture. This is addressed in Section 3.3.6, Section 4.4, and Section 5.2. 3. 3 Constructs The convention adopted for the syntax of the constructs in the UMass Spring thread package is based on [13] and [14] The focus of the presentation is how each construct facilitates the predictable execution of hard real time computation. 3.3.1 Creation of Processes and Threads RESULT create process (name, executable) char name; char executable; The creation of a process requires the ....

Eric C. Cooper and Richard P. Draves, "C threads," Tech. Rep. CMU- CS-88-154, School of Computer Science, Carnegie Mellon University, Pittsburg, PA, Feb. 1990.

No context found.

DRAVES, R., AND COOPER, E. C Threads. Tech. Rep. CMU-CS-88-154, School of Computer Science, Carnegie Mellon June 1988.

....Note that the process set attribute of the layoutSDL statement and the processors attribute of the thread SDL statement are used for different design decisions. 3.2 Spring C This section discusses the thread language constructs for Spring C. The convention adopted for the syntax is based on [10] and [11] RESULT sync thg sched (thg, thg params, rel time, deadline, value, max wait) any t thg, thg params; int rel time, deadline, value, max wait; The sync thg sched procedure is used by a thread that requires an Independent guarantee to attempt to spawn a new thread and wait for a ....

....difficult if not impossible. If an application could arbitrarily decide to change from one thread to another, resources would be requested and released in non determinate manner. 6. 3 Schwan s Real Time Threads The real time threads package of Schwan [11] is based on the Mach C Threads interface [10]. The approach taken is that the schedulability of a thread should be guaranteed before it is actually run. This guarantee can be made at either program compilation time or at the time of thread creation. The approach here is that higher level operating system software reacts according to the ....

E.C. Cooper and R.P. Draves, "C threads," Tech. Rep. CMU- CS-88-154, School of Computer Science, Carnegie Mellon University, Pittsburg, PA, Feb. 1990.

No context found.

Cooper, E.C. and Draves, R.P. C Threads. Technical Report, School of Computer Science, Carnegie Mellon University, Nov. 1990.

No context found.

Cooper, E.C., and Draves, R.P. June 1988."C Threads".CMU-CS-88-154, School of Computer Science, Carnegie Mellon University.

No context found.

Cooper, E.C., and Draves, R.P. June 1988."C Threads".CMU-CS-88-154, School of Computer Science, Carnegie Mellon University.

No context found.

Eric C. Cooper and Richard P. Draves, C Threads, School of Computer Science, Carnegie Mellon University, Technical Report CMU-CS-88-154, (June, 1988).

No context found.

E.C. Cooper and R.P. Draves, "C Threads", Technical Report No. CMU-CS-88--154, School of Computer Science, Carnegie Mellon University, Pittsburgh, PA, June 1988.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC