/barrelfish-master/lib/barrelfish/arch/x86_32/ |
H A D | pmap.c | 332 * \param request The number of slabs the allocator must have 342 static errval_t refill_slabs(struct pmap_x86 *pmap, size_t request) argument 346 /* Keep looping till we have #request slabs */ 347 while (slab_freecount(&pmap->slab) < request) { 348 // Amount of bytes required for #request 349 size_t bytes = SLAB_STATIC_SIZE(request - slab_freecount(&pmap->slab),
|
/barrelfish-master/doc/006-routing/ |
H A D | Routing.tex | 163 In addition to the forwarding table, each node maintains a routing table. The routing table is used for channel set-up: If a node receives a channel set-up request, it determines where to forward the request with the help of its routing table. 209 \item A client dispatcher initiates the set-up process by calling the bind function of the multi-hop interconnect driver. This function forwards the bind request to the monitor running on the client dispatcher's core. The bind request includes various parameters, including the \emph{iref} of the service and the client's (ingoing) virtual circuit identifier. 211 \item The monitor running on the client dispatcher's core determines (from the iref) the core on which the service resides. It then forwards the bind request to another monitor, which is determined based on the routing table. 213 \item Monitors receiving the bind request check whether the service is running on the same core as they are. If so, they determine the local dispatcher which has exported this iref and forward the request to it. Otherwise, the bind request is forwarded to another monitor in the same way as in step two. 215 \item As soon as the service's dispatcher receives the bind request, it runs the user provided connection callback. Based on the return value of this callback, it either accepts the connection or rejects it. In any case, the bind reply is sent back to the monitor. 217 \item The monitor proxies the bind replay back to where it received the bind request fro [all...] |
/barrelfish-master/usr/eclipseclp/documents/mpslib/ |
H A D | outline.tex | 336 Clients send a request to the server port and expect a reply from the 339 of the request. This is illustrated in the examples to follow. 346 polling its request port for requests and the client is polling its 400 Figure~\ref{fig:server_interrupt} shows a template of a simple request 445 sends the clock value in a request to the echo server resident on another
|
H A D | eclipse.tex | 75 is performing a request on behalf of its engine and that at times when the
|
/barrelfish-master/lib/arranet/ |
H A D | arranet.c | 658 memcache_times[6][memcache_transactions[6]] = get_time() - mypayload->message.header.request.opaque; 662 memcache_times[6][memcache_transactions[6]] = get_time() - mypayload->message.header.request.opaque; 789 lwip_send_time[lwip_send_transactions] = get_time() - mypayload->message.header.request.opaque; 876 memcache_times[0][memcache_transactions[0]] = get_time() - mypayload->message.header.request.opaque; 887 memcache_times[1][memcache_transactions[1]] = get_time() - mypayload->message.header.request.opaque; 1089 posix_recv_time[posix_recv_transactions] = get_time() - mypayload->message.header.request.opaque; 1230 /* posix_recv_time[posix_recv_transactions] = get_time() - mypayload->message.header.request.opaque; */ 1284 /* posix_recv_time[posix_recv_transactions] = get_time() - mypayload->message.header.request.opaque; */ 1342 posix_send_time[posix_send_transactions] = get_time() - mypayload->message.header.request.opaque; 1680 posix_send_time[posix_send_transactions] = get_time() - mypayload->message.header.request [all...] |
/barrelfish-master/lib/barrelfish/arch/arm/ |
H A D | pmap.c | 665 * \param request The number of slabs the allocator must have 676 static errval_t refill_slabs(struct pmap_arm *pmap, size_t request) argument 680 /* Keep looping till we have #request slabs */ 681 while (slab_freecount(&pmap->slab) < request) { 682 // Amount of bytes required for #request 683 size_t bytes = SLAB_STATIC_SIZE(request - slab_freecount(&pmap->slab),
|
/barrelfish-master/doc/011-idc/ |
H A D | IDC.tex | 386 \item A \emph{server} dispatcher accepts an incoming binding request from a 427 object. If it returns success, the binding request will be accepted, and the 430 the client. When accepting a binding request, the connection callback also has 901 service resides, and forwards the request to the monitor on that core 905 has exported this iref, and forwards the bind request to it using a 1019 \texttt{lmp\_bind\_request} on the monitor. The monitor sends the request to the 1075 channel buffers, then sending a cap to the buffer along with a bind request 1085 a request to the monitor, the monitor serialises it and sends it to the
|
/barrelfish-master/usr/eclipseclp/icparc_solvers/ |
H A D | vbs_router.pl | 25 % Call e.g. r(2) to run sample request 2.
|
/barrelfish-master/lib/usb/ |
H A D | usb_request.c | 24 * \brief this request is used to clear or disable a specific feature. 31 * Behaviour of the device upon receiving a request: 36 * - configured state: valid request forall recipients 58 * \brief this request returns the current device configuration value 65 * Behaviour of the device upon receiving a request: 104 * \brief This request returns the specified descriptor if the descriptor exists. 111 * Behaviour of the device upon receiving a request: 112 * - default state: valid request 113 * - address state: valid request 114 * - configured state: valid request [all...] |
/barrelfish-master/lib/libc/rpc/ |
H A D | rpcb_clnt.c | 112 __rpc_control(int request, void *info) argument 114 switch (request) {
|
/barrelfish-master/usr/eclipseclp/Kernel/lib/ |
H A D | http_grammar.pl | 94 % request header fields
|
H A D | io.pl | 1566 handle_control(disconnect, Control, _NextMsg) :- -?-> !, % disconnect request
|
/barrelfish-master/usr/eclipseclp/documents/megalog/ |
H A D | multiuser-sec.tex | 150 This example takes a passenger's name (smith) and flight request 151 (ba100) and prints the flight details. If the request is confirmed
|
/barrelfish-master/lib/openssl-1.0.0d/crypto/ts/ |
H A D | ts.h | 529 TS_REQ *request; member in struct:TS_resp_ctx 703 * policy = policy from the request or NULL if absent (in this case 705 * md_alg = MD algorithm from request 706 * imprint, imprint_len = imprint from request 708 * nonce, nonce_len = nonce from the request or NULL if absent (in this case
|
/barrelfish-master/include/openssl/ |
H A D | ts.h | 529 TS_REQ *request; member in struct:TS_resp_ctx 703 * policy = policy from the request or NULL if absent (in this case 705 * md_alg = MD algorithm from request 706 * imprint, imprint_len = imprint from request 708 * nonce, nonce_len = nonce from the request or NULL if absent (in this case
|
/barrelfish-master/lib/devif/backends/net/mlx4/drivers/net/mlx4/ |
H A D | mlx4.h | 1019 uint64_t mlx4_make_profile(struct mlx4_priv *priv, struct mlx4_profile *request,
|
/barrelfish-master/doc/009-notifications/ |
H A D | Notify.tex | 172 whenever the FIFO goes non-empty, or at the request of the receiver 173 (e.g. if it wrote a special 'request IPI' value into the next empty
|
/barrelfish-master/usr/eclipseclp/documents/internal/project/ |
H A D | organisation.tex | 122 \item[eclipse-request] For requests about \eclipse\ licences.
|
/barrelfish-master/usr/eclipseclp/ecrc_solvers/grace/ |
H A D | grace.pl | 320 tcl_source(request),
|
/barrelfish-master/usr/eclipseclp/documents/embedding/ |
H A D | embremoteproto.tex | 1423 can request the socket connection at Host/Port address (if the request is 1426 request to be accepted. This will happen when {\tt remote_connect_accept/6} 1445 attachment request is made in the specified time, the predicate will
|
H A D | embremote.tex | 142 attached to the {\eclipse} program. The attach request is initiated on the 346 Tcl. In particular, it is not possible to request data from the other side 1441 {\eclipse} side produces output or request input.
|
/barrelfish-master/doc/019-device-drivers/ |
H A D | DeviceDriver.tex | 491 of memory, in our case device memory. It allows you to request a smaller range 505 you will find a call to the monitor to request the I/O capability:
|
/barrelfish-master/doc/026-device-queues/ |
H A D | devif.tex | 135 that is introduced to buffer stores and the local request are satisfied by the contents 620 uint64_t request,
|
/barrelfish-master/usr/drivers/solarflare/ |
H A D | sfn5122f_cdriver.c | 1543 static void cd_control(struct sfn5122f_devif_binding *b, uint64_t request, argument 1781 * Typically through a request from the device manager.
|
/barrelfish-master/doc/013-capability-mgmt/ |
H A D | type_system.tex | 905 processing a revoke request from another core.
|