Searched refs:likely (Results 1 - 25 of 41) sorted by relevance

12

/barrelfish-master/lib/devif/backends/net/mlx4/include/linux/
H A Dcompiler.h65 #define likely(x) __builtin_expect(!!(x), 1) macro
H A Dmath64.h96 if (likely(((n) >> 32) == 0)) { \
/barrelfish-master/lib/devif/backends/net/mlx4/drivers/infiniband/hw/mthca/
H A Dmthca_srq.c572 if (likely(nreq)) {
644 if (likely(nreq)) {
H A Dmthca_qp.c1566 if (likely(cur + nreq < wq->max))
1797 if (likely(nreq)) {
1909 if (likely(nreq)) {
2138 if (likely(nreq)) {
2226 if (likely(nreq)) {
H A Dmthca_cq.c650 if (likely(free_cqe)) {
/barrelfish-master/usr/eclipseclp/documents/userman/
H A Dumsparallel.tex300 likely that some complex builtins (e.g. \bipref{select/3}{../bips/kernel/obsolete/select-3.html}) will not be completely
329 When the system complains about lack of swap space, then it is likely
375 (eclipse.exec). This will most likely require a hard kill (-9).
H A Dumserrors.tex352 These exits can be caught by wrapping a goal that is likely
H A Dumsexcept.tex860 %One of the most likely uses for the block
863 %handling via user-definable handlers, the likely use of the block
H A Dumsmodules.tex436 However, this is likely to be less efficient because it prevents
H A Dumstkeclipse.tex242 The user should most likely provide a connection for the output stream
/barrelfish-master/lib/devif/backends/net/mlx4/drivers/infiniband/hw/mlx4/
H A Dsrq.c353 if (likely(nreq)) {
/barrelfish-master/usr/eclipseclp/Kernel/lib/
H A Dkernel_bips.pl362 % sorting the list first is not necessary, but likely to reduce
H A Dfd.pl3174 most likely to fail, because this will cut down the size of the search
3201 most likely to fail, because this will cut down the size of the search
3205 with more constraints are more likely to fail when instantiated.
H A Dquintus.pl93 differs substantially. The meta-predicates very likely have
H A Dsuspend.pl195 % likely to be already in descending order, due to new suspensions
/barrelfish-master/usr/eclipseclp/documents/mpslib/
H A Declipse.tex61 therefore likely that worker migration will require facilities for
H A Doutline.tex135 the TCP/IP standard which is likely to be the basis for your local area
/barrelfish-master/usr/eclipseclp/Contrib/
H A Dapplic.pl196 % you are more likely to want somechk with its single solution.
/barrelfish-master/doc/018-Practical-guide/
H A Dreadme.tex27 The biggest compatibility problems are likely to be in the PCI/ACPI code. We
/barrelfish-master/doc/012-services/
H A DServices.tex634 %% The device manager will likely be implemented as a multithreaded
766 It will likely also be implemented using locking and group
811 The implementation will likely use locking, and may require the SKB to
848 Its implementation is likely to use locking.
861 The implementation of virtual memory management is likely to use
/barrelfish-master/usr/eclipseclp/documents/tutorial/
H A Dmodelling.tex351 likely be still uninstantiated. Therefore, the condition will in general
H A Deprolog.tex772 This is however likely to be less efficient because it prevents
915 This is likely to be the largest consumer of memory.
/barrelfish-master/usr/eclipseclp/documents/libman/
H A Dgfd.tex938 flexible, but is likely to be slower. Note that {\tt lib(branch_and_bound)} can
1016 a different choice of selection options, but likely to be less
1039 and likely to be less efficient than try_value/5.
1063 but try_value/2 is likely to be more efficient as it is specifically
1223 likely be less efficient than implementing the constraints directly in Gecode.
/barrelfish-master/doc/022-armv8/
H A Dreport.tex70 software support for likely future architectures, where large numbers of
92 counter as a general-purpose register. These most likely caused difficulty in
576 is likely to the same as with ARMv7 and x86, and we expect the existing
581 the ARMv8 is likely to result in a very different Local Message Passing (LMP)
975 obviously can't do so afterwards, as the thread likely has no idea that it's
/barrelfish-master/doc/000-overview/
H A DOverview.tex287 in size, though this restriction is likely to go away in the future.
709 requested, the following are likely to be present:

Completed in 249 milliseconds

12