Lines Matching full:by
22 \ref uipdrivervars "variables used by device drivers"
73 controlled by the network device driver.
78 the network by the network device driver. If the destination is not on
80 another network by a router that is situated between the two
83 packets by the router. If possible, the size of the TCP segments are
89 specified in a number of RFC documents published by the Internet
124 should be invoked by the main control loop. The input handler function
167 uIP leaves the 32-bit additions to be implemented by the architecture
191 application. Because the data in the buffer will be overwritten by the
194 later processing. The packet buffer will not be overwritten by new
197 either by the network device or by the device driver. Most single-chip
200 handled by the processor, such as RS-232 ports, can copy incoming
259 of uIP is implemented as a C function that is called by uIP in
284 packet contents after they have been sent by the device driver, and
295 carried out by the application, it is the responsibility of the stack
312 When the application is called by uIP, the global variable uip_conn is
329 uip_datalen(). The data is not buffered by uIP, but will be
332 data, or by itself copy the incoming data into a buffer for later
337 When sending data, uIP adjusts the length of the data sent by the
339 TCP window advertised by the receiver. The amount of buffer space is
340 dictated by the memory configuration. It is therefore possible that
343 data that actually will be sent by the stack.
345 The application sends data by using the uIP function uip_send(). The
349 (pointed to by the uip_appdata pointer) can be used for this purpose.
358 Retransmissions are driven by the periodic TCP timer. Every time the
362 been sent by the device driver, uIP requires that the
375 the actual retransmission operation is carried out by the application,
383 The application closes the current connection by calling the
386 application might want to abort the connection and does so by calling
389 If the connection has been closed by the remote end, the test function
396 that the connection was aborted by the remote host, or that the
398 aborted. uIP reports this by calling the application function. The
406 uip_poll() to check if it is being polled by uIP.
412 has been produced. The application can only send data when invoked by
430 uIP by the function uip_connect(). This function
433 the next time the connection is polled by uIP. The uip_connect()
440 two element 16-bit array used by uIP to represent IP addresses.
446 and the current connection is aborted by uip_abort().
477 been established, the application replies to all data sent to it by
530 been acknowledged by the remote host, it might have been dropped in
542 remote host, it responds by sending an "ok" back.
670 this data to the device by using the function device_enqueue(). It is
673 be overwritten by the next incoming packet.
676 remote host by calling the uIP function uip_stop(). The application
738 The application is driven by incoming acknowledgments. When data has
789 have happened by checking if uip_aborted() or uip_timedout() are
795 by checking if uip_connected() is true. The connected() function is
804 data by sending out the message "Hello world!". To illustrate how to
886 called by the event handler function. The newdata() function will
889 " message with the connection. This message will later be sent out by
893 has been acknowleged by the receiving host. This acked() function
894 first reduces the amount of data that is left to send, by subtracting
905 data that is to be sent. It is called by the event handler function
913 after checking if data should be sent out or not as indicated by the
934 When incoming packets are processed by uIP, the IP layer is the first
977 which is used by the "ping" program.
981 constructed by simply swapping the source and destination IP addresses
993 The TCP implementation in uIP is driven by incoming packets and timer
994 events. Incoming packets are parsed by TCP and if the packet contains
996 invoked by the means of the application function call. If the incoming
1004 uIP, a listening connection is identified by the 16-bit port number
1007 and can be altered by the applications in the system.
1019 to be supported by a complex application layer. Instead, uIP allows
1024 the sliding window algorithm, it is not required by the TCP
1045 Retransmissions are driven by the periodic TCP timer. Every time the
1051 been sent by the device driver, uIP requires that the
1062 carried out by the application, it is the responsibility of the stack
1073 indicated by the receiver.
1077 bytes it is allowed to send by the receiving host. If the remote host
1095 notification mechanism, which can be used by an application to mark
1110 dominated by the checksum calculation loop, the operation of copying
1117 copied. Performance can be enhanced by combining the copy operation
1130 by the copying of packet data from the network device to host memory,
1135 implementations can be obtained by calculating the amount of CPU
1153 limited by the 500 ms idle time.
1167 severe. Small amounts of data sent by such a system will not span more
1168 than a single TCP segment, and would therefore not be affected by the
1171 The maximum throughput when uIP acts as a receiver is not affected by