The mirage NFS router

Scott Baker; John H. Hartman

doi:10.1109/LCN.2004.127

The mirage NFS router

Scott Baker, John H. Hartman

Computer Science

Research output: Contribution to conference › Paper › peer-review

Abstract

Mirage ¹ aggregates multiple NFS servers into a single, virtual NFS file server. It is interposed between the NFS clients and servers, making the clients believe that they are communicating with a single, large server. Mirage is an NFS router because it routes an NFS request from a client to the proper NFS server, and routes the reply back to the proper client. Experiments with a Mirage prototype show that Mirage effectively virtualizes an NFS server using unmodified clients and servers. Mirage imposes a negligible overhead on a realistic NFS workload. On real world workloads, such as a collection of clients executing compile jobs over NFS, Mirage imposes an overhead of 3% as compared to a proxy that simply forwards packets.

Original language	English (US)
Pages	242-249
Number of pages	8
DOIs	https://doi.org/10.1109/LCN.2004.127
State	Published - 2004
Event	Proceedings - 29th Annual IEEE International Conference on Local Computer Networks, LCN 2004 - Tampa, FL, United States Duration: Nov 16 2004 → Nov 18 2004

Other

Other	Proceedings - 29th Annual IEEE International Conference on Local Computer Networks, LCN 2004
Country/Territory	United States
City	Tampa, FL
Period	11/16/04 → 11/18/04

ASJC Scopus subject areas

General Engineering

Access to Document

10.1109/LCN.2004.127

Cite this

@conference{b12bc4a13ca040c2a96d53b75c45ee3d,

title = "The mirage NFS router",

abstract = "Mirage 1 aggregates multiple NFS servers into a single, virtual NFS file server. It is interposed between the NFS clients and servers, making the clients believe that they are communicating with a single, large server. Mirage is an NFS router because it routes an NFS request from a client to the proper NFS server, and routes the reply back to the proper client. Experiments with a Mirage prototype show that Mirage effectively virtualizes an NFS server using unmodified clients and servers. Mirage imposes a negligible overhead on a realistic NFS workload. On real world workloads, such as a collection of clients executing compile jobs over NFS, Mirage imposes an overhead of 3% as compared to a proxy that simply forwards packets.",

author = "Scott Baker and Hartman, {John H.}",

year = "2004",

doi = "10.1109/LCN.2004.127",

language = "English (US)",

pages = "242--249",

note = "Proceedings - 29th Annual IEEE International Conference on Local Computer Networks, LCN 2004 ; Conference date: 16-11-2004 Through 18-11-2004",

}

TY - CONF

T1 - The mirage NFS router

AU - Baker, Scott

AU - Hartman, John H.

PY - 2004

Y1 - 2004

N2 - Mirage 1 aggregates multiple NFS servers into a single, virtual NFS file server. It is interposed between the NFS clients and servers, making the clients believe that they are communicating with a single, large server. Mirage is an NFS router because it routes an NFS request from a client to the proper NFS server, and routes the reply back to the proper client. Experiments with a Mirage prototype show that Mirage effectively virtualizes an NFS server using unmodified clients and servers. Mirage imposes a negligible overhead on a realistic NFS workload. On real world workloads, such as a collection of clients executing compile jobs over NFS, Mirage imposes an overhead of 3% as compared to a proxy that simply forwards packets.

AB - Mirage 1 aggregates multiple NFS servers into a single, virtual NFS file server. It is interposed between the NFS clients and servers, making the clients believe that they are communicating with a single, large server. Mirage is an NFS router because it routes an NFS request from a client to the proper NFS server, and routes the reply back to the proper client. Experiments with a Mirage prototype show that Mirage effectively virtualizes an NFS server using unmodified clients and servers. Mirage imposes a negligible overhead on a realistic NFS workload. On real world workloads, such as a collection of clients executing compile jobs over NFS, Mirage imposes an overhead of 3% as compared to a proxy that simply forwards packets.

UR - http://www.scopus.com/inward/record.url?scp=20544477100&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=20544477100&partnerID=8YFLogxK

U2 - 10.1109/LCN.2004.127

DO - 10.1109/LCN.2004.127

M3 - Paper

AN - SCOPUS:20544477100

SP - 242

EP - 249

T2 - Proceedings - 29th Annual IEEE International Conference on Local Computer Networks, LCN 2004

Y2 - 16 November 2004 through 18 November 2004

ER -

The mirage NFS router

Abstract

Other

ASJC Scopus subject areas

Access to Document

Other files and links

Fingerprint

Cite this