Gaining efficiency in transport services by appropriate design and implementation choices

Abstract

End-to-end transport protocols continue to be an active area of research and development involving (1) design and implementation of special-purpose protocols, and (2) reexamination of the design and implementation of general-purpose protocols. This work is motivated by the perceived low bandwidth and high delay, CPU, memory, and other costs of many current general-purpose transport protocol designs and implementations.This paper examines transport protocol mechanisms and implementation issues and argues that general-purpose transport protocols can be effective in a wide range of distributed applications because (1) many of the mechanisms used in the special-purpose protocols can also be used in general-purpose protocol designs and implementations,(2) special-purpose designs have hidden costs, and (3) very special operating system environments, overall system loads, application response times, and interaction patterns are required before general-purpose protocols are the main system performance bottlenecks.

A Protocol To Improve The Data Communication Over Wireless Network

“…Several reliable transport protocols have been proposed in the literature for best-effort networks: Delta-t [4], NETBLT [5], VMTP [6], OSI/TP4 [7], XTP [8] and TCP [9]. In all these protocols, data items are identified by sequence numbers that are either byte-based or packet-based.…”

Efficient multicast design in a microkernel environment

“…If the basic microkernel services are not too restrictive semantically they can accommodate a wide range of control functions, group maintenance algorithms and ordering semantics. Performance compromises such as those observed by Watson and Mamrak [63] between application-level and transport-level abstractions can be avoided by using partial evaluation techniques [64] or protocol compilation techniques [65].…”

A Reduced Operation Protocol Engine (ROPE) for a multiple-layer bypass architecture

“…The heavy processing load is due to a combination of operating system overhead, protocol complexity, and per-octet processing on the data stream. To alleviate the end-system bottleneck one may consider new protocols [10], improved software implementation of existing protocols [5,35], parallel processing techniques [14,21,38], special protocol structures [15,30] and hardware assist [22] by offloading all or part of the protocol functions to an adaptor. This paper takes the latter approach.…”

“…0 Non-protocol-specific processing is a large part of the total load, as shown in [35]. Examples include interrupt handling, context switching and data copying at layer boundaries in deeply layered protocol stacks.…”