Searched refs:behind (Results 1 - 21 of 21) sorted by relevance
/barrelfish-master/include/vm/ |
H A D | vm_fault.c | 296 int ahead, behind, cluster_offset, error, locked, rv; local 678 behind = 0; 683 behind = 0; 698 behind = ulmin(cluster_offset, 706 &behind, &ahead); 708 faultcount = behind + 1 + ahead; 1008 faultcount > 0 ? behind : PFBAK, 1041 PAGE_SIZE + behind * PAGE_SIZE);
|
/barrelfish-master/usr/eclipseclp/documents/tutorial/ |
H A D | real.tex | 140 but a delayed goal is left behind, indicating that the result of the 175 not throw exceptions or leave behind large numbers of meaningless delayed 230 delayed goal \texttt{-0.1__0.1 >= 0} will be left behind and Code A
|
/barrelfish-master/usr/eclipseclp/documents/internal/kernel/ |
H A D | globalstate.tex | 73 For the following, it is useful to know the ideas behind the UNIX
|
H A D | kernel.tex | 824 a(A),y(Y) and leave S pointing behind it\\ 1762 behind and filling the allocated space.
|
/barrelfish-master/usr/eclipseclp/documents/userman/ |
H A D | umsstring.tex | 137 Moreover the call leaves a choicepoint behind (as shown by the more-prompt).
|
H A D | umsmemory.tex | 206 has left a choicepoint behind.
|
H A D | umsarith.tex | 211 behind which can then be inspected by the user to decide whether the
|
H A D | umsdeveltools.tex | 530 whether they left behind any choice-points for backtracking;
|
H A D | umsexcept.tex | 374 the execution continues at the point behind the call of the erroneous goal;
|
H A D | umslanguage.tex | 1074 Moreover the call leaves a choicepoint behind (as shown by the
|
/barrelfish-master/doc/004-virtual_memory/ |
H A D | VirtualMemory.tex | 170 This is hidden behind wrapper functions and most users of the library are shielded from this.
|
/barrelfish-master/usr/eclipseclp/documents/libman/ |
H A D | ic.tex | 171 interval contains the true answer. This is the principle behind the bounded 183 delayed goal is left behind. This delayed goal indicates that the 185 goal is true. For example, if the delayed goal left behind was 1286 behind and may perform extra propagation before returning (it may be
|
/barrelfish-master/usr/eclipseclp/documents/megalog/ |
H A D | multiuser-sec.tex | 184 Concurrency control is performed automatically behind
|
H A D | database-sec.tex | 908 is valid in an {\bf isr} clause behind the {\bf where}.
|
/barrelfish-master/doc/015-disk-driver-arch/ |
H A D | libahci.tex | 7 The intent behind \libahci is to provide an easy-to-use low-level interface to
|
/barrelfish-master/doc/019-device-drivers/ |
H A D | DeviceDriver.tex | 288 next chapters we will have a closer look on what is actually happening behind
|
/barrelfish-master/doc/017-arm/ |
H A D | ARM.tex | 279 split. The idea behind a memory split is to separate kernel code from
|
/barrelfish-master/usr/eclipseclp/documents/search/ |
H A D | search.tex | 1515 just described labelling procedure, \verb'label/1', does not leave behind a
|
/barrelfish-master/doc/014-bulk-transfer/ |
H A D | bulk-transfer.tex | 199 %behind them yet, but my preliminary guess was that context switches on
|
/barrelfish-master/lib/tommath/ |
H A D | tommath.tex | 254 That is to not only explain a limited subset of the core theory behind the algorithms but also the various ``house keeping'' 414 answer these questions will feel comfortable with the concepts behind the topic at hand. 844 The logic behind the algorithm is extended by marking cleared mp\_int structures so that subsequent calls to this 2177 motivation behind this change is due to the way this function is typically used. Algorithms such as mp\_add store the result in an optionally 3634 fairly slow if not unavailable. The idea behind fixed point arithmetic is to take a normal $k$-bit integer data type and break it into $p$-bit
|
/barrelfish-master/doc/002-mackerel/ |
H A D | Mackerel.tex | 1852 this in favor of masks and shifts, hidden behind inline functions.
|
Completed in 202 milliseconds