Skip to main content

Design and Implementation of an Improved Zero-Copy File Transfer Mechanism

  • Conference paper
Parallel and Distributed Computing: Applications and Technologies (PDCAT 2004)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 3320))

  • 804 Accesses

Abstract

This paper presents the design and implementation of an improved zero-copy file transfer mechanism that improves the efficiency of file transfers for Linux-based PC cluster systems. This mechanism, based on the Virtual Interface Architecture (VIA), presents a file transfer primitive that does not require the file system to be modified. This allows the NIC to transfer data from the kernel buffer to the remote node directly, without copying to a user buffer or page flipping. In addition, we apply the RDMA write technique to this mechanism to minimize the CPU utilization of the receive node. To do this, we have developed a hardware-based VIA network adapter for use as a NIC. We demonstrate the performance of the improved zero-copy file transfer mechanism experimentally, and compare results with those from existing file transfer mechanisms.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Similar content being viewed by others

References

  1. Stancevic, D.: Zero Copy I: User-Mode Perspective. Linux Journal 2003(105) (January 2003)

    Google Scholar 

  2. Tranter, J.: Exploring The Sendfile System Call. Linux Gazette (91) (June 2003)

    Google Scholar 

  3. Virtual Interface Architecture Specification, http://www.viarch.org/

  4. InfiniBandTM Architecture, http://www.infinibandta.org/

  5. DAFS Collaborative. Direct Access File System Protocol, Version 1.0 (September 2001), http://www.dafscollaborative.org

  6. Feforova, A., Seltzer, M., Magoutis, K., Addetia, S.: Application performance on the Direct Access File System. In: ACM SIGSOFT Sofrware Engineering Notes, Proc. of the 4th international workshop on Software and Performance, January 2004, vol. 29 (2004)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2004 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Park, S., Chung, SH., Choi, BS., Kim, SM. (2004). Design and Implementation of an Improved Zero-Copy File Transfer Mechanism. In: Liew, KM., Shen, H., See, S., Cai, W., Fan, P., Horiguchi, S. (eds) Parallel and Distributed Computing: Applications and Technologies. PDCAT 2004. Lecture Notes in Computer Science, vol 3320. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-30501-9_90

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-30501-9_90

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-24013-6

  • Online ISBN: 978-3-540-30501-9

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy