LIGHTWEIGHT INPUT/OUTPUT PROTOCOL

• US 20100161855A1
• Filed: 03/04/2010
• Published: 06/24/2010
• Est. Priority Date: 12/31/2003
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Voellm, Anthony F., Mohamed, Ahmed H.
• Application Number:
  US12/717,306
• Publication Number:
  US 20100161855A1
• Time in Patent Office: Days
• US Class Current: 710/56
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/10 Streamlined, light-weight or high-speed protocols, e.g. express transfer protocol [XTP] or byte stream
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12

Abstract

A method and system for offloading I/O processing from a first computer to a second computer, using RDMA-capable network interconnects, are disclosed. The method and system include a client on the first computer communicating over an RDMA connection to a server on the second computer by way of a lightweight input/output (LWIO) protocol. The protocol generally comprises a network discovery phase followed by an I/O processing phase. During the discovery phase, the client and server determine a minimal list of shared RDMA-capable providers. During the I/O processing phase, the client posts I/O requests for offloading to the second machine over a mutually-authenticated RDMA channel. The I/O model is asymmetric, with read operations being implemented using RDMA and write operations being implemented using normal sends. Read and write requests may be completed in polling mode and in interrupt mode. Buffers are managed by way of a credit mechanism.

Claims

1. A method for managing buffers in an input/output offload protocol, comprising:

sending, by a server to a client, a delta credit message including an information field set to a number of credits, wherein, if the number is a negative number −

N, the server requires the client to retire N credits;

if the number of credits is a negative number −

N, sending, by the client to the server, N credit messages, and otherwise sending, by the client to the server, one credit message; and

for each credit message sent by the client, sending, by the server to the client, a status response message.