Searched refs:sent (Results 1 - 25 of 49) sorted by relevance

12

/barrelfish-master/lib/libc/gen/
H A Dsendmmsg.c40 size_t i, sent; local
43 sent = 0;
44 for (i = 0; i < vlen; i++, sent++) {
47 if (sent != 0) {
49 * We have sent messages. Let caller
50 * know about the data sent, socket
54 return (sent);
59 /* Save sent bytes. */
63 return (sent);
/barrelfish-master/include/net_sockets/
H A Dnet_sockets.h13 net_sent_callback_t sent; member in struct:net_socket
36 // data must be allocated using net_alloc, it can be freed, when on_sent is called (i.e. actually sent)
/barrelfish-master/usr/eclipseclp/documents/embedding/
H A Dembremoteproto.tex69 interface. Messages (in EXDR format) are sent in both directions according
72 to {\eclipse} and return the results. The goal is sent in EXDR format.
86 control message is sent, the control is passed to the other side, and the
87 side that sent the message waits for a reply message from the other side.
93 issued, a message is sent via the control connection to the {\eclipse}
105 consumes the data that is sent from the other. This ensures that no
156 behaves correctly. The version information is sent from the remote side
181 be in blocking mode, and perform no translation on the data sent.
207 connection. This is sent in EXDR format, and is used to identify this
219 blocking mode, and perform no translation on the data sent
[all...]
H A Dembremote.tex71 embedded interface: {\eclipse} goals can be sent from the Tcl side to the
74 processes to allow streams of bytes to sent from one side to the other.
183 will be sent to the {\eclipse} side in EXDR format\footnote{See
192 sent from the Tcl to the {\eclipse} side.
248 Note also that by default, none of the information sent through the queues
266 interface. Information can be sent to {\eclipse} via bindings for (input)
296 displayed by a Tcl window. Streams of bytes can be sent along the queue
298 when the queue is flushed, the data is sent to the other side, which can
299 now read the data. The data can either be sent as normal strings (where
328 sent fro
[all...]
H A Dembvb.tex48 A stream of on which data can be sent to or from {\eclipse}.
204 The direction in which data is sent over this EclipseStream
/barrelfish-master/lib/lwip/src/netif/
H A Dethernetif.c113 * @return ERR_OK if the packet could be sent
114 * an err_t value if the packet couldn't be sent
140 signal that packet should be sent();
/barrelfish-master/include/lwip2/lwip/
H A Dtcp.h83 /** Function prototype for tcp sent callback functions. Called when sent data has
264 u32_t snd_nxt; /* next new seqno to be sent */
295 tcp_sent_fn sent; member in struct:tcp_pcb
311 /* idle time before KEEPALIVE is sent */
358 void tcp_sent (struct tcp_pcb *pcb, tcp_sent_fn sent);
/barrelfish-master/usr/drivers/lo/
H A Dlo_qdriver.c39 // Data-structure to map sent buffer slots back to application slots
108 // Tell the client we sent them!!!
258 * so that packet can be sent
287 /* Actual place where packet is sent. Adding trace_event here */
352 bool sent = false;
369 sent = handle_tx_done(pbuf_list_tx[ether_transmit_bufptr].opaque);
/barrelfish-master/doc/006-routing/
H A DRouting.tex118 The work has also shown that the order in which messages are sent also matters.
150 Interconnect drivers in Barrelfish generally provide a reliable messaging service: A message is delivered only once and each message sent is eventually delivered and its content is not corrupted. Furthermore, messages are delivered in FIFO order. The multi-hop interconnect driver is designed to provide a reliable messaging service in principle. However, contrary to the end-to-end argument, it does not provide any \emph{end-to-end} reliability, but builds on the reliability provided by the interconnect drivers of the underlying links. We accept that the multi-hop interconnect driver can fail in case any of the interconnect drivers of the underlying link fail.
161 Each monitor maintains a forwarding table. For each multi-hop channel, entries are created in the forwarding tables at all the nodes of that channel. Messages that are sent over the channel are forwarded at each node according to its forwarding table. Those entries in the forwarding tables can be seen as per-channel created \emph{hard} state: It is explicitly created at channel set-up and deleted at channel tear-down. Additionally to the entries in the forwarding table, per-channel created state includes bindings to the neighbouring nodes on the multi-hop channel.
177 Those additional channels are needed to ensure that the default monitor binding is not congested or even blocked by multi-hop messages. For example, suppose that a client's dispatcher receives a lot of multi-hop messages within a short period of time. The client reacts to this by allocating more memory. If multi-hop messages are sent over the default monitor binding, the message coming from the memory server will be blocked, therefore this will result in a dead lock. By creating new monitor bindings and not using the default monitor binding, we can prevent such a scenario.
182 Multi-hop messages carry a virtual circuit identifier (VCI). Virtual circuit identifiers allow nodes to identify the particular multi-hop channel a message belongs to. Each node on a multi-hop channel maintains a forwarding table, which maps VCIs to the next hop on that particular channel. A node forwards multi-hop messages based on this forwarding table. At channel end-points, a VCI allows to identify the binding belonging to the multi-hop channel the message was sent over. Virtual circuit identifiers are not only local to a specific link, but also to a direction on that link. Figure~\ref{fig:vci} shows an example assignment of VCIs.
188 This design requires that each node on a multi-hop channel tells its neighbours what virtual circuit identifier they should use for messages sent over that particular channel. This happens in the set-up phase of a multi-hop channel (see section~\ref{section: set-up}).
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.
225 As described in section~\ref{section:vcis}, it is necessary that each node on the multi-hop channel tells its neighbouring nodes what virtual circuit identifier they should use for messages sent over that particular channel. Therefore, each message contains the virtual circuit identifier of the sender. The two response-messages additionally contain the VCI of the receiver. This allows the receiver of a response-message to identify the multi-hop channel the message belongs to.
230 Once the multi-hop channel is set-up, messages can be sent in both directions. A message can be sent b
[all...]
/barrelfish-master/include/sys/
H A Dfile.h115 off_t *sent, int flags, struct thread *td);
378 struct uio *trl_uio, off_t offset, size_t nbytes, off_t *sent, int flags,
383 nbytes, sent, flags, td));
377 fo_sendfile(struct file *fp, int sockfd, struct uio *hdr_uio, struct uio *trl_uio, off_t offset, size_t nbytes, off_t *sent, int flags, struct thread *td) argument
/barrelfish-master/usr/eclipseclp/Opium/
H A Dpce_new.pl62 sent by PCE.
/barrelfish-master/include/lwip/lwip/
H A Dtcp.h71 err_t(*sent) (void *arg, struct tcp_pcb * tpcb, u16_t len));
340 u32_t snd_nxt; /* next new seqno to be sent */
369 err_t(*sent) (void *arg, struct tcp_pcb * pcb, u16_t space); member in struct:tcp_pcb
414 /* idle time before KEEPALIVE is sent */
480 if((pcb)->sent != NULL) \
481 (ret) = (pcb)->sent((pcb)->callback_arg,(pcb),(space)); \
/barrelfish-master/lib/lwip2/src/netif/
H A Dethernetif.c127 * @return ERR_OK if the packet could be sent
128 * an err_t value if the packet couldn't be sent
155 signal that packet should be sent();
/barrelfish-master/usr/net_socket_server/
H A Dnet_sockets_server.c68 genoffset_t sent, length; member in struct:send_frame
314 // socket->send_frames[0].offset, socket->send_frames[0].sent, socket->send_frames[0].length,
315 // socket->send_frames[1].offset, socket->send_frames[1].sent, socket->send_frames[1].length);
317 // socket->send_frames[0].offset, socket->send_frames[0].sent, socket->send_frames[0].length,
318 // socket->send_frames[1].offset, socket->send_frames[1].sent, socket->send_frames[1].length);
322 if (len < (socket->send_frames[0].length - socket->send_frames[0].sent)) {
323 socket->send_frames[0].sent += len;
326 len -= socket->send_frames[0].length - socket->send_frames[0].sent;
337 socket->send_frames[1].sent = 0;
591 // socket->send_frames[0].offset, socket->send_frames[0].sent, socke
[all...]
H A Dlib_netss.c68 genoffset_t sent, length; member in struct:send_frame
291 if (len < (socket->send_frames[0].length - socket->send_frames[0].sent)) {
292 socket->send_frames[0].sent += len;
295 len -= socket->send_frames[0].length - socket->send_frames[0].sent;
307 socket->send_frames[1].sent = 0;
633 while (socket->send_frames[0].length) { // invaldate all sent frames
644 socket->send_frames[1].sent = 0;
/barrelfish-master/usr/eclipseclp/documents/userman/
H A Dumssocket.tex40 where each packet sent by one process can be sent to different address.
140 It is based on packets sent from one process to another, perhaps across
172 the address where the packet should be sent
175 If the next packet is to be sent to a different address, a new
203 % be sent and the handler reads the message.
/barrelfish-master/lib/net_sockets/
H A Dnet_sockets.c351 socket->sent = cb;
433 // DEBUG_NETSOCK_to_log("%s(%d): dequeue sent %lx:%ld %p %p", __func__, socket->descriptor, offset, length, shb_data, socket->sent);
434 if (socket->sent) {
435 socket->sent(socket->user_state, socket, shb_data, nb->size);
/barrelfish-master/doc/011-idc/
H A DIDC.tex357 the typed messages defined in the interface definition to be sent and received
483 /* register an event for when a message is likely to be able to be sent */
568 A message may be sent on the binding by calling the appropriate transmit
585 transmission, and will eventually be sent if no asynchronous errors occur.
588 which will be executed after the given message has been successfully sent.
604 is buffered but not yet completely sent. The send continuation may be used to
950 is sent to the local monitor, containing the capability and an identifier
951 for the channel on which the capability is to be sent.
953 \item The monitor determines whether the cap may be sent to the remote core.
956 as LMP endpoints) may not be sent, no
[all...]
/barrelfish-master/include/lwip2/lwip/priv/
H A Dtcp_priv.h191 if((pcb)->sent != NULL) \
192 (ret) = (pcb)->sent((pcb)->callback_arg,(pcb),(space)); \
/barrelfish-master/doc/015-disk-driver-arch/
H A Dintro.tex16 Commands that can be sent to \ac{ata} devices are specified in the \ac{acs}
21 The way these commands are sent to the device is specified in the respective
H A Dxahcid.tex47 command is sent to determine the disk's parameters. A copy of the {\tt
/barrelfish-master/usr/eclipseclp/documents/libman/
H A Dmp.tex68 Messages are sent to {\em logical ports}.
136 Messages are general \eclipse terms and are sent to ports, normally
/barrelfish-master/lib/lwip/src/core/
H A Dtcp.c180 /* To ensure all data has been sent when tcp_close returns, we have
182 Since we don't really have to ensure all data has been sent when tcp_close
183 returns (unsent data is sent from tcp timer functions, also), we don't care
186 If SOF_LINGER is set, the data should be sent when tcp_close returns. */
198 * @param reset boolean to indicate whether a reset should be sent
391 * Returns how much extra window would be advertised if we sent an
438 * Otherwise wait for a packet to be sent in the normal course of
468 * ERR_OK if connect request has been sent
469 * other err_t values if connect request couldn't be sent
634 /* Check if KEEPALIVE should be sent */
[all...]
/barrelfish-master/tools/demo/Aquarium/
H A DWindow1.xaml.cs1124 //Dictionary<ulong, KeyValuePair<int, long>> sent = new Dictionary<ulong, KeyValuePair<int, long>>();
1126 Dictionary<ulong, ChannelAction> sent = new Dictionary<ulong, ChannelAction>();
1139 if (sent.TryGetValue(chan, out other))
1141 sent.Remove(chan);
1172 sent.Add(chan, ca);
1182 foreach (KeyValuePair<ulong, ChannelAction> kvp in sent)
/barrelfish-master/lib/lwip2/src/core/
H A Dtcp.c250 * For tcp_close(), a RST is sent if the application didn't receive all data
285 /* CLOSE_WAIT: deallocate the pcb since we already sent a RST for it */
365 /* To ensure all data has been sent when tcp_close returns, we have
367 Since we don't really have to ensure all data has been sent when tcp_close
368 returns (unsent data is sent from tcp timer functions, also), we don't care
462 * @param reset boolean to indicate whether a reset should be sent
750 * Returns how much extra window would be advertised if we sent an
816 * Otherwise wait for a packet to be sent in the normal course of
868 * ERR_OK if connect request has been sent
869 * other err_t values if connect request couldn't be sent
1732 tcp_sent(struct tcp_pcb *pcb, tcp_sent_fn sent) argument
[all...]

Completed in 300 milliseconds

12