IBM Full-System Simulator for Cell BE processor 3.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News IBM Full-System Simulator for Cell BE processor 3.0 (Default branch)
# 1  
Old 04-19-2008
IBM Full-System Simulator for Cell BE processor 3.0 (Default branch)

IBM Full-System Simulator for Cell BE processor is a full-system simulation infrastructure and tools for the Cell Broadband Engine (CBE) processor. A significant part of the Full-System Simulator's simulation capability is directly attributed to its simulation multitasking framework component. Developed as a robust, high-performance alternative to conventional process and thread programming, the multitasking framework is a lightweight scheduling framework that provides a complete set of facilities for creating and scheduling threads, manipulating time delays, and applying a variety of interthread communication policies and mechanisms to simulation events.License: Free for non-commercial useChanges:
Assorted bugfixes.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ns2 simulator with gcc compiler using only 1 processor(?)

Hi! I am using the ns2.31 simulator in Ubuntu 9.04. I have developed my program and when I simulate it (calling ns2 from Ubuntu default shell, that uses gcc), I notice that only 1 of the 2 processors available in my notebook seems to be used (simulations are very heavy and my notebook stays... (5 Replies)
Discussion started by: Alice236
5 Replies

2. Filesystems, Disks and Memory

File system simulator

Can anyone suggest me good links where i can read about unix file system and how it was created? (2 Replies)
Discussion started by: meet_pavithra
2 Replies
Login or Register to Ask a Question
processor_sets(4)					     Kernel Interfaces Manual						 processor_sets(4)

NAME
processor_sets - Collections of processors DESCRIPTION
A processor set is a collection of processors. When a processor set is first created, it does not contain any processors. You can add processors to a processor set, remove processors from a processor set, and also destroy the processor set. In addition, you can assign specific processes to a processor set. When the system is booted, all its processors are assigned to the default processor set. Each processor in a system can be a member of only one processor set at one time. In addition, when you create a process, it is assigned to a processor set. Unless you indicate a specific processor set, a process is assigned to the default processor set. A process can execute only on an processor that is included in the processor set to which the process is assigned. If you assign a process to an empty processor set, it will not execute until a processor is assigned to the processor set or until the process is assigned to another processor set. Use the pset_create command or the create_pset function to create a processor set. When you first create a processor set, it does not con- tain any processors. Use the pset_assign_cpu command or the assign_cpu_to_pset function to assign processors to a specific processor set. When you assign a processor to a specific processor set, the processor is removed from its current processor set. Use the pset_destroy command or the destroy_pset function to destroy a processor set. Processors that belong to a destroyed processor set are assigned to the default processor set. Use the pset_assign_pid command or the assign_pid_to_pset function to assign a process to a specific processor set. In addition, you can request that a process has exclusive access to a processor set. If a process has exclusive access to a processor set, no other process is able to use that processor set. If a process has exclusive access to a processor set, that access will be cleared automatically when the process exits. Note that if a process is already assigned to a processor set, a request for exclusive access to that processor set will be denied. Use the pset_info command to display the status of each processor set on the system as well as the status of each processor. You must be root to create and destroy processor sets and to assign a processor to a processor set. Processor set creation and destruction and processor assignments to processor sets are logged in the /var/adm/wtmp file. FILES
/var/adm/wtmp RELATED INFORMATION
Commands: pset_create(1), pset_destroy(1), pset_info(1), pset_assign_pid(1), pset_assign_cpu(1), runon(1), psrinfo(1), psradm(8) Functions: assign_pid_to_pset(3), assign_cpu_to_pset(3), create_pset(3), destroy_pset(3) delim off processor_sets(4)