Searched refs:control (Results 51 - 75 of 137) sorted by relevance

123456

/barrelfish-2018-10-04/lib/ahci/
H A Dahci.c321 static errval_t ahci_control(struct ahci_binding *_binding, idc_control_t control) argument
349 binding->control = ahci_control;
/barrelfish-2018-10-04/doc/006-routing/
H A DRouting.tex165 The virtual circuit switching approach would also allow to reserve some resources on the nodes for each channel. Per-channel reserved resources could include buffer space to save received, but not yet forwarded messages, or bandwidth on the ICD links. This is potentially very useful for congestion and flow control. Note that we cannot simply drop messages in case of congested links, as we want to provide a reliable messaging service. As of now, we do not reserve resources on the nodes, but allocate required resources dynamically.
232 In order to support sending messages, the existing messaging interfaces between dispatchers and their local monitor, and between monitors has been extended. Each multi-hop message contains a VCI, a field encoding the direction of the message and the message payload (as a dynamic array). Furthermore, it contains one field encoding message flags and another field used to acknowledge received messages. Those two fields are used for flow control (see section~\ref{section: flow control}).
277 \section{Flow control}
278 \label{section: flow control}
279 It is possible that one dispatcher on a multi-hop channel is sending at a faster rate than the receiving dispatcher can handle incoming messages and process them. Because we want to provide a reliable messaging service, we cannot just drop messages in such a case, but have to buffer them and deliver them eventually. To limit the space needed to buffer undelivered messages, we decided to implement a flow control mechanism within the multi-hop interconnect driver. The flow control mechanism allows the receiving dispatcher to control the transmission speed, so that it is not overwhelmed with messages.
281 We decided to use a credit-based flow control mechanism: The number of messages in flight at any given time is limited. Once a sender has reached this limit, he has to wait until he receives an acknowledgement that the receiver has processed previously sent messages. We call this limit the \emph{window size}.
283 The flow control mechanis
[all...]
/barrelfish-2018-10-04/usr/eclipseclp/documents/embedding/
H A Dembtcl.tex145 The control flow between Tcl and {\eclipse} is conceptually thread-based.
147 goal is posted from Tcl, and control is transferred automatically to
152 transfer of control.
187 "yield" if control was transferred because of a
207 can be handled. Afterwards the control is passed back to Tcl.
238 also has the effect of briefly transferring control to the other side to
412 flushes it. This will briefly pass control back to Tcl, the {\bf
414 added to its arguments), afterwards control is passed back to
426 This will briefly yield control back to Tcl, the
428 afterwards control i
[all...]
H A Dembjava.tex581 in the execution of the {\eclipse} goal. If the goal succeeds, control
607 During the execution of the {\tt rpc}\index{rpc() method} method, control
610 \ref{sec:ji-using-queue-streams}, control is sometimes temporarily
922 can be used independently of which side has control.
929 even while the ECLiPSe side has control, e.g. during an RPC. This
940 data arrives from the Java side. If the ECLiPSe side has control at
942 may be deferred until ECLiPSe has control back.
1009 read the data. Otherwise, the write-operation may block, and control will
1030 side has control.
1159 stack and the control stac
[all...]
H A Dembvb.tex95 'Fail' is returned if the goals fail, and 'Yield' if control was
145 The maximum size of the {\eclipse} local/control stack in bytes.
H A Dembed.tex248 At particular points during its execution {\eclipse} will yield control
280 data and yielding control to the other thread.
298 In {\eclipse} control is normally implicit. Control returns to C++ when all
325 resume the {\eclipse} execution and the goals succeed, then control returns
421 Although implicitly yielding control when a set of goals succeeds
423 control to the C++ level. This is done with the
425 predicate. This yields control to the calling C++ program.
H A Dembsumc.tex247 as well as subsequent waking will only happen once control is
266 Waking will only happen once control is returned to {\eclipse}
333 PFAIL is returned if the goals fail, and PYIELD if control was
351 If the return value is PYIELD, control was yielded because of a
470 that require only infrequent call-return style control transfers
H A Dembsumcxx.tex244 as well as subsequent waking will only happen once control is
265 Waking will only happen once control is returned to {\eclipse}
307 goals fail, and EC_yield if control was yielded because of a
/barrelfish-2018-10-04/usr/eclipseclp/documents/internal/kernel/
H A Dbuiltins.tex70 Built-ins and language constructs to control execution are mostly
169 Everything related to suspensions, priority- and data-driven control.
/barrelfish-2018-10-04/usr/drivers/lpc_timer/
H A Dmain.c311 b->control(b, IDC_CONTROL_CLEAR_SYNC);
/barrelfish-2018-10-04/doc/015-disk-driver-arch/
H A Dintro.tex49 address space is divided into two areas: global registers for control of the
61 Every port area (\autoref{fig:port_mem}) contains further control registers and
/barrelfish-2018-10-04/usr/eclipseclp/documents/userman/
H A Dumsparallel.tex67 you to dynamically control worker configuration during the session.
96 \item there is no programmer control over which worker takes which
113 A parallel primitive that is useful to build upon is \bipref{fork/2}{../bips/kernel/control/fork-2.html}.
209 Worker management is also possible under program control. Use the
245 \bipref{mutex/2}{../bips/kernel/control/mutex-2.html}. It can be used to make a sequence of several goals atomic,
H A Dumsprofile.tex242 %of the procedure \bipref{!/0}{../bips/kernel/control/I-0.html}, it means that some cuts in
258 %[eclipse 3]: debug(go_qsort). % run program under debugger control
324 %[eclipse 4]: debug(go_qsort). % run program under debugger control
H A Dumsmacros.tex84 The following declarations and built-ins control macro expansion:
513 term is transformed, unless it is enclosed in curly brackets. The control
520 \bipref{phrase/3}{../bips/kernel/control/phrase-3.html}.
521 The first argument of \bipref{phrase/3}{../bips/kernel/control/phrase-3.html} is
572 using \bipref{phrase/3}{../bips/kernel/control/phrase-3.html}. If the predicate
593 The predicate \bipref{phrase/3}{../bips/kernel/control/phrase-3.html} may be
H A Dumsmodules.tex359 \txtbipref{:/2}{(:)/2}{../bips/kernel/control/N-2.html}
381 The \txtbipref{:/2}{(:)/2}{../bips/kernel/control/N-2.html} primitive can be used to
604 \biptxtrefni{call(Goal)@Module}{(@)/2}{../bips/kernel/control/A-2.html}%
650 \txtbipref{@/2}{(@)/2}{../bips/kernel/control/A-2.html}%
671 \item \txtbipref{:/2}{(:)/2}{../bips/kernel/control/N-2.html}
673 \item \biptxtrefni{@/2}{(@)/2}{../bips/kernel/control/A-2.html}%
H A Dumsintro.tex48 high-level modelling and control language, interfaces to third-party
236 %possible to implement almost any control strategy.
306 %tool for the integration of non-Prolog data and control into {\eclipse}.
H A Dumsmemory.tex187 \index{control stack}
196 Disjunctions (\bipref{;/2}{../bips/kernel/control/O-2.html}) also create
267 Nevertheless, there are some predicates to control their action.
/barrelfish-2018-10-04/usr/eclipseclp/documents/tutorial/
H A Dmodelling.tex48 adding control information that enables a computer to deduce a solution.
115 \item Adding control annotations, e.g.
135 Specification is mixed with procedural control.
/barrelfish-2018-10-04/doc/011-idc/
H A DIDC.tex489 /* perform control operations */
490 iface_control_fn *control;
507 \lstinline+change_waitset()+ control function must be used.
599 continuation function, or by using the \lstinline+register_send()+ control
610 Four standard control functions are defined for all binding implementations,
613 and \lstinline+control+.
648 \subsubsection*{control}
651 typedef errval_t iface_control_fn(struct iface_binding *binding, idc_control_t control);
654 This function provides a generic control mechanism. The currently-defined
655 control operation
646 and running its internal event handlers. subsubsection
[all...]
/barrelfish-2018-10-04/usr/eclipseclp/documents/megalog/
H A Dbackwards-sec.tex110 control the debugger.
H A Dmultiuser-sec.tex67 where the argument specifies the database that the server should control.
166 \eclipse uses the {\em Two Phase Locking} algorithm to control
184 Concurrency control is performed automatically behind
/barrelfish-2018-10-04/usr/eclipseclp/Kernel/lib/
H A Dtoplevel.pl54 % Execute the specified goal under control of the toplevel.
485 % Eclipse is running and has control
493 % Once Eclipse has control back, it executes 'abort' handler
656 calling throw(end) will return the control to the previous level.
/barrelfish-2018-10-04/usr/eclipseclp/icparc_solvers/
H A Dic_probing_for_scheduling.pl35 % - add facilities to control propagation during probing
449 the user more control.
457 The options offer user control over
H A Dprobing_for_scheduling.pl36 % - add facilities to control propagation during probing
449 the user more control.
457 The options offer user control over
/barrelfish-2018-10-04/doc/019-device-drivers/
H A DDeviceDriver.tex80 instantiated driver (see Driver Instance) in order to control its
147 grained control over the life-cycle of the instance. It exports the following
160 Legacy drivers live within a 9single) domain and the structure, as well as the control
414 control for a specific PCI device. The device is identified by using the
495 you a way to have fine grained, page level access control on memory. In
578 \fnname{spawn\_init\_common} is setting up a new dispatcher control block, for

Completed in 202 milliseconds

123456