/barrelfish-master/usr/eclipseclp/Shm/src/ |
H A D | shared_mem.c | 209 hd->shared_header->processes = 1; /* done last, for synchronisation */ 246 while (tmp_header->processes == 0) 284 hd->shared_header->processes++; 300 if (--hd->shared_header->processes == 0 && hd->shared_header->mapfile) 393 int processes; local 406 processes = hd->shared_header->processes; 420 hd->shared_header->processes = processes;
|
H A D | memman.h | 254 int processes; /* number of attached processes */ member in struct:shm_desc
|
/barrelfish-master/usr/eclipseclp/documents/mpslib/ |
H A D | eclipse.tex | 39 processes dynamically is therefore a general requirement, especially 43 i.e. remove idle workers (with their underlying processes) and free 47 and migrating processes since this may be too complicated, especially
|
H A D | outline.tex | 112 that enables processes to associate names with their ports. Ports 121 for the unique port identifiers. This implies that only the processes 132 \eclipse application. It are several communicating \eclipse processes 190 Although not strictly necessary, processes invoke {\it mps\_exit} just 192 and other processes. 240 All the processes of a distributed application start with associating 278 done by different processes on different machines. When you take this 475 i.e. only \eclipse processes can communicate with other \eclipse 476 processes. A logical step is to provide an interface to the message
|
/barrelfish-master/usr/eclipseclp/documents/userman/ |
H A D | umssocket.tex | 34 that can connect multiple processes on different machines 39 Sockets in general allow a networked communication among many processes, 70 which are connected through the network. It can also connect two processes 86 communicating processes. 90 one of the processes, the server, gives it a name 94 After the connection is established, both processes can read and write 404 it is limited to communications between two processes on the same Unix
|
H A D | umsopsys.tex | 255 {\eclipse} provides all the necessary built-ins needed to create UNIX processes 257 A {\eclipse} process can communicate with other processes via streams and by 306 For more sophisticated applications, the processes have to run in parallel 339 Then, by writing and reading these streams, the processes can communicate in 392 For explicitly sending signals to other processes
|
H A D | umsparallel.tex | 39 A parallel {\eclipse} session consists of a number of processes that jointly 164 since the processes involved have their own local timers, e.g.\ for 349 \item A number of worker processes {\tt eclipse.exec}. 351 They are normal sequential {\eclipse} processes that do the actual 368 session, it may be necessary to kill some processes and to remove files
|
H A D | extsuspend.tex | 311 \item \predspec{equal_lists/4} processes the arguments of compound terms. 315 \item \predspec{diff_pairs/2} processes this list.
|
H A D | umstkeclipse.tex | 307 The {\eclipse} session and the development tools are two separate processes 310 processes are synchronised in that there is a thread-like flow of control
|
H A D | umsdeveltools.tex | 234 processes this information file to produce readable HTML and plain text files.
|
H A D | umsio.tex | 320 %This mechanism is normally used to communicate with other processes
|
/barrelfish-master/usr/eclipseclp/documents/megalog/ |
H A D | multiuser-sec.tex | 48 processes communicate with the server, possibly across a network. 50 processes per database. This restriction may be lifted in future releases. 59 database and several \eclipse client processes can use the database
|
/barrelfish-master/doc/012-services/ |
H A D | Services.tex | 194 capabilities). It processes requests for memory, allocating appropriate 249 includes creating, starting, stopping, and pausing processes, as well 250 as mechanisms for loading processs, and migrating processes. Part of 267 etc. Manipulating resource usage includes scheduling processes, 608 threads, process management to attach to and control processes 729 principals service, to provide processes with the appropriate caps for
|
/barrelfish-master/usr/eclipseclp/icparc_solvers/ |
H A D | changeset.pl | 117 information to be conveyed to the code that processes the changes.
|
/barrelfish-master/usr/eclipseclp/documents/embedding/ |
H A D | embremote.tex | 48 \item The connection between the Tcl and {\eclipse} processes are established 62 program. However, as the Tcl and {\eclipse} processes are not as tightly 64 the Tcl and {\eclipse} processes is likely to be slower. 68 The interface is used by starting separate {\eclipse} and Tcl processes, and 70 attached, the Tcl and {\eclipse} processes can communicate much as in the 74 processes to allow streams of bytes to sent from one side to the other. 79 processes. Thus, typically, if the programmer wants to allow a particular 92 processes.}. At any given time, 100 An {\eclipse} process can have several attached remote processes. Each
|
H A D | embremoteproto.tex | 54 an {\eclipse} process. The processes exchange messages in the EXDR (see 57 processes can be located on any two machines which can establish socket 64 {\eclipse} processes. The attachment establishes two socket connections 65 between the two processes: 70 to the remote protocol to co-ordinate the two processes.
|
H A D | embjava.tex | 1274 depending on how the operating system allocates these between processes. 1349 \item {\eclipse} can connect to multiple Java processes using this model. 1419 only client connections made by processes on the same machine and
|
/barrelfish-master/usr/eclipseclp/documents/internal/kernel/ |
H A D | globalstate.tex | 27 shared memory system (where several processes work on a piece of
|
/barrelfish-master/doc/026-device-queues/ |
H A D | devif.tex | 88 devices like network cards and block devices but also between processes. 105 \item \textbf{Endpoint}: An endpoint is a processes or devices. 776 The IDC backend facilitates communication between two processes on either the same core 834 // In this case simple channel between two processes 858 In this case we create a queue to connect two processes. Following the creation, we cast
|
/barrelfish-master/doc/000-overview/ |
H A D | Overview.tex | 62 OS is structured as a distributed system of single-core processes atop 73 processes interrupts, pagefaults, traps, and exceptions. 86 Typically we refer to user level processes (or services or servers) as "user 146 with good support for best-effort processes as well. 591 time-sliced along with other processes, can block when waiting for I/O
|
/barrelfish-master/doc/023-coreboot/ |
H A D | coreboot.tex | 73 run as processes, but closely resemble device drivers and could equally run as
|
/barrelfish-master/doc/022-armv8/ |
H A D | report.tex | 345 user-space processes in AArch64 mode without support for virtualisation. 347 mode, and user-space processes in both AArch64 and AArch32 modes without 439 allow us to avoid multiplexing IDs among active processes, on any 516 AArch32 dispatcher processes, by marking each dispatcher with a flag
|
/barrelfish-master/doc/011-idc/ |
H A D | IDC.tex | 301 When invoked, Flounder processes a single interface file, and generates into a
|
/barrelfish-master/doc/006-routing/ |
H A D | Routing.tex | 526 The client sends messages to the server, the server processes them
|
/barrelfish-master/doc/014-bulk-transfer/ |
H A D | bulk-transfer.tex | 63 can be different. So, participating processes can't exchange the virtual
|