Searched refs:remote (Results 1 - 25 of 43) sorted by relevance

12

/barrelfish-master/usr/eclipseclp/documents/embedding/
H A Dembremoteproto.tex33 The {\eclipse} remote interface protocol is used to build a remote
36 separate {\eclipse} process via the remote interface. The Tcl remote
38 interface. This chapter describes the protocol, so that remote interfaces
45 peers\/} is used to unify the remote and embedding interfaces.
47 Another feature of the remote interface is that on the {\eclipse} side,
50 interface (e.g.\ for a GUI) and change the remote code without needing to
53 Briefly, a socket connection is established between the remote program and
56 communication to be platform independent, and the {\eclipse} and remote
[all...]
H A Dembremote.tex34 This chapter describes the remote Tcl interface, which allows a separate
53 \item More than one Tcl (or other remote) process can be attached to a
54 single {\eclipse} via the remote interface.
55 \item For the programmer, the embedding and remote interfaces are largely
56 similar, and once the connection is established in the remote interface,
60 The remote interface thus offers more flexibility than an embedding
72 {\eclipse} side via the remote predicate call ({\bf ec_rpc}) mechanism,
80 application to be usable through both the Tcl remote and embedding
83 application (the attach and detach operations in the case of the remote
91 an embedded {\eclipse}, or the {\eclipse} process and other attached remote
[all...]
H A Dembtcl.tex42 An alternative method of using {\eclipse} with Tcl is to use the Tcl remote
45 remote and embedding interfaces are largely compatible, so that it is
49 more efficient. The advantage of the remote interface is that the Tcl and
56 but the development tools can be used with both the embedding and remote
209 and is provided for compatibility with the Tcl remote interface
242 side. However, it is needed in the remote case, and for compatibility and
299 This is provided mainly for compatibility with the Tcl remote
303 remote interface. Instead, asynchronous queues are needed (see
306 Note that it is possible to use the asynchronous queues of the remote
437 This is provided for compatibility with the Tcl remote
[all...]
H A Dembtclmulti.tex37 interface is of the embedded or remote variants.
51 ({\bf eclipse}) or remote ({\bf remote_eclipse}) variant of the Tcl peer
64 (i.e. it has already been set up using ec_init (embedded) or ec_remote_init (remote)).
227 The Tcl program uses the remote Tcl peer interface to create a window that
230 different remote peer. Each window has three buttons:
/barrelfish-master/usr/tests/spantest/
H A Dxcorejoin.c22 static int remote(void *dummy) function
64 err = domain_thread_create_on(i, remote, (void*)(uintptr_t)i, &threads[i]);
H A Dspantest.c226 static int remote(void *dummy) function
231 printf("remote running on %d after %"PRIu64"\n", core, time-times[0]);
372 err = domain_thread_create_on(i, remote, NULL, NULL);
/barrelfish-master/usr/eclipseclp/Kernel/lib/
H A Dremote_tools.pl25 % ECLiPSe II remote development tools ECLiPSe side interface
88 (writeln(log_output, "Disconnected from remote tools"),
122 "This library allows the Tk development tools to be used via the remote Tcl
149 summary: "Initiate the attachment of remote development tools",
151 <P>Initiate the attachment of the remote development tools. This will create
152 a connection waiting for the remote development tools to be attached to.
154 the development tools. The remote development tools should be started
164 summary: "A flexible attachment of remote development tools",
166 args: ["Address": "Address for the remote connection (Host/Port or variable)",
172 <P>Initiate the attachment of the remote developmen
[all...]
H A Dio.pl949 % PeerType: either remote or embed.
953 % remote(PeerHost,LocalHost,TimeOut)
960 % What is used has implications for what the remote side can
963 % 1) actual ECLiPSe side hostname: remote side must also
965 % 2) localhost: remote side must used localhost for the
968 % 3) not instantiated: remote side can use either
986 % PeerType: peer type for the queue: Either embed or remote
989 % sync(SocketName): synchronous remote queue, with socket
990 % async : asynchronous remote queue
994 % The above information is used to clean up a remote sid
[all...]
H A Dtoplevel.pl161 embedded or remote-interfaced to a GUI-based host program.
467 % remote-eclipse was created with the UseQueues option)
486 % remote:
487 % remote sends exdr 'int' on async gui_pause_request
492 % remote optionally sends 'abort' on async gui_pause_request
495 ( peer_get_property(host, type, remote) ->
/barrelfish-master/include/xomp/
H A Dxomp_master.h91 * \param remote pointer where to store the remote path
95 errval_t xomp_master_build_path(char **local, char **remote);
H A Dxomp.h18 /// size of the messaging channel between master and remote workers
48 /// core on which to spawn remote workers
71 XOMP_WORKER_LOC_MIXED, ///< spawn remote and local
72 XOMP_WORKER_LOC_REMOTE, ///< spawn remote only
120 /** uniform master arguments for local and remote workers */
129 /** distinct master arguments for local and remote workers separatly */
135 struct xomp_spawn remote; ///< arguments for hte remote workers member in struct:xomp_args::__anon401::__anon404
/barrelfish-master/include/barrelfish/
H A Dmonitor_client.h51 errval_t monitor_cap_set_remote(struct capref cap, bool remote);
/barrelfish-master/tools/
H A Ddebug.sh42 target remote localhost:$PORT
H A Dqemu-wrapper.sh295 target remote localhost:$PORT
/barrelfish-master/lib/bomp/backends/
H A Dxomp_master.c55 XOMP_WORKER_TYPE_REMOTE = 2 ///< worker runs remote to master
99 uint32_t num; ///< number of remote workers
100 struct xomp_worker *workers; ///< array of remote workers
101 uint32_t next; ///< next remote worker to "allocate"
102 } remote; member in struct:xomp_master
139 /// only use remote workers, no locals
148 /// arguments to supply to the remote spawned workers
305 debug_printf("remote worker %016lx: add memory took %lu cycles, %lu ms\n",
550 spawn_args_remote.path = args->args.distinct.remote.path;
571 /* remote initializatio
1063 xomp_master_build_path(char **local, char **remote) argument
[all...]
/barrelfish-master/usr/eclipseclp/JavaInterface/
H A Djoop_boot.pl41 % waits for resume signal from remote side
48 session(Control); % yield to the remote peer for a session
52 % yield to the remote peer until final resume is called, then disconnect.
/barrelfish-master/usr/eclipseclp/documents/userman/
H A Dumstkeclipse.tex66 Unless it is attached to the remote
276 from the {\eclipse} session, and are attached to it via the Tcl/Tk remote
295 remote tools active)}
299 Once attached to an {\eclipse} session, the remote development tools have
309 to each other via the remote Tcl/Tk interface. The interactions of the two
315 can only interact with the remote tools window when execution in the
316 {\eclipse} session is suspended. The toplevel window of the remote tools
319 the remote tools to {\eclipse}. This can either be
322 to {\eclipse} via the ``Resume ECLiPSe'' button on the remote tools window.
327 To use the remote tool
[all...]
/barrelfish-master/usr/bench/xomp_bench/
H A Dspawn_bench.c107 .remote = remote_info
H A Dwork_bench.c117 .remote = remote_info
/barrelfish-master/lib/libc/rpc/
H A Drpcb_clnt.c106 * This routine adjusts the timeout used for calls to the remote rpcbind.
637 "\tCouldn't resolve remote address!\n");
688 * returns the client handle that it uses to contact the remote rpcbind.
737 struct netbuf remote; local
788 CLNT_CONTROL(client, CLGET_SVC_ADDR, (char *)&remote);
792 malloc(remote.len)) == NULL)) {
799 memcpy(address->buf, remote.buf, remote.len);
802 address->len = address->maxlen = remote.len;
824 * We also send the remote syste
[all...]
/barrelfish-master/usr/eclipseclp/lib_tcl/
H A Dtkeclipse.tcl1132 if {[ec_interface_type] == "remote"} {
1178 if {[ec_interface_type] == "remote"} {
1264 if {[ec_interface_type] == "remote"} {
/barrelfish-master/usr/eclipseclp/documents/libman/
H A Dmp.tex71 synchronous facilities (e.g. remote procedure call style) can be built on top.
137 remote ports.
139 \item [msg\_send(+PortId, +Message)] Send a message to a (remote) port.
/barrelfish-master/lib/barrelfish/
H A Dmonitor_client.c314 errval_t monitor_cap_set_remote(struct capref cap, bool remote) argument
322 err = mc->rpc_tx_vtbl.cap_set_remote(mc, cap, remote, &reterr);
501 // debug_printf("Got remote monitor cap\n");
/barrelfish-master/lib/lwip2/src/netif/ppp/
H A Dipcp.c87 /* Hook for a plugin to choose the remote IP address */
179 { "ipcp-accept-remote", o_bool, &ipcp_wantoptions[0].accept_remote,
249 "set local and remote IP addresses",
450 u32_t local, remote; local
485 * If colon last character, then no remote addr.
488 if ((remote = inet_addr(colon)) == (u32_t) -1) {
493 remote = *(u32_t *)hp->h_addr;
497 if (bad_ip_adrs(remote)) {
498 option_error("bad remote IP address %s", ip_ntoa(remote));
[all...]
/barrelfish-master/include/lwip2/netif/ppp/
H A Dipcp.c87 /* Hook for a plugin to choose the remote IP address */
179 { "ipcp-accept-remote", o_bool, &ipcp_wantoptions[0].accept_remote,
249 "set local and remote IP addresses",
450 u32_t local, remote; local
485 * If colon last character, then no remote addr.
488 if ((remote = inet_addr(colon)) == (u32_t) -1) {
493 remote = *(u32_t *)hp->h_addr;
497 if (bad_ip_adrs(remote)) {
498 option_error("bad remote IP address %s", ip_ntoa(remote));
[all...]

Completed in 127 milliseconds

12