WO2005067430A2 - Lightweight input/output protocol - Google Patents
Lightweight input/output protocol Download PDFInfo
- Publication number
- WO2005067430A2 WO2005067430A2 PCT/US2004/024026 US2004024026W WO2005067430A2 WO 2005067430 A2 WO2005067430 A2 WO 2005067430A2 US 2004024026 W US2004024026 W US 2004024026W WO 2005067430 A2 WO2005067430 A2 WO 2005067430A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- server
- client
- computer
- request
- lwio
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
- G06F13/28—Handling requests for interconnection or transfer for access to input/output bus using burst mode transfer, e.g. direct memory access DMA, cycle steal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network 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]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/10—Streamlined, light-weight or high-speed protocols, e.g. express transfer protocol [XTP] or byte stream
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
Definitions
- the present invention relates generally to systems and methods of remote file access, and more particularly to techniques for offloading input/output processing using Remote Direct Memory Access (RDMA).
- RDMA Remote Direct Memory Access
- a system for offloading an I/O task from a first computer to a second computer includes a client running on the first computer and a server running on the second computer.
- the system further includes one or more RDMA channels linking the first computer and the second computer.
- the client and server communicate in accordance with an LWIO protocol comprising a network discovery phase and an I/O processing phase.
- the LWIO protocol is used in association with another network protocol, such as SMB/C1FS, leveraging the security and authentication infrastructure of the second protocol, h order to provide a better security model, the I/O model in the protocol is asymmetric: reads are implemented using RDMA, while writes are implemented using send operations.
- a method for offloading an I/O task from a first computer to a second computer is provided.
- the method takes advantage of common RDMA-capable communication devices on the two computers and is associated with a lightweight input/output (LWIO) client-server protocol.
- the protocol generally comprises a 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.
- the client initially obtains a server request resume key from the server.
- the client then opens a pipe to the server, over which the client sends a negotiate request containing a list of RDMA-capable providers on the first machine.
- the server sends a negotiate response over the pipe containing a list of available providers on the second machine that match providers on the first machine.
- the client then creates an RDMA connection to the server over a shared provider.
- the client and the server mutually authenticate the new connection.
- the client then registers one or more files for use with the server.
- I/O processing request messages include a close message, a cancel message, a read message, a write message, a vectored read message, and a vectored write message.
- the protocol features an asymmetric I/O model for security reasons.
- Read data is sent to the client using RDMA write operations, while writes are completed using ordinary sends.
- Read and write requests can be specified by the client to be completed by the server in polling mode or in interrupt mode. If the client indicates that the completion should not be in polling mode, the server completes the I/O processing request by sending a status block to the first computer by way of RDMA transfer.
- FIG. 4B is a diagram generally illustrating a representation of an exemplary server negotiate response in accordance with an embodiment of the invention
- FIG. 5 is a flow diagram generally illustrating additional steps taken in the discovery phase of the LWIO protocol in accordance with an embodiment of the invention
- FIG. 6 A is a diagram generally illustrating a representation of an exemplary client authenticate request message in accordance with an embodiment of the invention
- FIG. 6B is a diagram generally illustrating a representation of an exemplary server authenticate response in accordance with an embodiment of the invention
- FIG. 6C is a diagram generally illustrating a representation of an exemplary server status response completing authentication in accordance with an embodiment of the invention
- FIG. 7 A is a diagram generally illustrating a representation of an exemplary client register file message in accordance with an embodiment of the invention.
- FIG. 7B is a diagram generally illustrating a representation of an exemplary server status response completing file registration in accordance with an embodiment of the invention;
- FIG. 8 is a flow diagram generally illustrating steps taken with respect to completion of an I/O request in polling mode and in non-polling mode, in accordance with an embodiment of the invention
- FIG. 9A is a diagram generally illustrating a representation of an exemplary client interrupt request message in accordance with an embodiment of the invention.
- FIG. 10 is a flow diagram generally illustrating steps taken with respect to a server-client credit transaction in accordance with an embodiment of the invention.
- FIG. 1 IB is a diagram generally illustrating a representation of an exemplary client-to-server credit message in accordance with an embodiment of the invention
- FIG. 11 C is a diagram generally illustrating a representation of an exemplary server status response completing a client-server credit transaction in accordance with an embodiment of the invention
- FIG. 12A is a diagram generally illustrating a representation of an exemplary client close request message in accordance with an embodiment of the invention.
- FIG. 14B is a diagram generally illustrating a representation of an exemplary server status response completing a read request in the non-polling mode case, in accordance with an embodiment of the invention.
- FIG. 14C is a diagram generally illustrating a representation of an exemplary- client read request message in the polling mode case, in accordance with an embodiment of the invention;
- FIG. 14D is a diagram generally illustrating a representation of an exemplary server I/O status block completing a read request in the polling mode case, in accordance with an embodiment of the invention.
- FIG. 15 A is a diagram generally illustrating a representation of an exemplary client write request message in the non-polling mode case, in accordance with an embodiment of the invention.
- FIG. 15C is a diagram generally illustrating a representation of an exemplary client write request message in the polling mode case, in accordance with an embodiment of the invention.
- FIG. 16B is a diagram generally illustrating a representation of an exemplary server status response completing a vectored read request in the non-polling mode case, in accordance with an embodiment of the invention
- FIG. 16D is a diagram generally illustrating a representation of an exemplary server I/O status block completing a vectored read request in the polling mode case, in accordance with an embodiment of the invention
- FIG. 17A is a diagram generally illustrating a representation of an exemplary client vectored write request message in the non-polling mode, non-collapsed case, in accordance with an embodiment of the invention
- FIG. 17D is a diagram generally illustrating a representation of an exemplary server status response completing a vectored write request in the non-polling mode case, in accordance with an embodiment of the invention.
- FIG. 17E is a diagram generally illustrating a representation of an exemplary server I/O status block completing a vectored write request in the polling mode case, in accordance with an embodiment of the invention.
- FIG. 1 is a schematic diagram generally illustrating certain features of a representative networked client/server environment within which aspects of the present invention may be incorporated. Depicted in FIG. 1 are two computer machines, labeled Host A 101 and Host B 121. While the invention may be practiced in an environment involving computers of many different types and uses, in one representative scenario Host A 101 functions as an application server machine charged with I/O-intensive work, such as a database server.
- Each of Host A 101 and Host B 121 include a number of network interface cards (NICs) 109, 111, 113, 133, 135, 137 allowing for networked data communication from one machine to the other.
- NICs network interface cards
- NICs 109, 111, 135, 137 permitting RDMA data transfer.
- a non-RDMA network link 119 and an RDMA channel 117 are present between the two hosts 101, 121.
- FIG. 2 illustrates steps taken in the discovery phase of the LWIO protocol in an embodiment of the invention.
- the LWIO server registers with the SMB/CIFS server running on that host machine.
- the SMB/CIFS server notifies a SMB/CIFS client running on a remote host that the LWIO server is available.
- the LWIO client requests a server request resume key.
- the resume key is an authentication mechanism that has been disclosed in another application having the same assignee as the present application, "Method and System for Accessing a File (Resume Key)," U.S. Patent Application Serial No. , filed on October 24, 2003, which is hereby incorporated herein in its entirety by reference.
- the LWIO server passes the server request resume key back to the client, hi an embodiment of the invention the server request resume key has the following structure:
- FIG. 3 provides an illustrative representation of the server request resume key 219.
- ResumeKey 221, Timestamp 223, and Pid 225 are generated on the server and are opaque to the client.
- Context 229 is an array containing a UNC name that is used by the LWIO client to contact the server.
- ContextLength 227 is the number of bytes in Context 229.
- the client application When the client application receives the server request resume key 219, it retrieves the server UNC name from the Context field 229. Returning to FIG. 2, at step 209 the client opens a pipe to the LWIO server.
- the pipe is used for automatic discovery of RDMA-capable devices that are available in the network, in a manner described further below. This is an important and useful feature of the present invention; address resolution mechanisms like ARP are generally absent from NLA networks and similar networks.
- the client next queries the server for a list of its RDMA-capable devices ("providers") that are available for use with the LWIO protocol. The querying is accomplished by way of a negotiate request, which the client constructs and sends to the server over the newly-opened pipe at step 211.
- the negotiate request has the following structure:
- GUID UUID
- typedef struct ⁇ CHAR Name [L IO_MAX_PROVIDER_NAME] ;
- FIG. 4A provides an illustrative representation of the negotiate request packet 231 in an embodiment of the invention.
- the negotiate request includes a control header 233, a fixed-length Unicode client name field 235, a client UUID 237 used as a key, a local buffer size 239 for receiving a response, and the list of providers 241.
- the Protocolld 'LWIO' 243 is stored as the first four bytes of the header.
- Revld 245 holds a currently defined value 0x1001, LWIO_REV_ID.
- Opcode 247 holds a currently defined value Oxfe, LWIO_CONTROL_OPCODE_NEGOTIATE.
- Length 249 is the size in bytes of the complete packet to be sent to the server, including all opcode-specific data.
- ClientName 235 is used by the server to identify the client.
- Key 237 is used in a subsequent network-specific authentication procedure, as described below.
- ResponseLength 239 is the size of the buffer for receiving a negotiate response from the server, as described below.
- ProviderCount 251 is the number of providers associated with the client machine and about which the client is informing the server.
- the provider list 241 contains the list of ProviderCount providers.
- Name 253 is the name of the provider. In order for compatible networks to be detected, the client and the server should preferably use the same name for the same provider.
- LnstanceCount 255 is the number of devices of a particular provider type.
- the instance table 257 is a table of network/discriminator pairs, in which a pair serves to describe, in a device-specific way, how to form a remote connection.
- HostAddressLen 259 is the length of the network-specific host address 263.
- DiscriminatorLen 261 is the length of the network-specific discriminator 265. Following these length fields are the HostAddressLen bytes of the host address 263 and the DiscriminatorLen bytes of the discriminator 265.
- the server determines which RDMA-capable communication devices it has in common with the client.
- the server sends a negotiate response to the client over the pipe, including a list of shared providers.
- the negotiate response has the following structure:
- FIG. 4B provides an illustrative representation of the negotiate response 267 in an embodiment of the invention.
- the control header 269 is as in the negotiate request, except that Length 271 now reflects the size of the response message 267.
- SrvName 273 holds the name of the server.
- Key 275 is a server- generated GUID for use by the client. As explained further below, the client sends the Key back to the server in an authenticate request over a new connection using one of the common communication devices.
- ProviderCount 277 is the number of providers in the provider list 279.
- the provider list 279 contains a list of providers common to the server and the client. There is no guarantee that the client can actually connect to these providers.
- the server and the client have shared communication device information, and the minimal list of common providers has been determined.
- the client creates one or more RDMA connections to the LWIO server over one or more of the shared devices.
- the following opcodes are defined for client-to-server communication: #define LWIO_ OPCODE_READ 0x0
- the corresponding client-to-server messages in the LWIO protocol feature a common header structure.
- the common header has the following format in an embodiment of the invention:
- FIG. 5 illustrates steps taken by the client and the server in an embodiment of the invention, during the remainder of the initial phase of the LWIO protocol.
- the client establishes a connection to the server over a shared communication device, as explained above.
- the client and the server now mutually authenticate the new connection.
- the client sends an authentication request message (LWIO_OPCODE_AUTH) to the server. Authentication is done in order to prevent server-side and client-side spoofing. If the authentication is not timely completed, the connection is terminated.
- FIG. 6A provides an illustrative representation of the client authenticate request message in an embodiment of the invention.
- the authenticate message 617 comprises the common header 619 followed by an LWIO_AUTHJP ARAMS structure 621.
- Length 623 is set to the number of bytes sent to the server (the size of the common header 619 plus the size of the LWIO_AUTH_PARAMS 621).
- Opcode 625 is set to LWIO_OPCODE_AUTH (0x6).
- Flags 627 is set to LWIO_HDR_FLAG_INTERRUPT.
- Cookie 629 in this and the other client protocol messages, is set to a value chosen by the client and is sent back in the server reply. The Cookie value is typically used to match a request with a server reply.
- DataVa 631 is set to the address to which the server should RDMA the server authentication parameters.
- DataMh 633 holds the RDMA memory handle associated with DataVa 631.
- an LWIO_AUTH_PARAMS 621 forms the second part of the packet.
- Magic 635 is set to 'LWIO'.
- Revld 637 is set to LWIO_REV_ID.
- Endian 639 is set to sizeof(ULONG_PTR).
- PageSize 641 is set to the CPU page size (4k on 32-bit machines and 8k on 64-bit machines).
- BaseSequence 643 is set to 0.
- MaxRdmaWindowSize 645 is intended to be set to the maximum number of bytes that the client can accept in an RDMA transfer; in the depicted embodiment it is set to 64k.
- MaxSendBufferSize 647 is intended to be set to the number of bytes that the client can send to the server in a single request; in the depicted embodiment it is set to Ik.
- MaxRecvBufferSize 649 is intended to be set to the number of bytes that the client has posted to receive data from the server; in the depicted embodiment it is set to 16 bytes.
- HeaderSize 651 is set to the number of bytes in the LWIO control header 619.
- Credits 652 is set to the initial number of buffer credits that the client wishes to have. The use of credits is explained further below.
- the server may or may not satisfy the client's request.
- RdmaReadSupported 653 is set to 0 if the client does not support RDMA read operations and is set to 1 if the client does support RDMA read.
- Revld 663 is set to LWIO_REV_ID.
- Endian 665 is set to sizeof(ULONG_PTR).
- PageSize 667 is set to the CPU page size.
- BaseSequence 669 is intended to be set to (client BaseSequence + 1).
- MaxRdmaWindowSize 671 is intended to be set to the maximum number of bytes that the client can accept in an RDMA transfer; in the depicted embodiment it is set to 512k.
- MaxSendBufferSize 673 is intended to be set to the number of bytes that the server sends to the client in a single response; in the depicted embodiment it is set to 16 bytes.
- MaxRecvBufferSize 675 is intended to be set to the number of bytes that the server has pre-posted to receive data from the client; in the depicted embodiment it is set to 8k. HeaderSize 677 is set to the number of bytes in the common header. Credits 679 is set to the initial number of credits that the server has available for the client. RdmaReadSupported 681 is set to 0 if the server does not support RDMA read and is set to 1 if the server does support RDMA read.
- the server sends the following options: Key (LWIO_AUTH_OPTION_KEY) 683, Sessionld (LWIO_AUTH_OPTION_SESSION_ID) 685, and a Signature (LWIO_AUTH_OPTION_SIGNATURE) 687.
- Key 683 is set to the Key that the client had sent previously in the Negotiate Request.
- the Sessionld 685 value is used by the client in registering client files with the server, as explained below.
- Signature 687 is an MD5 signing of the LWIO_AUTH_P ARAMS excluding the Signature.
- the LWIOJVISG_STATUS_RESPONSE structure has the following format:
- LWIO_IO_STATUS_BLOCK Ios ⁇ LWIO_MSG_STATUS_RESPONSE, *LPLWIO_MSG_STATUS_RESPONSE;
- FIG. 6C provides an illustrative representation of the LWIO_MSG_STATUS_RESPONSE 689 returned by the server to complete the authentication in an embodiment of the invention.
- Cookie 691 is set to the cookie value set by the client in the header of the authenticate message.
- Information 693 is set to the number of bytes of LWIO_AUTH_P ARAMS plus eight bytes.
- Status 695 is set to 0x0 (signifying success) or 0xC0000022 (signifying "access denied").
- step 609 when the new connection has been mutually authenticated by the client and the server, the client begins registering files for use with the server. File operations for a file are not processed over a link until the client has registered the file for use with the server.
- FIG. 7 A provides an illustrative representation of the register file message sent by the client to the server in an embodiment of the invention.
- the registration message 701 comprises the common header 703 followed by an LWIO JFIDJP ARAMS structure 705.
- Length 707 is set to the number of bytes sent to the server (the size of the header 703 plus the size of the LWIO_FID_PARAMS 705).
- Opcode 709 is set to LWIO_OPCODE_REGISTER (0x7).
- Flags 711 is set to
- LWIO_HDR_FLAG_INTERRUPT In this client message and subsequent client messages, Credits 713 is set to the number of pending I/O requests on the client.
- the Credits field serves as a hint to the server to allocate more credits to the connection, thus allowing additional outstanding I/O requests, as explained further below.
- the number of outstanding client requests at any one time cannot exceed the "Credits" value.
- Cookie 715 is set to a client-specified value.
- the LWIO_FID_P ARAMS structure has the following format:
- ResumeKey 717 is set to the server request resume key that was returned over the initial file access channel.
- Sessionld 719 is set to the Sessionld that was returned by the server during the connection authentication stage.
- FlagsAndAttributes 721 is set to the Win32 Create Flags used initially to open the file.
- FIG. 7B provides an illustrative representation of the LWIO_MSG_STATUS__RESPONSE 723 sent by the server in an embodiment of the invention.
- Information 725 is set to the Fid (File ID) to be used when sending I/O requests.
- Status 727 is set to 0x0 (success) or another NTSTATUS code on failure.
- Cookie 729 is set to the cookie value that the client set in the header of the register file message.
- I/O Processing phase of the LWIO protocol begins.
- One key feature of embodiments of the LWIO protocol is an asymmetric I/O model for reads and writes. Read operations are implemented using RDMA, while writes are implemented using send operations. Writes are not implemented using RDMA in order to provide a better security model. If the server exposes its address space over the NIC for RDMA it introduces a data corruption vulnerability that can be exploited by a malicious client. In this scenario, the malicious client issues, in a loop, RDMA write operations on a given server virtual address.
- the malicious client eventually catches the server using the same virtual address for a different connection, causing the data to be written into a server buffer that might be associated with a different client.
- the asymmetric I/O model in the LWIO protocol guards against this possibility. This feature is a principal difference between the LWIO protocol and other RDMA-based file transfer protocols, such as DAFS.
- DAFS RDMA-based file transfer protocols
- the flow diagram of FIG. 8 generally illustrates, from the general perspective of the LWIO server, steps taken in an embodiment of the invention with respect to completing an I/O request in polling mode or non-polling mode.
- a client I/O request specifies whether the server should send back a post-send (interrupting the CPU) or an RDMA message.
- the server determines whether an LWIO_HDR__FLAG_INTERRUPT flag is set in the common header of the client I/O request message. If this flag is set, at step 803 the server completes the client request by way of an LWIO_MSG_STATUS_RESPONSE using an ordinary send. If the LWIO_HDR_FLAG_INTERRUPT flag is not set (polling mode), then the server completes the client request by RDMAing an LWIO _ O_STATUS_BLOCK to the client, as indicated at step 805.
- the client may wish to sleep while waiting for an I/O completion from the server. Completions in this case are sent by way of RDMA to the client, so a mechanism is needed to wake up the client to notify it that a completion has occurred.
- the client wishes to be woken up, it sends an interrupt request (LWIO_OPCODE_INTERRUPT) message to the server, received by the server at step 807 of FIG. 8.
- a server that receives an interrupt request will not send a response until an I/O request has completed on the server (step 809).
- the completion is sent to the client at step 811 by way of an ordinary send, interrupting the client. Only one interrupt message can be outstanding for a given client connection.
- FIG. 9 A provides an illustrative representation of the interrupt request message sent by the client to the server in an embodiment of the invention.
- the message comprises the common header 815.
- Opcode 817 is set to LWIO_OPCODE_REGISTER (0x9).
- Flags 819 is set to (LWIO_HDR_FLAG_INTERRUPT
- Credits 821 is set to the number of pending I7O requests on the client, and Cookie 823 is set to a client-specified value.
- FIG. 9B provides an illustrative representation of the LWIO_MSG_STATUS_RESPONSE message 825 sent by server in an embodiment of the invention.
- Information 827 is set to 0.
- Status 829 is set to 0x0 (success) or another NTSTATUS code on failure.
- Cookie 831 is set to the Cookie value in the header of the interrupt request sent by the client. Credits [0088] As has been noted, all client-to-server I/O requests include a credits field in the header. The credits field is a hint to the server regarding the number of outstanding I/O requests that the client would like to send to the server. It is the responsibility of the server to manage credits.
- Credits provide a novel solution to the problem of flushing buffers. If the client currently has N credits, it is required to post N+l receive buffers in order for the server to send the client a credit message. The server has only one outstanding credit request along a client connection at any one time. Credit messages are always sent in interrupt mode.
- a credit transaction comprises a server-initiated three-way handshake between client and server.
- FIG. 10 generally illustrates the steps comprising the credit transaction in an embodiment of the invention.
- the server sends a delta credit request message along a client connection.
- FIG. 11 A provides an illustrative representation of the server delta credit message in an embodiment of the invention.
- This message takes the form of an LWIO_MSG_STATUS JRESPONSE 1011. Credits correspond to buffers.
- Information 1013 is set to the number of credits that the client should give up (a negative number) or the number of credits (extra buffers) that the server has newly allocated for the client's use (a positive number).
- Status 1015 is set to LWIO_NOTIFY_CREDIT (0x1).
- Cookie 1017 is set to 0.
- the client receives the credit message from the server.
- the client is required to respond with an LWIO_OPCODE_CREDIT message to the server on the same connection.
- This message signifies either the releasing of a single credit or notifying the server of the number of the newly-allocated credits that the client has used.
- the client sends N LWIO DPCODE_CREDIT messages (one for each credit that it is required to give up), indicated as step 1005. If the Information field is positive, then the client sends only one LWIO_OPCODE_CREDIT message, indicated as step 1007.
- FIG. 1 IB provides an illustrative representation of the
- LWIO_OPCODE_CREDIT message sent by the client in an embodiment of the invention comprises a common header 1021.
- Opcode 1023 is set to LWIO_OPCODE_CREDIT (0x8).
- Flags 1025 is set to LWIO_ HDR_FLAG_TNTERRUPT (0x80).
- Credits 1027 is set to the number of pending I/O requests on the client.
- Cookie 1031 is set to a client-specified value. If the client received a positive delta credit message, the upper 32 bits of Offset 1029 are set to the number of credits allocated by the server that the client did not use.
- the server normally does not send another positive update message until at least one negative update is sent. Typically, the client returns zero.
- the client if the client received a negative (-N) delta credit message, the client is required to send N credit messages to the server, one for each credit that it is giving up.
- the upper 32 bits of Offset 1029 in this case are accordingly set to -N, -(N-l), . . . , -1.
- the server assumes that the client has finished processing the server credit message and is eligible to receive new credit messages.
- FIG. 11C provides an illustrative representation of the LWIO_MSG_STATUS_RESPONSE 1033 sent by the server in an embodiment of the invention.
- Information 1037 is set to 0. If the upper 32 bits of Offset in the header of the LWIO_OPCODE_CREDIT message sent by the client was greater than or equal to zero, Status 1039 is set to 0x0, signifying success.
- the server sets Status 1039 to LWIO_CREDIT_NOTIFY in order to allow the client to retire the credit.
- Cookie 1035 is set to the Cookie value set by the client in the common header of the LWIO_OPCODE_CREDIT message.
- FIG. 12A provides an illustrative representation of the close message sent by the client in an embodiment of the invention.
- the close message 1041 comprises a common header 1043.
- Opcode 1045 is set to LWIO_OPCODE_CLOSE (0x4).
- Flags 1047 is set to LWIO_HDR_FLAG_INTERRUPT (0x80).
- Credits 1049 is set to the number of pending I/O requests on the client.
- Cookie 1053 is set to a client-specified value.
- Fid 1051 is set to the File Id of the file that is to be closed.
- FIG. 12B provides an illustrative representation of the close completion
- LWIO_MSG_STATUS_RESPONSE 1055 returned by the server in an embodiment of the invention.
- Infonnation 1059 is set to 0.
- Status 1061 is set to 0, indicating success.
- Cookie 1057 is set to the Cookie value that was set in the client close request.
- the cancel message is used to stop I/O processing for a particular Fid that was exchanged during the registration stage.
- the server completes the request.
- I/O requests that cannot be canceled may still proceed on the server.
- FIG. 13 A provides an illustrative representation of the cancel message sent by the client in an embodiment of the invention.
- the cancel message 1063 comprises a common header 1065.
- Opcode 1067 is set to LWIO_OPCODE_CANCEL (0x5).
- Flags 1069 is set to LWIOJHDR_FLAGJNTERRUPT (0x80).
- Credits 1071 is set to the number of pending I/O requests on the client.
- Cookie 1075 is set to a client-specified value.
- Fid 1073 is set to the File Id on which the cancel is being issued.
- FIG. 13B provides an illustrative representation of the cancel completion LWIO__MSG_STATUS_RESPONSE 1077 returned by the server in an embodiment of the invention.
- Information 1081 is set to 0.
- Status 1083 is set to 0, indicating success.
- Cookie 1079 is set to the Cookie value that was set in the client cancel request [0099]
- the read message is used to obtain data from a particular Fid that was exchanged during the registration stage.
- the user buffer For a read request smaller than one kilobyte, if the user buffer is not registered with the NIC, the data is received into an internal pre-registered buffer, and a copy is performed into the user buffer once the data is received from the server. This is done because it is more efficient to copy small amounts of data rather than to register small user buffers. For large reads the user buffer is registered and the data is received directly by way of RDMA write. The amount of data read pursuant to a single read request is limited by the server MaxRdmaWindowSize.
- FIGS. 14A and 14C provide illustrative representations of the read message sent by the client in an embodiment of the invention, with FIG. 14A giving the non-polling case and FIG. 14C giving the polling case.
- the read message 1401 comprises a common header 1403.
- Length 1405 is set to the number of bytes to be read from the associated file.
- Opcode 1407 is set to LWIO__OPCODE_READ (0x0).
- Offset 1417 is set to the byte location at which the file read is to begin.
- Marker 1413 is set to OxFF.
- Flags 1409, 1427 is set to 0x0 in the polling case 1427 or LWIO_HDR_FLAG_INTERRUPT (0x80) in the non-polling case 1409.
- Fid 1415 is set to the File Id on which to issue the VO.
- DataVa 1419 is set to the address to which the read data is to be RDMAed, and DataMh 1421 is set to the associated memory handle.
- ImmediateCookie 1423 and Cookie 1425 are set to client-specified values.
- the server can complete the read request in this case with an LWIO_MSG_STATUS_RESPONSE by way of a normal send, or with an RDMA with immediate data if the read is successful.
- the immediate data of the RDMA write is accordingly set to the ImmediateCookie value of the read request, hi the polling case, IosVa 1431 is set to the location to which the server response status (LWIO_IO_STATUS_BLOCK) is RDMAed, and IosMh 1429 is set to the associated memory handle.
- the server first RDMAs the read data.
- the server then can respond with an LWIO_MSG_STATUS_RESPONSE, or the server can send immediate data with the RDMA read data, in which case the immediate data is set to the ImmediateCookie value of the read request.
- FIG. 14B provides an illustrative representation of the LWIO_MSG_STATUS_RESPONSE 1433 returned by the server in the non-polling case in an embodiment of the invention.
- Information 1437 is set to the number of bytes read.
- Status 1439 is set to 0, indicating success, or to another NTSTATUS, indicating failure.
- Cookie 1435 is set to the Cookie value set by the client in the header of the read message.
- the server In the polling case, the server first RDMAs the read data. The server then RDMAs an LWIO_IO_STATUS_BLOCK to the client.
- FIG. 14D provides an illustrative representation of the LWIO_IO_STATUS_BLOCK 1441 returned by the server in an embodiment of the invention.
- Infomiation 1443 is set to the number of bytes read.
- Status 1445 is set to 0, indicating success, or another NTSTATUS, indicating failure.
- the write message is used to place data into a particular Fid that was exchanged during the file registration. All write data is sent using ordinary send operations. The amount of data written is limited by the server MaxRecvBufferSize. If the client sends more data than this, the connection is terminated.
- FIGS. 15A and 15C provide illustrative representations of the write message sent by the client in an embodiment of the invention, with FIG. 15A giving the non-polling case and FIG. 15C giving the polling case.
- the write message 1501 includes a common header 1503.
- Length 1505 is set to the number of bytes of data to be written.
- Opcode 1507 is set to LWIO_OPCODE_WRITE (0x1).
- Offset 1517 is set to the byte location at which to begin writing the file data.
- Flags 1509, 1529 is set to 0x0 in the polling case 1529 or LWIO_HDR_FLAG_INTERRUPT (0x80) in the ' non-polling case 1509.
- Marker 1513 is set to OxFF.
- Credits 1511 is set to the number of pending I/O requests on the client.
- Fid 1515 is set to the File Id on which to issue the I/O.
- the data to be written 1527 immediately follows the
- Cookie 1525 is set to a client-specified value.
- IosVa 1533 is set to the location at which the server response status (LWIO_IO_STATUS_BLOCK) is RDMAed, and IosMh 1531 is set to the associated memory handle.
- the server responds to the write message with an LWIO_MSG_STATUS_RESPONSE.
- FIG. 15B provides an illustrative representation of the LWIO_MSG_STATUS_RESPONSE 1535 returned by the server in an embodiment of the invention.
- Information 1539 is set to the number of bytes written.
- Status 1541 is set to 0, indicating success, or to another NTSTATUS, indicating failure.
- Coolde 1537 is set to the Cookie value set by the client in the header of the write message.
- the server RDMAs an LWIO_IO_STATUS_BLOCK.
- FIG. 15D provides an illustrative representation of the LWIO_IO_STATUS_BLOCK 1543 returned by the server in an embodiment of the invention.
- Information 1545 is set to the number of bytes written.
- Status 1547 is set to 0, indicating success, or to another NTSTATUS, indicating failure.
- the vectored read is used to obtain data from a particular Fid that was exchanged during the registration stage and to scatter the data on a page basis to multiple segments on the requester. All data read is sent to the requester by way of RDMA writes, with one RDMA write from the server for each read segment. The data read from disk is contiguous. The amount of data read is limited by the maximum number of destination pages that can be described hi a single request. This limit is the server MaxRecvBufferSize divided by sizeof(LWIO_RDMA_REGION). The structure of LWIO_RDMA_REGION is given below.
- FIGS. 16A and 16C provide illustrative representations of the vectored read message sent by the client in an embodiment of the invention, with FIG. 16A giving the non-polling case and FIG. 16C giving the polling case.
- the read message 1401 comprises a common header 1603 followed by one or more LWIO_RDMA_REGION segments 1605, 1607.
- Length 1609 is set to the number of bytes of data to be read from the file.
- Opcode 1611 is set to LWIO_OPCODE_VEC_READ (0x2).
- Offset 1621 is set to the byte location at which to begin reading the file data.
- Flags 1613, 1631 is set to 0x0 in the polling case 1631, or LWIO_HDR_FLAG_INTERRUPT (0x80) in the non-polling case 1613.
- Marker 1617 is set to OxFF.
- Credits 1615 is set to the number of pending I/O requests on the client.
- Fid 1619 is set to the File Id on which to issue the I/O.
- NumPages 1623 is set to the number of LWIO_RDMA_REGIONs that follow the common header 1603.
- PageSize 1625 is set to the local page size in bytes.
- ImmediateCookie 1627 and Cookie 1629 are set to client-specified values.
- the server can complete the vectored read request in this case with an LWIO_MSG_STATUS_RESPONSE by way of a normal send, or with an RDMA with immediate data if the read is successful.
- the immediate data of the RDMA write is accordingly set to the ImmediateCookie 1627 value of the read request, h the polling case, IosVa 1635 is set to the location at which the server response status (LWIOJO_STATUS_BLOCK) is RDMAed, and IosMh 1633 is set to the associated memory handle.
- LWIO__RDMA_REGION has the following format:
- the first LWIO_RDMA_REGION corresponds to the first PageSize bytes read
- the second LWIO_RDMA_REGION corresponds to the second PageSize bytes read
- DataVa 1637 is set to the location marking the beginning of the page in which the read data is to be placed.
- DataMh 1639 is set to the memory handle of the DataVa 1637.
- Length 1641 is set to the PageSize 1625 for all regions except for the final region, for which Length may be smaller but must be a multiple of the backend disk sector size. [0113] In the non-polling case, the server first RDMAs the read data.
- FIG. 16B provides an illustrative representation of the LWIO_MSG_STATUS_RESPONSE 1643 returned by the server in the non-polling case in an embodiment of the invention.
- Information 1647 is set to the number of bytes read.
- Status 1649 is set to 0, indicating success, or to another NTSTATUS, indicating failure.
- Cookie 1645 is set to the Cookie value set by the client in the header of the vectored read message.
- FIG. 16D provides an illustrative representation of the LWIO_IO_STATUS_BLOCK 1651 returned by the server in an embodiment of the invention.
- Information 1653 is set to the number of bytes read.
- Status 1655 is set to 0, indicating success, or another NTSTATUS, indicating failure.
- FIGS. 17A, 17B and 17C provide illustrative representations of the vectored write message sent by the client in an embodiment of the invention, with FIG. 17A illustrating the non-polling, non-collapse case, FIG. 17B illustrating the non-polling, collapse case, and FIG. 17C illustrating the polling, collapse case.
- the write message 1701 includes a common header 1703, immediately followed by the data to be written 1705.
- Length 1707 is set to the number of bytes of data being written.
- Opcode 1709 is set to LWIO_OPCODE_WRITE (0x3).
- Offset 1719 is set to the byte location at which to begin writing the file data.
- Marker 1715 is set to OxFF.
- Credits 1713 is set to the number of pending I/O requests on the client.
- Fid 1717 is set to the File Id on which to issue the I/O.
- Flags 1711, 1721, 1727 is set to 0x0, signifying polling 1727, or else to LWIOJHDR_FLAG_INTERRUPT (0x80) 1711.
- flags can also include LWIO__HDR_FLAG_COLLAPSE 1721 to indicate that all pages in the write contain the same data, so that only a single page of data has been sent. This is an optimization intended to minimize the transfer of redundant data.
- LWIO_HDR_FLAG_COLLAPSE can only be used if the registered file flags include FILE_NO_INTERMEDIATE_BUFFERING (0x8) and the PageSizes exchanged during the authentication stage are even multiples of each other.
- NumPages 1723 is set to the number of pages of data spanned by the I/O. The last page may be partial due to the Length parameter.
- PageSize 1725 is set to the local page size in bytes.
- IosVa 1731 is set to the location at which the server response status (LWIO_IO_STATUS_BLOCK) is to be RDMAed.
- IosMh 1729 is the associated memory handle.
- FIG. 17D provides an illustrative representation of the
- LWIO_MSG_STATUSJRESPONSE 1733 returned by the server in an embodiment of the invention.
- Information 1737 is set to the number of bytes written.
- Status 1739 is set to 0, indicating success, or to another NTSTATUS, indicating failure.
- Cookie 1735 is set to the Cookie value set by the client in the header of the write message.
- FIG. 17E provides an illustrative representation of the LWIO__IO_STATUS_BLOCK 1741 returned by the server in an embodiment of the invention, frifonnation 1743 is set to the number of bytes written. Status 1745 is set to 0, indicating success, or to another NTSTATUS, indicating failure.
Abstract
Description
Claims
Priority Applications (11)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2004279182A AU2004279182B2 (en) | 2003-12-31 | 2004-07-26 | Lightweight input/output protocol |
NZ540173A NZ540173A (en) | 2003-12-31 | 2004-07-26 | Lightweight input/output protocol |
BR0406413-5A BRPI0406413A (en) | 2003-12-31 | 2004-07-26 | Lightweight inbound / outbound protocol |
MXPA05006638A MXPA05006638A (en) | 2003-12-31 | 2004-07-26 | Lightweight input/output protocol. |
KR1020057007528A KR101084897B1 (en) | 2003-12-31 | 2004-07-26 | Lightweight input/output protocol |
JP2006546957A JP4564970B2 (en) | 2003-12-31 | 2004-07-26 | Lightweight input / output protocol |
EP04779200A EP1700264A4 (en) | 2003-12-31 | 2004-07-26 | Lightweight input/output protocol |
CN2004800013330A CN101375263B (en) | 2003-12-31 | 2004-07-26 | System and method for downloading input/output I/O task from a first computer to a second computer |
CA002501521A CA2501521A1 (en) | 2003-12-31 | 2004-07-26 | Lightweight input/output protocol |
NO20052054A NO20052054L (en) | 2003-12-31 | 2005-04-26 | Simplified in / out protocol |
IL168595A IL168595A (en) | 2003-12-31 | 2005-05-16 | Lightweight input/output protocol |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/749,959 US7698361B2 (en) | 2003-12-31 | 2003-12-31 | Lightweight input/output protocol |
US10/749,959 | 2003-12-31 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2005067430A2 true WO2005067430A2 (en) | 2005-07-28 |
WO2005067430A3 WO2005067430A3 (en) | 2008-04-24 |
Family
ID=34701133
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2004/024026 WO2005067430A2 (en) | 2003-12-31 | 2004-07-26 | Lightweight input/output protocol |
Country Status (17)
Country | Link |
---|---|
US (2) | US7698361B2 (en) |
EP (1) | EP1700264A4 (en) |
JP (1) | JP4564970B2 (en) |
KR (1) | KR101084897B1 (en) |
CN (1) | CN101375263B (en) |
AU (1) | AU2004279182B2 (en) |
BR (1) | BRPI0406413A (en) |
CA (1) | CA2501521A1 (en) |
IL (1) | IL168595A (en) |
MX (1) | MXPA05006638A (en) |
MY (2) | MY158076A (en) |
NO (1) | NO20052054L (en) |
NZ (2) | NZ540173A (en) |
RU (2) | RU2388039C2 (en) |
TW (2) | TW201240413A (en) |
WO (1) | WO2005067430A2 (en) |
ZA (1) | ZA200503161B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10452579B2 (en) | 2017-07-05 | 2019-10-22 | Fujitsu Limited | Managing input/output core processing via two different bus protocols using remote direct memory access (RDMA) off-loading processing system |
Families Citing this family (57)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7529778B1 (en) | 2001-12-12 | 2009-05-05 | Microsoft Corporation | System and method for providing access to consistent point-in-time file versions |
US7698361B2 (en) * | 2003-12-31 | 2010-04-13 | Microsoft Corporation | Lightweight input/output protocol |
US7617256B2 (en) * | 2004-07-19 | 2009-11-10 | Microsoft Corporation | Remote file updates through remote protocol |
US20060168094A1 (en) * | 2005-01-21 | 2006-07-27 | International Business Machines Corporation | DIRECT ACCESS OF SCSI BUFFER WITH RDMA ATP MECHANISM BY iSCSI TARGET AND/OR INITIATOR |
US8316129B2 (en) | 2005-05-25 | 2012-11-20 | Microsoft Corporation | Data communication coordination with sequence numbers |
US7549037B1 (en) * | 2005-09-01 | 2009-06-16 | Symantec Operating Corporation | Efficient off-host backup of a file set clone |
US8151116B2 (en) * | 2006-06-09 | 2012-04-03 | Brigham Young University | Multi-channel user authentication apparatus system and method |
ES2382108T3 (en) * | 2006-07-27 | 2012-06-05 | Contextream Ltd. | Distributed edge network |
US7836143B2 (en) | 2007-04-25 | 2010-11-16 | International Business Machines Corporation | Message communications of particular message types between compute nodes using DMA shadow buffers |
US8325633B2 (en) | 2007-04-26 | 2012-12-04 | International Business Machines Corporation | Remote direct memory access |
US7827024B2 (en) | 2007-05-09 | 2010-11-02 | International Business Machines Corporation | Low latency, high bandwidth data communications between compute nodes in a parallel computer |
US7966618B2 (en) * | 2007-05-29 | 2011-06-21 | International Business Machines Corporation | Controlling data transfers from an origin compute node to a target compute node |
US8037213B2 (en) | 2007-05-30 | 2011-10-11 | International Business Machines Corporation | Replenishing data descriptors in a DMA injection FIFO buffer |
US7921428B2 (en) | 2007-06-18 | 2011-04-05 | International Business Machines Corporation | Multi-registration of software library resources |
US8018951B2 (en) | 2007-07-12 | 2011-09-13 | International Business Machines Corporation | Pacing a data transfer operation between compute nodes on a parallel computer |
US8478834B2 (en) | 2007-07-12 | 2013-07-02 | International Business Machines Corporation | Low latency, high bandwidth data communications between compute nodes in a parallel computer |
US8959172B2 (en) | 2007-07-27 | 2015-02-17 | International Business Machines Corporation | Self-pacing direct memory access data transfer operations for compute nodes in a parallel computer |
US7805546B2 (en) * | 2007-07-27 | 2010-09-28 | International Business Machines Corporation | Chaining direct memory access data transfer operations for compute nodes in a parallel computer |
US8929372B2 (en) * | 2007-10-30 | 2015-01-06 | Contextream Ltd. | Grid router |
US8467295B2 (en) | 2008-08-21 | 2013-06-18 | Contextream Ltd. | System and methods for distributed quality of service enforcement |
IT1391040B1 (en) * | 2008-10-01 | 2011-10-27 | St Microelectronics Srl | PROCEDURE FOR PERFORMING TRANSACTIONS IN COMMUNICATION NETWORKS, COMMUNICATION NETWORK AND RELATED COMPUTER PRODUCT |
US8521821B2 (en) * | 2009-03-17 | 2013-08-27 | Brigham Young University | Encrypted email based upon trusted overlays |
US8949453B2 (en) | 2010-11-30 | 2015-02-03 | International Business Machines Corporation | Data communications in a parallel active messaging interface of a parallel computer |
US8806030B2 (en) * | 2010-12-06 | 2014-08-12 | Microsoft Corporation | Multichannel connections in file system sessions |
US8631277B2 (en) | 2010-12-10 | 2014-01-14 | Microsoft Corporation | Providing transparent failover in a file system |
US9146765B2 (en) | 2011-03-11 | 2015-09-29 | Microsoft Technology Licensing, Llc | Virtual disk storage techniques |
FR2973185B1 (en) * | 2011-03-22 | 2013-03-29 | Sagem Defense Securite | METHOD AND DEVICE FOR CONNECTING TO A HIGH SECURITY NETWORK |
US9331955B2 (en) * | 2011-06-29 | 2016-05-03 | Microsoft Technology Licensing, Llc | Transporting operations of arbitrary size over remote direct memory access |
US8856582B2 (en) | 2011-06-30 | 2014-10-07 | Microsoft Corporation | Transparent failover |
US8949328B2 (en) | 2011-07-13 | 2015-02-03 | International Business Machines Corporation | Performing collective operations in a distributed processing system |
US8788579B2 (en) | 2011-09-09 | 2014-07-22 | Microsoft Corporation | Clustered client failover |
US20130067095A1 (en) | 2011-09-09 | 2013-03-14 | Microsoft Corporation | Smb2 scaleout |
JP5966229B2 (en) * | 2011-10-27 | 2016-08-10 | ▲ホア▼▲ウェイ▼技術有限公司Huawei Technologies Co.,Ltd. | Method and apparatus for high-speed data distribution |
US8930962B2 (en) | 2012-02-22 | 2015-01-06 | International Business Machines Corporation | Processing unexpected messages at a compute node of a parallel computer |
CN102708062A (en) * | 2012-04-10 | 2012-10-03 | 深圳市佳信捷电子有限公司 | Multimedia storage method and multimedia storage device based on data block |
US9111081B2 (en) | 2012-06-26 | 2015-08-18 | International Business Machines Corporation | Remote direct memory access authentication of a device |
US9251201B2 (en) * | 2012-12-14 | 2016-02-02 | Microsoft Technology Licensing, Llc | Compatibly extending offload token size |
US9986028B2 (en) * | 2013-07-08 | 2018-05-29 | Intel Corporation | Techniques to replicate data between storage servers |
AU2013245529A1 (en) * | 2013-10-18 | 2015-05-07 | Cisco Technology, Inc. | Network Interface |
US20150326684A1 (en) * | 2014-05-07 | 2015-11-12 | Diablo Technologies Inc. | System and method of accessing and controlling a co-processor and/or input/output device via remote direct memory access |
CN104202391B (en) * | 2014-08-28 | 2018-09-25 | 浪潮(北京)电子信息产业有限公司 | RDMA communication means between the no tight coupling system of shared system address space |
RU2599937C1 (en) * | 2015-03-26 | 2016-10-20 | Общество с ограниченной ответственностью "Научно-производственное предприятие "Цифровые решения" | Method for prevention of faults in a local computer network caused by onset of incorrect units |
US10257273B2 (en) * | 2015-07-31 | 2019-04-09 | Netapp, Inc. | Systems, methods and devices for RDMA read/write operations |
US9952797B2 (en) | 2015-07-31 | 2018-04-24 | Netapp, Inc. | Systems, methods and devices for addressing data blocks in mass storage filing systems |
RU2638781C2 (en) * | 2016-09-29 | 2017-12-15 | Общество с ограниченной ответственностью "ГРЭК" | Method for arranging direct access to memory in transmission of information between physical objects |
US10523675B2 (en) * | 2017-11-08 | 2019-12-31 | Ca, Inc. | Remote direct memory access authorization |
RU2731321C2 (en) | 2018-09-14 | 2020-09-01 | Общество С Ограниченной Ответственностью "Яндекс" | Method for determining a potential fault of a storage device |
RU2718215C2 (en) | 2018-09-14 | 2020-03-31 | Общество С Ограниченной Ответственностью "Яндекс" | Data processing system and method for detecting jam in data processing system |
RU2714219C1 (en) | 2018-09-14 | 2020-02-13 | Общество С Ограниченной Ответственностью "Яндекс" | Method and system for scheduling transfer of input/output operations |
RU2721235C2 (en) | 2018-10-09 | 2020-05-18 | Общество С Ограниченной Ответственностью "Яндекс" | Method and system for routing and execution of transactions |
RU2714602C1 (en) | 2018-10-09 | 2020-02-18 | Общество С Ограниченной Ответственностью "Яндекс" | Method and system for data processing |
RU2711348C1 (en) | 2018-10-15 | 2020-01-16 | Общество С Ограниченной Ответственностью "Яндекс" | Method and system for processing requests in a distributed database |
CN109377778B (en) * | 2018-11-15 | 2021-04-06 | 浪潮集团有限公司 | Collaborative automatic driving system and method based on multipath RDMA and V2X |
RU2714373C1 (en) | 2018-12-13 | 2020-02-14 | Общество С Ограниченной Ответственностью "Яндекс" | Method and system for scheduling execution of input/output operations |
RU2749649C2 (en) | 2018-12-21 | 2021-06-16 | Общество С Ограниченной Ответственностью "Яндекс" | Method and system for scheduling processing of i/o operations |
RU2720951C1 (en) | 2018-12-29 | 2020-05-15 | Общество С Ограниченной Ответственностью "Яндекс" | Method and distributed computer system for data processing |
RU2746042C1 (en) | 2019-02-06 | 2021-04-06 | Общество С Ограниченной Ответственностью "Яндекс" | Method and the system for message transmission |
Family Cites Families (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10612A (en) * | 1854-03-07 | Seaman | ||
WO1995003586A1 (en) * | 1993-07-21 | 1995-02-02 | Persistence Software, Inc. | Method and apparatus for generation of code for mapping relational data to objects |
US6014681A (en) * | 1997-07-15 | 2000-01-11 | Microsoft Corporation | Method for saving a document using a background save thread |
US6226680B1 (en) * | 1997-10-14 | 2001-05-01 | Alacritech, Inc. | Intelligent network interface system method for protocol processing |
US6219761B1 (en) * | 1998-05-06 | 2001-04-17 | International Business Machines Corporation | Load/store assist engine |
US6356863B1 (en) * | 1998-09-08 | 2002-03-12 | Metaphorics Llc | Virtual network file server |
CA2386293A1 (en) * | 1999-09-29 | 2001-04-05 | Cyberset Technologies, Inc. | Method and apparatus for an active file system |
US6718370B1 (en) * | 2000-03-31 | 2004-04-06 | Intel Corporation | Completion queue management mechanism and method for checking on multiple completion queues and processing completion events |
US7103626B1 (en) * | 2000-05-24 | 2006-09-05 | Hewlett-Packard Development, L.P. | Partitioning in distributed computer system |
JP4192416B2 (en) * | 2000-06-08 | 2008-12-10 | 株式会社日立製作所 | Computer system and data transfer method thereof |
WO2002037300A1 (en) * | 2000-11-02 | 2002-05-10 | Pirus Networks | Switching system |
US7313614B2 (en) * | 2000-11-02 | 2007-12-25 | Sun Microsystems, Inc. | Switching system |
US6891635B2 (en) * | 2000-11-30 | 2005-05-10 | International Business Machines Corporation | System and method for advertisements in web-based printing |
US6976174B2 (en) * | 2001-01-04 | 2005-12-13 | Troika Networks, Inc. | Secure multiprotocol interface |
US6898638B2 (en) * | 2001-01-11 | 2005-05-24 | International Business Machines Corporation | Method and apparatus for grouping data for transfer according to recipient buffer size |
US6748502B2 (en) * | 2001-01-12 | 2004-06-08 | Hitachi, Ltd. | Virtual volume storage |
US6898740B2 (en) * | 2001-01-25 | 2005-05-24 | Hewlett-Packard Development Company, L.P. | Computer system having configurable core logic chipset for connection to a fault-tolerant accelerated graphics port bus and peripheral component interconnect bus |
US7401126B2 (en) * | 2001-03-23 | 2008-07-15 | Neteffect, Inc. | Transaction switch and network interface adapter incorporating same |
US20020144037A1 (en) * | 2001-03-29 | 2002-10-03 | Bennett Joseph A. | Data fetching mechanism and method for fetching data |
US8051212B2 (en) * | 2001-04-11 | 2011-11-01 | Mellanox Technologies Ltd. | Network interface adapter with shared data send resources |
US20020184362A1 (en) * | 2001-05-31 | 2002-12-05 | International Business Machines Corporation | System and method for extending server security through monitored load management |
US6832297B2 (en) * | 2001-08-09 | 2004-12-14 | International Business Machines Corporation | Method and apparatus for managing data in a distributed buffer system |
CN100367254C (en) * | 2001-08-24 | 2008-02-06 | 英特尔公司 | A general input/output architecture, protocol and related methods to support legacy interrupts |
US6895590B2 (en) * | 2001-09-26 | 2005-05-17 | Intel Corporation | Method and system enabling both legacy and new applications to access an InfiniBand fabric via a socket API |
US20030065856A1 (en) * | 2001-10-03 | 2003-04-03 | Mellanox Technologies Ltd. | Network adapter with multiple event queues |
US20030145230A1 (en) * | 2002-01-31 | 2003-07-31 | Huimin Chiu | System for exchanging data utilizing remote direct memory access |
US8005966B2 (en) * | 2002-06-11 | 2011-08-23 | Pandya Ashish A | Data processing system using internet protocols |
US20040003069A1 (en) * | 2002-06-28 | 2004-01-01 | Broadcom Corporation | Selective early drop method and system |
US6760793B2 (en) * | 2002-07-29 | 2004-07-06 | Isys Technologies, Inc. | Transaction credit control for serial I/O systems |
US7107385B2 (en) * | 2002-08-09 | 2006-09-12 | Network Appliance, Inc. | Storage virtualization by layering virtual disk objects on a file system |
US7051140B2 (en) * | 2002-11-13 | 2006-05-23 | International Business Machines Corporation | Connector that enables aggregation of independent system resources across PCI/PCI-X bus and interlocked method for aggregating independent system resources across PCI/PCI-X bus |
US7366092B2 (en) * | 2003-10-14 | 2008-04-29 | Broadcom Corporation | Hash and route hardware with parallel routing scheme |
US7457861B1 (en) * | 2003-12-05 | 2008-11-25 | Unisys Corporation | Optimizing virtual interface architecture (VIA) on multiprocessor servers and physically independent consolidated NICs |
US6996070B2 (en) * | 2003-12-05 | 2006-02-07 | Alacritech, Inc. | TCP/IP offload device with reduced sequential processing |
US20050137966A1 (en) * | 2003-12-19 | 2005-06-23 | Munguia Peter R. | Flow control credit synchronization |
US8549170B2 (en) * | 2003-12-19 | 2013-10-01 | Nvidia Corporation | Retransmission system and method for a transport offload engine |
US7698361B2 (en) * | 2003-12-31 | 2010-04-13 | Microsoft Corporation | Lightweight input/output protocol |
-
2003
- 2003-12-31 US US10/749,959 patent/US7698361B2/en not_active Expired - Fee Related
-
2004
- 2004-07-16 MY MYPI20084350A patent/MY158076A/en unknown
- 2004-07-16 MY MYPI20042851A patent/MY143575A/en unknown
- 2004-07-21 TW TW101121785A patent/TW201240413A/en unknown
- 2004-07-21 TW TW093121799A patent/TW200522630A/en unknown
- 2004-07-26 BR BR0406413-5A patent/BRPI0406413A/en not_active IP Right Cessation
- 2004-07-26 EP EP04779200A patent/EP1700264A4/en not_active Withdrawn
- 2004-07-26 KR KR1020057007528A patent/KR101084897B1/en not_active IP Right Cessation
- 2004-07-26 NZ NZ540173A patent/NZ540173A/en not_active IP Right Cessation
- 2004-07-26 CA CA002501521A patent/CA2501521A1/en not_active Abandoned
- 2004-07-26 RU RU2005120695/09A patent/RU2388039C2/en not_active IP Right Cessation
- 2004-07-26 CN CN2004800013330A patent/CN101375263B/en not_active Expired - Fee Related
- 2004-07-26 ZA ZA200503161A patent/ZA200503161B/en unknown
- 2004-07-26 WO PCT/US2004/024026 patent/WO2005067430A2/en not_active Application Discontinuation
- 2004-07-26 NZ NZ580159A patent/NZ580159A/en not_active IP Right Cessation
- 2004-07-26 MX MXPA05006638A patent/MXPA05006638A/en active IP Right Grant
- 2004-07-26 AU AU2004279182A patent/AU2004279182B2/en not_active Ceased
- 2004-07-26 JP JP2006546957A patent/JP4564970B2/en not_active Expired - Fee Related
-
2005
- 2005-04-26 NO NO20052054A patent/NO20052054L/en not_active Application Discontinuation
- 2005-05-16 IL IL168595A patent/IL168595A/en not_active IP Right Cessation
-
2009
- 2009-03-17 RU RU2009109685/08A patent/RU2009109685A/en unknown
-
2010
- 2010-03-04 US US12/717,306 patent/US20100161855A1/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
See references of EP1700264A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10452579B2 (en) | 2017-07-05 | 2019-10-22 | Fujitsu Limited | Managing input/output core processing via two different bus protocols using remote direct memory access (RDMA) off-loading processing system |
Also Published As
Publication number | Publication date |
---|---|
MY158076A (en) | 2016-08-30 |
JP2007527057A (en) | 2007-09-20 |
CN101375263A (en) | 2009-02-25 |
IL168595A (en) | 2011-02-28 |
KR20060112178A (en) | 2006-10-31 |
US7698361B2 (en) | 2010-04-13 |
CN101375263B (en) | 2012-06-20 |
CA2501521A1 (en) | 2005-06-30 |
MXPA05006638A (en) | 2006-02-22 |
MY143575A (en) | 2011-05-31 |
AU2004279182B2 (en) | 2010-03-11 |
RU2388039C2 (en) | 2010-04-27 |
EP1700264A4 (en) | 2011-06-15 |
NO20052054D0 (en) | 2005-04-26 |
TW201240413A (en) | 2012-10-01 |
US20100161855A1 (en) | 2010-06-24 |
NO20052054L (en) | 2005-06-10 |
US20050198113A1 (en) | 2005-09-08 |
ZA200503161B (en) | 2008-01-30 |
AU2004279182A1 (en) | 2005-07-14 |
BRPI0406413A (en) | 2005-10-04 |
JP4564970B2 (en) | 2010-10-20 |
KR101084897B1 (en) | 2011-11-17 |
RU2009109685A (en) | 2010-09-27 |
NZ580159A (en) | 2011-01-28 |
NZ540173A (en) | 2009-11-27 |
RU2005120695A (en) | 2006-01-20 |
TW200522630A (en) | 2005-07-01 |
EP1700264A2 (en) | 2006-09-13 |
WO2005067430A3 (en) | 2008-04-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7698361B2 (en) | Lightweight input/output protocol | |
US10165051B2 (en) | High performance IP processor using RDMA | |
EP1629656B1 (en) | Processing data for a tcp connection using an offload unit | |
US8180928B2 (en) | Method and system for supporting read operations with CRC for iSCSI and iSCSI chimney | |
US7921240B2 (en) | Method and system for supporting hardware acceleration for iSCSI read and write operations and iSCSI chimney | |
EP1759317B1 (en) | Method and system for supporting read operations for iscsi and iscsi chimney | |
US20050283545A1 (en) | Method and system for supporting write operations with CRC for iSCSI and iSCSI chimney | |
US20050281261A1 (en) | Method and system for supporting write operations for iSCSI and iSCSI chimney | |
Neeser et al. | SoftRDMA: Implementing iWARP over TCP kernel sockets |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2501521 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005/03161 Country of ref document: ZA Ref document number: 200503161 Country of ref document: ZA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020057007528 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1824/DELNP/2005 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 168595 Country of ref document: IL Ref document number: 1-2005-500919 Country of ref document: PH |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004779200 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006546957 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20048013330 Country of ref document: CN Ref document number: 540173 Country of ref document: NZ |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004279182 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 05050648 Country of ref document: CO |
|
WWE | Wipo information: entry into national phase |
Ref document number: PA/a/2005/006638 Country of ref document: MX |
|
ENP | Entry into the national phase |
Ref document number: 2005120695 Country of ref document: RU Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2004279182 Country of ref document: AU Date of ref document: 20040726 Kind code of ref document: A |
|
WWP | Wipo information: published in national office |
Ref document number: 2004279182 Country of ref document: AU |
|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
ENP | Entry into the national phase |
Ref document number: PI0406413 Country of ref document: BR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 2004779200 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1020057007528 Country of ref document: KR |