The Experts below are selected from a list of 306 Experts worldwide ranked by ideXlab platform
Sungin Jung - One of the best experts on this subject based on the ideXlab platform.
-
design and implementation of a user level sockets layer over virtual interface architecture
Concurrency and Computation: Practice and Experience, 2003Co-Authors: Sungin Jung, Soonhoi HaAbstract:SUMMARY The Virtual Interface Architecture (VIA) is an industrystandard user-level communication architecture for system area networks. The VIA provides a protected, directly-accessible interface to a network hardware, removing the operating system from the critical communication path. In this paper, we design and implement a user-level Sockets layer over VIA, named SOVIA (Sockets Over VIA). Our objective is to use the SOVIA layer to accelerate the existing Sockets-based applications with a reasonable effort and to provide a portable and high-performance communication library based on VIA to application developers. SOVIA realizes comparable performance to native VIA, showing a minimum one-way latency of 10.5 µs and a peak bandwidth of 814 Mbps on Giganet’s cLAN. We have shown the functional compatibility with the existing Sockets API by porting File Transfer Protocol (FTP) and Remote Procedure Call (RPC) applications over the SOVIA layer. Compared to the Giganet’s LAN Emulation (LANE) driver which emulates TCP/IP inside the kernel, SOVIA easily doubles the file transfer bandwidth in FTP and reduces the latency of calling an empty Remote Procedure by 77% in RPC applications. Copyright c � 2003 John Wiley & Sons, Ltd.
-
sovia a user level sockets layer over virtual interface architecture
Foundations of Computer Science, 2001Co-Authors: Sungin JungAbstract:The Virtual Interface Architecture (VIA) is an industry standard user-level communication architecture for system area networks. The VIA provides a protected, directly-accessible interface to a network hardware, removing the operating system from the critical communication path. In this paper, we design and implement a user-level Sockets layer over VIA, named SOVIA (Sockets Over VIA). Our objective is to use the SOVIA layer to accelerate the existing Sockets-based applications with a reasonable effort and to provide a portable and high performance communication library based on VIA to the application developers.SOVIA realizes comparable performance to native VIA, showing the minimum latency of 10.5usec and the peak bandwidth of 814Mbps on Giganet's cLAN. We have verified the functional compatibility with the existing Sockets API by porting FTP (File Transfer Protocol) and RPC (Remote Procedure Call) applications over the SOVIA layer. Compared to the Giganet's LANE driver which emulates TCP/IP inside the kernel, SOVIA easily doubles the file transfer bandwidth in FTP and reduces the latency of calling an empty Remote Procedure by 77% in RPC applications.
E K Koh - One of the best experts on this subject based on the ideXlab platform.
-
A survey of asynchronous Remote Procedure calls
ACM SIGOPS Operating Systems Review, 1992Co-Authors: A L Ananda, B H Tay, E K KohAbstract:Remote Procedure Call (RPC) is a popular paradigm for interprocess communication in distributed systems. It is simple, flexible and powerful. However, most of the RPC systems today are synchronous in nature, and hence fail to exploit fully the parallelism inherent in distributed applications. In view of this, various asynchronous RPC systems have been designed and implemented to achieve higher parallelism while retaining the familiarity and simplicity of synchronous RPC. Asynchronous RPC calls do not block the caller (client) and the replies can be received as and when they are needed, thus allowing the client execution to proceed locally in parallel with the callee (server) invocation. Asynchronous RPC calls can be classified into two types depending on whether the calls return a value. Most asynchronous RPC systems only support calls that do not return a value, and few support both classes. In this paper, an analysis and comparison of various asynchronous RPC systems are presented.
-
astra an asynchronous Remote Procedure call facility
International Conference on Distributed Computing Systems, 1991Co-Authors: A L Ananda, B H Tay, E K KohAbstract:A transport-independent asynchronous RPC (Remote Procedure call) mechanism (ASTRA) that combines the advantages of both RPC and message-passing IPC (interprocess communication) has been designed and implemented. ASTRA calls do not block the caller (client) and the replies can be received as and when they are needed, thus allowing the client execution to proceed locally in parallel with the server invocation. All the calls are received and executed by the server in the order called by the client. ASTRA is unique among other asynchronous RPC systems in allowing its users to explicitly specify whether low-latency or high-throughput is required for a call, and in providing highly optimized lightweight intramachine calls. ASTRA is built within the framework of the SHILPA distributed computing environment. >
Robert Ross - One of the best experts on this subject based on the ideXlab platform.
-
mercury enabling Remote Procedure call for high performance computing
International Conference on Cluster Computing, 2013Co-Authors: Jerome Soumagne, Dries Kimpe, Judicael A Zounmevo, Mohamad Chaarawi, Quincey Koziol, Ahmad Afsahi, Robert RossAbstract:Remote Procedure call (RPC) is a technique that has been largely adopted by distributed services. This technique, now more and more used in the context of high-performance computing (HPC), allows the execution of routines to be delegated to Remote nodes, which can be set aside and dedicated to specific tasks. However, existing RPC frameworks assume a socket-based network interface (usually on top of TCP/IP), which is not appropriate for HPC systems, because this API does not typically map well to the native network transport used on those systems, resulting in lower network performance. In addition, existing RPC frameworks often do not support handling large data arguments, such as those found in read or write calls. We present in this paper an asynchronous RPC interface, called Mercury, specifically designed for use in HPC systems. The interface allows asynchronous transfer of parameters and execution requests and provides direct support of large data arguments. Mercury is generic in order to allow any function call to be shipped. Additionally, the network implementation is abstracted, allowing easy porting to future systems and efficient use of existing native transport mechanisms.
Satoshi Sekiguchi - One of the best experts on this subject based on the ideXlab platform.
-
ninf g a reference implementation of rpc based programming middleware for grid computing
Journal of Grid Computing, 2003Co-Authors: Yoshio Tanaka, Hidemoto Nakada, Satoshi Sekiguchi, Toyotaro Suzumura, Satoshi MatsuokaAbstract:GridRPC, which is an RPC mechanism tailored for the Grid, is an attractive programming model for Grid computing. This paper reports on the design and implementation of a GridRPC programming system called Ninf-G. Ninf-G is a reference implementation of the GridRPC API which has been proposed for standardization at the Global Grid Forum. In this paper, we describe the design, implementations and typical usage of Ninf-G. A preliminary performance evaluation in both WAN and LAN environments is also reported. Implemented on top of the Globus Toolkit, Ninf-G provides a simple and easy programming interface based on standard Grid protocols and the API for Grid Computing. The overhead of Remote Procedure calls in Ninf-G is acceptable in both WAN and LAN environments.
-
omnirpc a grid rpc facility for cluster and global computing in openmp
International Workshop on OpenMP, 2001Co-Authors: Mitsuhisa Sato, Motonari Hirano, Yoshio Tanaka, Satoshi SekiguchiAbstract:Omni Remote Procedure call facility, OmniRPC, is a thread-safe grid RPC facility for cluster and global computing environments. The Remote libraries are implemented as executable programs in each Remote computer, and OmniRPC automatically allocates Remote library calls dynamically on appropriate Remote computers to facilitate location transparency. We propose to use OpenMP as an easy-to-use and simple programming environment for the multi-threaded client of OmniRPC. We use the POSIX thread implementation of the Omni OpenMP compiler which allows multi-threaded execution of OpenMP programs by POSIX threads even in a single processor. Multiple outstanding requests of OmniRPC calls in OpenMP work-sharing construct are dispatched to different Remote computers to exploit network-wide parallelism.
-
omnirpc a grid rpc facility for cluster and global computing in openmp extended abstract
2001Co-Authors: Mitsuhisa Sato, Motonari Hirano, Yoshio Tanaka, Satoshi SekiguchiAbstract:Omni Remote Procedure call facility, OmniRPC, is a thread- safe grid RPC facility for cluster and global computing environments. The Remote libraries are implemented as executable programs in each Remote computer, and OmniRPC automatically allocates Remote library calls dynamically on appropriate Remote computers to facilitate location transparency. We propose to use OpenMP as an easy-to-use and simple programming environment for the multi-threaded client of OmniRPC. We use the POSIX thread implementation of the Omni OpenMP com- piler which allows multi-threaded execution of OpenMP programs by POSIX threads even in a single processor. Multiple outstanding requests of OmniRPC calls in OpenMP work-sharing construct are dispatched to dierent Remote computers to exploit network-wide parallelism.
Satoshi Matsuoka - One of the best experts on this subject based on the ideXlab platform.
-
ninf g a reference implementation of rpc based programming middleware for grid computing
Journal of Grid Computing, 2003Co-Authors: Yoshio Tanaka, Hidemoto Nakada, Satoshi Sekiguchi, Toyotaro Suzumura, Satoshi MatsuokaAbstract:GridRPC, which is an RPC mechanism tailored for the Grid, is an attractive programming model for Grid computing. This paper reports on the design and implementation of a GridRPC programming system called Ninf-G. Ninf-G is a reference implementation of the GridRPC API which has been proposed for standardization at the Global Grid Forum. In this paper, we describe the design, implementations and typical usage of Ninf-G. A preliminary performance evaluation in both WAN and LAN environments is also reported. Implemented on top of the Globus Toolkit, Ninf-G provides a simple and easy programming interface based on standard Grid protocols and the API for Grid Computing. The overhead of Remote Procedure calls in Ninf-G is acceptable in both WAN and LAN environments.
-
overview of gridrpc a Remote Procedure call api for grid computing
Grid Computing, 2002Co-Authors: Keith Seymour, Hidemoto Nakada, Satoshi Matsuoka, Jack Dongarra, Henri CasanovaAbstract:This paper discusses preliminary work on standardizing and implementing a Remote Procedure call (RPC) mechanism for grid computing. The GridRPC API is designed to address the lack of a standardized, portable, and simple programming interface. Our initial work on GridRPC shows that client access to existing grid computing systems such as NetSolve and Ninf can be unified via a common API, a task that has proven to be problematic in the past.
-
ninf a network based information library for global world wide computing infrastructure
IEEE International Conference on High Performance Computing Data and Analytics, 1997Co-Authors: Makoto Sato, Hidemoto Nakada, S. Sekiguchi, Satoshi Matsuoka, Umpei Nagashima, Hiromitsu TakagiAbstract:Ninf is an ongoing global network-wide computing infrastructure project which allows users to access computational resources including hardware, software and scientific data distributed across a wide area network. Ninf is intended not only to exploit high performance in network parallel computing, but also to provide high quality numerical computation services and accesses to scientific database published by other researchers. Computational resources are shared as Ninf Remote libraries executable at a Remote Ninf server. Users can build an application by calling the libraries with the Ninf Remote Procedure Call, which is designed to provide a programming interface similar to conventional function calls in existing languages, and is tailored for scientific computation. In order to facilitate location transparency and network-wide parallelism, Ninf metaserver maintains global resource information regarding computational server and databases, allocating and scheduling coarse-grained computation for global load balancing. Ninf also interfaces with the WWW browsers for easy accessibility.
