Techniques for remapping sessions for a multi-threaded application

• US 9,336,040 B2
• Filed: 09/15/2014
• Issued: 05/10/2016
• Est. Priority Date: 09/15/2014
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Dong, Yao Zu, Tian, Kun
• Primary Examiner(s): Nguyen, Phillip H
• Application Number:
  US14/486,270
• Publication Number:
  US 20160077857A1
• Time in Patent Office: 603 Days
• Field of Search: 718/1, 719/328, 719/329
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

Examples may include a remapping of sessions for a multi-threaded application that may be executed at a server or a client coupled to the server via a plurality of transmit control protocol (TCP) connections. Sessions may be remapped such that the multi-threaded application may expect to route sessions through a same TCP connection but the sessions are actually outputted via separate TCP connections.

Claims

1. An apparatus comprising:

circuitry at a server coupled to a client via a plurality of transport control protocol (TCP) connections, the server arranged to host a primary or a secondary virtual machine (VM) capable of separately executing a first application;

an intercept component for execution by the circuitry to intercept first and second socket application interface (API) calls made from the first application, the first and second socket APIs arranged to route respective first and second sessions for expected output through a same TCP connection from among the plurality of TCP connections, the first and second sessions generated by the first application responsive to a request received from a second application at the client;

an index component for execution by the circuitry to generate a session index using respective first and second identifier information for the first and second sessions; and

a remap component for execution by the circuitry to remap the first and second sessions for actual output through separate TCP connections from among the plurality of TCP connections such that the session index is capable of being used at the client to recombine the first and second sessions with the same TCP connection for delivery to the second application.

2. The apparatus of claim 1, comprising:

the intercept component to intercept the first and second socket APIs by substituting a dynamic link library of socket APIs used by the application to route sessions for expected output through the plurality of TCP connections to the client, the dynamic link library substituted with a TCP decouple link library; and

the remap component to remap the first and second sessions includes using the TCP decouple link library to cause the first and second sessions to be actually outputted to the client through the separate TCP connections.

3. The apparatus of claim 1, the intercept component to intercept the first and second socket APIs comprises the intercept component to emulate the first and second socket APIs based on one of a TCP connection setup with the client or a TCP data exchange with the client.

4. The apparatus of claim 3, comprising:

the intercept component to emulate the first and second socket APIs based on the TCP connection setup, the intercept component to create multiple operating system (OS) socket APIs for the first and second socket APIs and assign the multiple OS socket APIs to the separate TCP connections; and

the remap component to remap the first and second sessions to use the multiple OS socket APIs to cause the first and second session to be actually outputted to the client through the separate TCP connections.

5. The apparatus of claim 4, comprising:

the intercept component to remove the multiple OS socket APIs for the first and second socket APIs responsive to an end of file (EOF) message for a TCP tear down with the client.

6. The apparatus of claim 3, comprising:

the intercept component to emulate the first and second socket APIs based on the TCP data exchange and use the session index to address a fixed mapping table that maps the first and second sessions to multiple operating system (OS) socket APIs assigned to the separate TCP connections; and

the remap component to remap the first and second sessions based on the fixed mapping table to cause the first and second sessions to be actually outputted to the client through the separate TCP connections.

7. The apparatus of claim 1, the intercept component to intercept the first and second socket APIs based on the application being selectively chosen for interception while another application capable of being executed by the primary or the secondary VM is not chosen for interception.

8. The apparatus of claim 1, the first and second identifier information comprises a first thread name or identifier assigned to a first thread used to generate the first session and a second thread name or identifier assigned to a second thread used to generate the second session.

9. The apparatus of claim 1, the first and second identifier information comprises a first protocol stack pattern including a first internet protocol (IP) address associated with generation of the first session and a second protocol stack pattern including a second IP address associated with generation of the second session.

10. The apparatus of claim 1, comprising a digital display coupled to the circuitry to present a user interface view.

11. At least one non-transitory machine readable medium comprising a plurality of instructions that in response to being executed by a system at a server arranged to host a primary or a secondary virtual machine (VM) capable of separately executing a first application, the instructions to cause the system to:

receive first and second sessions via separate transport control protocol (TCP) connections with a client, the first and second sessions generated by a second application at the client responsive to a request previously sent to the second application from the first application;

receive a session index having identifier information for the first and second sessions;

regroup the first and second sessions to a same TCP connection based on the session index; and

forward the first and second sessions via the same TCP connection to respective first and second socket application interfaces (APIs) for the first application.

12. The at least one non-transitory machine readable medium of claim 11, the identifier information comprises a first thread name or identifier assigned to a first thread used to generate the first session for the first application and a second thread name or identifier assigned to a second thread used to generate the second session for the first application.

13. The at least one non-transitory machine readable medium of claim 11, the identifier information comprises a first protocol stack pattern including a first internet protocol (IP) address associated with generation of the first session, and a second protocol stack pattern including a second IP address associated with generation of the second session.

14. The at least one non-transitory machine readable medium of claim 11, the instructions to further cause the system to regroup the first and second sessions to the same TCP connection using a same round-robin policy as used at the server to remap the first and second sessions from the same TCP connection at the server to the separate TCP connections.

15. A method comprising:

receiving, at circuitry for a client coupled to a server via a plurality of transport control protocol (TCP) connections, first and second sessions via separate TCP connections from among the plurality of TCP connections, the first and second sessions generated by a first application executed by a primary or a secondary virtual machine hosted by the server and outputted from the server via the separate TCP connections, the first and second sessions generated responsive to a request previously sent to the first application by a second application at the client;

receiving a session index having identifier information for the first and second sessions;

regrouping the first and second session to a same TCP connection from among the plurality of TCP connections based on the session index; and

forwarding the first and second sessions via the same TCP connection to respective first and second socket application interfaces (APIs) for the second application.

16. The method of claim 15, the identifier information comprises a first thread name or identifier assigned to a first thread used to generate the first session for the first application and a second thread name or identifier assigned to a second thread used to generate the second session for the first application.

17. The method of claim 15, the identifier information comprises a first protocol stack pattern including a first internet protocol (IP) address associated with generation of the first session, and a second protocol stack pattern including a second IP address associated with generation of the second session.

18. The method of claim 15, regrouping the first and second session sessions to the same TCP connection comprises using a same round-robin policy as used at the server to remap the first and second sessions from the same TCP connection at the server to the separate TCP connections.

19. At least one non-transitory machine readable medium comprising a plurality of instructions that in response to being executed by a system at a client coupled to a server via a plurality of transport control protocol (TCP) connections, the server arranged to host a primary or a secondary virtual machine (VM) capable of separately executing a first application, the instructions to cause the system to:

receive first and second sessions via separate TCP connections from among the plurality of TCP connections, the first and second session generated by the first application and outputted from the server via the separate TCP connections, the first and second sessions generated responsive to a request previously sent to the first application by a second application at the client;

receive a session index having identifier information for the first and second sessions;

regroup the first and second session to a same TCP connection from among the plurality of TCP connections based on the session index; and

forward the first and second sessions via the same TCP connection to respective first and second socket application interfaces (APIs) for the second application.

20. The at least one non-transitory machine readable medium of claim 19, the identifier information comprises a first thread name or identifier assigned to a first thread used to generate the first session for the first application and a second thread name or identifier assigned to a second thread used to generate the second session for the first application.

21. The at least one non-transitory machine readable medium of claim 19, the first and second identifier information comprises a first protocol stack pattern including a first a first internet protocol (IP) address associated with generation of the first session and a second protocol stack pattern including a second IP address associated with generation of the second session.

22. The at least one non-transitory machine readable medium of claim 19, the first and second session sessions regrouped to the same TCP connection comprises using a same round-robin policy as used at the server to remap the first and second sessions from the same TCP connection at the server to the separate TCP connections.