System and method for atomic file transfer operations over connectionless network protocols

• US 10,033,822 B2
• Filed: 01/05/2015
• Issued: 07/24/2018
• Est. Priority Date: 01/20/2005
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Masputra, Cahya A., Tripathi, Sunay, Srinivasan, Thirumalai
• Primary Examiner(s): Won, Michael Y
• Application Number:
  US14/589,912
• Publication Number:
  US 20150120860A1
• Time in Patent Office: 1,296 Days
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 69/164 Adaptation or special uses of UDP protocol
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers

Abstract

A system for atomic file transfer operations over connectionless network protocols includes a processor and a memory coupled to the processor. The memory contains program instructions executable by the processor to implement an operating system including a system call interface for sending one or more data files to another system over a network via a connectionless network protocol. In response to an invocation of the system call by an application, the operating system is configured to send the one or more data files to the other system over the network without the application copying contents of the data files into application address space.

Claims

1. A system, comprising:

a processor; and

a memory coupled to the processor and configured to store program instructions executable by the processor to implement;

an operating system comprising a system call interface for sending one or more data files to another system over a network via a connectionless network protocol;

an application configured to invoke said system call interface to initiate sending of one or more data files to another system over the network;

wherein, in response to an invocation of said system call interface by the application, the operating system is configured to send the one or more data files to the another system over the network without the application copying contents of the one or more data files into an address space of the application.

2. The system as recited in claim 1, wherein the connectionless network protocol is the User Datagram Protocol (UDP).

3. The system as recited in claim 1, wherein the operating system is configured to send a data file of the one or more data files using one or more datagrams, wherein each datagram of the one or more datagrams includes a header, and wherein, in response to the invocation of the system call interface, the operating system is configured to prepare the header for each datagram of the one or more datagrams without the application generating content for the header.

4. The system as recited in claim 1, wherein the operating system is further configured to store at least one data file of the one or more data files in a kernel cache, and to send the data file from the kernel cache to a second other system in response to a second invocation of the system call interface by the application.

5. The system as recited in claim 1, wherein the application is configured to perform one or more other tasks while the operating system sends the one or more data files.

6. The system as recited in claim 1, wherein a data file of the one or more data files is pre-formatted for datagram-based transmission.

7. The system as recited in claim 1, wherein the invocation of the system call interface includes a parameter specifying at least one of:

a data file of the one or more data files, a communication endpoint, a starting offset within the data file, a packet size, and an amount of data of the data file to be sent to the another system.

8. The system as recited in claim 7, wherein the communication endpoint is a socket.

9. The system as recited in claim 1, wherein the invocation of the system call interface includes a parameter specifying a collection of one or more file specifications, wherein each file specification of the one or more file specifications includes a field identifying a particular data file of the one or more data files.

10. A method, comprising:

providing a system call interface in an operating system for sending one or more data files to a destination system over a network via a connectionless network protocol;

receiving an invocation of the system call interface from an application at the operating system;

in response to the invocation of the system call, the operating system sending the one or more data files to the destination system over the network without the application copying contents of the one or more data files into an address space of the application.

11. The method as recited in claim 10, wherein the operating system is configured to send a data file of the one or more data files using one or more datagrams, wherein each datagram of the one or more datagrams includes a header, the method further comprising:

in response to the invocation of the system call interface, the operating system preparing the header for each datagram of the one or more datagrams without the application generating content for the header.

12. The method as recited in claim 10, further comprising:

the operating system storing at least one data file of the one or more data files in a kernel cache; and

the operating system sending the data file from the kernel cache to a second destination system in response to a second invocation of the system call interface by the application.

13. The method as recited in claim 10, wherein the invocation of the system call interface includes a parameter specifying at least one of:

a data file of the one or more data files, a communication endpoint, a starting offset within the data file, a packet size, and an amount of data of the data file to be sent to the another system.

14. The method as recited in claim 13, wherein the communication endpoint is a socket.

15. The method as recited in claim 10, wherein the invocation of the system call interface includes a parameter specifying a collection of one or more file specifications, wherein each file specification of the one or more file specifications includes a field identifying a particular data file of the one or more data files.

16. The method as recited in claim 10, further comprising:

the application creating a communication endpoint;

the application associating the endpoint with the destination system;

the application opening the one or more data files; and

the application passing a parameter in invoking the system call interface, wherein the parameter specifies at least one of;

a data file of the one or more data files, the communication endpoint, a starting offset within the data file, a packet size, and an amount of data of the data file to be sent to the destination system.

17. A non-transitory, computer-readable medium comprising program instructions, wherein the instructions are executable to implement an operating system configured to:

provide a system call interface for sending one or more data files to a destination system over a network via a connectionless network protocol;

receive an invocation of the system call interface from an application;

in response to the invocation of the system call, send the one or more data files to the destination system over the network without the application copying contents of the one or more data files into an address space of the application.

18. The non-transitory, computer-readable medium as recited in claim 17, wherein the operating system is configured to send a data file of the one or more data files using one or more datagrams, wherein each datagram of the one or more datagrams includes a header, and wherein, in response to the invocation of the system call interface, the operating system is further configured to prepare the header for each datagram of the one or more datagrams without the application generating content for the header.

19. The non-transitory, computer-readable medium as recited in claim 17, wherein the invocation of the system call interface includes a parameter specifying at least one of:

a data file of the one or more data files, a communication endpoint, a starting offset within the data file, a packet size, and an amount of data of the data file to be sent to the another system.

20. The non-transitory, computer-readable medium as recited in claim 17, wherein the invocation of the system call interface includes a parameter specifying a collection of one or more file specifications, wherein each file specification of the one or more file specifications includes a field identifying a particular data file of the one or more data files.