Non-blocking buffered inter-machine data transfer with acknowledgment

• US 8,463,937 B2
• Filed: 08/23/2006
• Issued: 06/11/2013
• Est. Priority Date: 03/24/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bush, Eric N.
• Primary Examiner(s): NGUYEN, PHUOC H
• Application Number:
  US11/509,438
• Publication Number:
  US 20060294193A1
• Time in Patent Office: 2,484 Days
• Field of Search: 709/213, 709/203, 709/238, 709/242, 719/101, 719/318
• US Class Current: 709/238
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A system, method and data structures for transmitting batched data over a network in asynchronous, non-blocking operations, with acknowledgements returned to the senders. Each machine includes a sender subsystem and a receiver subsystem. Transmission items corresponding to data to be sent are buffered until a send is triggered, at which time the transmission items are sorted according to their destinations and sent as a GUID-identified batch to each destination by a send thread. At each receiver, a receiving thread adds descriptions of the data to a receive list, which a transfer thread processes when triggered. The transfer thread sends the corresponding data to a recipient program, and sends GUID-identified acknowledgements corresponding to each GUID back to the originating senders. An acknowledge thread at each originating sender buffers the acknowledgements, and when triggered, a cleanup thread uses the GUID to identify which batched transmissions were received.

Claims

1. In a computing environment, a system comprising:

a sender subsystem of a first machine, the sender subsystem receiving a plurality of transmission items wherein at least two of the transmission items are intended for different destination machines, the sender subsystem maintaining a data structure of the transmission items to send, and the sender subsystem including a send mechanism that sends data, wherein the transmission items are tracked by the sender subsystem in a transmission item list, wherein the transmission item list is closed when the sender subsystem detects a send trigger event, and a new transmission item list is created for tracking transmission items that are received after the transmission item list is closed;

a receiver subsystem of each of at least two destination machines configured to receive data from the sender subsystem of the first machine, the receiver subsystem maintaining a receive data structure of information corresponding to data sent by the sender subsystem; and

the sender subsystem configured to detect the send trigger event and to process the transmission items into per-destination data items such that the transmission items are grouped based on the destination machine to which they are to be sent, the send mechanism sending the per-destination data items and corresponding data to the corresponding destination machines, wherein each per-destination data item has a unique identifier associated therewith, and wherein the receiver subsystem returns an acknowledgement corresponding to the received per-destination data item to the sender subsystem, the acknowledgement including the unique identifier.

2. The system of claim 1 further comprising a data item destination buffer at the first machine, and wherein the sender subsystem maintains the per-destination data items in the data item destination buffer.

3. The system of claim 1 wherein each transmission item specifies at least one destination machine and at least one set of data to send to each destination machine, and wherein in at least one transmission item, each set of data is specified via a data pointer and size information.

4. The system of claim 1 wherein at least two transmission items are submitted to the sender subsystem in a single call from a data generator.

5. The system of claim 1 wherein the sender subsystem comprises a process having a send thread that detects the send trigger event, and wherein the send trigger event corresponds to a time limit being reached, a threshold amount of data being achieved, or a priority level being detected, or any combination of a time limit being reached, a threshold amount of data being achieved, or a priority level being detected.

6. The system of claim 1 wherein the receiver subsystem returns an acknowledgement corresponding to the received per-destination data item to the sender subsystem, and further comprising an acknowledgement handler that places data corresponding to the returned acknowledgement into an acknowledgement data structure.

7. The system of claim 6 further comprising a cleanup mechanism, wherein the cleanup mechanism accesses the acknowledgement data structure to determine which per-destination data items have been successfully received by a destination.

8. The system of claim 7 wherein the cleanup mechanism operates in response to a cleanup trigger event corresponding to a time limit being reached, a threshold amount of data being achieved, or a priority level being detected, or any combination of a time limit being reached, a threshold amount of data being achieved, or a priority level being detected.

9. The system of claim 1 wherein the receiver subsystem of the second machine receives the selected per-destination data item and its corresponding data, and returns an acknowledgement corresponding to the received per-destination data item to the first machine.

10. In a computing environment, a method comprising:

accumulating a plurality of transmission items to send, each transmission item specifying at least one destination machine and at least one set of data to send to each destination machine, wherein the plurality of transmission items include two or more transmission items that specify different destination machines to which they are to be sent, wherein the accumulated transmission items are tracked in a transmission item list;

detecting a send trigger event, and in response, closing the transmission item list and grouping the transmission items in the transmission item list into per-destination data items such that the transmission items are grouped based on the destination machine to which they are to be sent, each per-destination data item identifying a particular destination machine and each set of data to send to the particular destination machine, and further creating a new transmission item list for receiving transmission items that are submitted after the send trigger event is detected;

associating a unique identifier with each per-destination data item;

sending a transmission for each per-destination data item to the destination machine identified in that per-destination data item, the transmission comprising the unique identifier associated with that per-destination data item and each set of data corresponding to that per-destination data item; and

receiving an acknowledgement from each destination machine that received the transmission sent thereto, the acknowledgment comprising the unique identifier.

11. The method of claim 10 further comprising receiving at least two transmission items in a single call from a data generator.

12. The method of claim 10 wherein detecting the send trigger event includes testing for the send trigger event, and wherein testing for the send trigger event comprises a) determining whether a time limit is reached, b) determining whether a threshold amount of data is achieved or c) determining whether a transmission item indicates that at least part of its corresponding data comprises high-priority data, or any combination of a), b) or c) or a), b) and c).

13. The method of claim 10 further comprising, placing data corresponding to returned acknowledgements into an acknowledgement data structure, and accessing the acknowledgement data structure to determine which per-destination data items have been successfully received by a destination.

14. The method of claim 13 further comprising, locating a unique identifier corresponding to a selected acknowledgement in the acknowledgement data structure, freeing data based on the unique identifier, tracking the acknowledgements in the acknowledgement data structure, closing the acknowledgement data structure on a cleanup trigger event, and providing a new acknowledgement data structure for tracking subsequently returned acknowledgements.

15. The method of claim 14 further comprising detecting the cleanup trigger event upon a time limit being reached, a threshold amount of data being achieved, or a priority level being detected, or any combination of a time limit being reached, a threshold amount of data being achieved, or a priority level being detected.

16. The method of claim 10 further comprising, at a specified destination machine, receiving a data transmission from the sender and placing information corresponding to the transmission into a receive data structure.

17. A computer storage medium having computer-executable instructions, which when executed by a processor of a computer perform steps, comprising:

accumulating a plurality of transmission items to send, each transmission item specifying at least one destination machine and at least one set of data to send to each destination machine, wherein the plurality of transmission items include two or more transmission items that specify different destination machines to which they are to be sent, wherein the accumulated transmission items are tracked in a transmission item list;

detecting a send trigger event, and in response, closing the transmission item list and grouping the transmission items in the transmission item list into per-destination data items such that the transmission items are grouped based on the destination machine to which they are to be sent, each per-destination data item identifying a particular destination machine and each set of data to send to the particular destination machine, and further creating a new transmission item list for receiving transmission items that are submitted after the send trigger event is detected;

associating a unique identifier with each per-destination data item;

sending a transmission for each per-destination data item to the destination machine identified in that per-destination data item, the transmission comprising the unique identifier associated with that per-destination data item and each set of data corresponding to that per-destination data item; and

receiving an acknowledgement from each destination machine that received the transmission sent thereto, the acknowledgment comprising the unique identifier.