Socket management device and socket management method

• US 8,024,445 B2
• Filed: 03/19/2009
• Issued: 09/20/2011
• Est. Priority Date: 03/28/2008
• Status: Expired due to Fees

• Current Assignee: Seiko Epson Corporation (Seiko Group)
• Original Assignee: Seiko Epson Corporation (Seiko Group)
• Inventors: Shima, Toshihiro, Kamijima, Kyoichi
• Primary Examiner(s): DUONG, OANH
• Application Number:
  US12/407,569
• Publication Number:
  US 20090248875A1
• Time in Patent Office: 915 Days
• Field of Search: 709/223, 709/224, 718/102, 718/104
• US Class Current: 709/223
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals

Abstract

In order to properly allocates a limited number of sockets to applications (202, 202, . . . ) in a computer system so as to improve the system network performance, an application management module (300) memorizes the total number of sockets which OS (100) can supply to the applications (202, 202, . . . ), and a target number of sockets for each application. When an application (202) wants to obtain a socket, the application management module (300) recalculates the target number of sockets which can be allocated to the application (202), using a predetermined scheduling algorithm (312), based on the number of sockets presently unallocated and the priority revel of the application (202), and notifies the recalculated target number to the application (202). The application (202) judges from the notified target number whether a socket can be obtained or not, and based on the judgment determines whether or not to actually obtain a socket from the OS (100).

Claims

1. A socket management device that manages a number of sockets allocated to each of one or more applications operating in a computer system, the socket management device comprising:

a computer memory;

a means for application management that stores a total socket count indicating a total number of sockets which can be allocated to all of the one or more applications, and a target socket count for each of the one or more applications indicating a target value for the number of sockets allocated to each of the one or more applications, wherein the means for application management is embedded in the computer memory;

a means for scheduling that recalculates, when a socket-count change request indicating a socket acquisition request or a socket release request is received from any of the one or more applications, the target socket count of a request-source application which has issued the socket-count change request, based on the received socket-count change request and based on the total socket count and the target socket count for each of the one or more applications, which are stored in the means for application management, and that updates the target socket count of the request-source application stored in the means for application management so as to have the recalculated target socket count; and

a means for response that generates a response to the socket-count change request based on the target socket count recalculated by the means for scheduling, and that notifies the response to the request-source application.

2. A socket management device according to claim 1, wherein:

the means for application management further stores a priority level of each of the one or more applications; and

the means for scheduling recalculates the target socket count of the request-source application based on the received socket-count change request, based on the total socket count and the target socket count for each of the one or more applications, which are stored in the means for application management, and based on the priority level of the request-source application, which is stored in the means for application management.

3. A socket management device according to claim 2, wherein the means for scheduling determines a socket-allocation-count ratio among the one or more applications based on the priority level of each of the one or more applications, stored in the means for application management, and determines the target socket count of the request-source application according to the determined socket-allocation-count ratio.

4. A socket management device according to either one of claims 1 to 3, wherein the means for scheduling controls a socket-allocation-count ratio among the one or more applications according to a remaining socket count which corresponds to a difference between the total socket count and a sum of the target socket counts of the one or more applications.

5. A socket management device according to claim 1, further comprising a means for socket acquisition that judges whether to allow the request-source application to obtain a socket, based on the target socket count of the request-source application recalculated by the means for scheduling, and that obtains, when the means for socket acquisition judges that the request-source application is allowed to obtain a socket, a new socket for the request-source application from an operating system of the computer system.

6. A socket management system, comprising:

one or more applications; and

a socket management device comprising;

a means for application management that stores a total socket count indicating a total number of sockets which can be allocated to all of the one or more applications, and a target socket count for each of the one or more applications indicating a target value for the number of sockets allocated to each of the one or more applications;

a means for scheduling that recalculates, when a socket-count change request indicating a socket acquisition request or a socket release request is received from any of the one or more applications, the target socket count of a request-source application which has issued the socket-count change request, based on the received socket-count change request and based on the total socket count and the target socket count for each of the one or more applications, which are stored in the means for application management, and that updates the target socket count of the request-source application stored in the means for application management so as to have the recalculated target socket count;

and a means for response that generates a response to the socket-count change request based on the target socket count recalculated by the means for scheduling, and that notifies the response to the request-source application,

wherein each of the one or more applications includes a first means for socket acquisition that judges whether socket acquisition has been allowed, based on the response notified from the socket management device, and that obtains a new socket from an operating system of the computer system when the first means for socket acquisition judges that socket acquisition has been allowed.

7. A socket management system according to claim 6, wherein the socket management device further comprises:

a second means for socket acquisition that judges whether to allow the request-source application to obtain a socket, based on the target socket count of the request-source application recalculated by the means for scheduling, and that obtains, when the second means for socket acquisition judges that the request-source application is allowed to obtain a socket, a new socket for the request-source application from an operating system of the computer system,

wherein each of the one or more applications uses a socket for the application, obtained by the socket management device.

8. A socket management method for managing a number of sockets allocated to each of one or more applications operating in a computer system, the socket management method comprising:

an application management step of storing a total socket count indicating a total number of sockets which can be allocated to all of the one or more applications, and a target socket count for each of the one or more applications indicating a target value for the number of sockets allocated to each of the one or more applications;

a scheduling step of recalculating, when a socket-count change request indicating a socket acquisition request or a socket release request is received from any of the one or more applications, the target socket count of a request-source application which has issued the socket-count change request, based on the received socket-count change request and based on the total socket count and the target socket count for each of the one or more applications, which are stored in the application management step, and of updating the target socket count of the request-source application stored in the application management step so as to have the recalculated target socket count; and

a response step of generating a response to the socket-count change request based on the target socket count recalculated in the scheduling step, and of notifying the response to the request-source application.

9. A computer-readable computer program recorded on a non-transitory computer-readable medium and causing a computer to execute a method for managing a number of sockets allocated to each of one or more applications operating in a computer system, the method comprising:

an application management step of storing a total socket count indicating a total number of sockets which can be allocated to all of the one or more applications, and a target socket count for each of the one or more applications indicating a target value for the number of sockets allocated to each of the one or more applications;

a scheduling step of recalculating, when a socket-count change request indicating a socket acquisition request or a socket release request is received from any of the one or more applications, the target socket count of a request-source application which has issued the socket-count change request, based on the received socket-count change request and based on the total socket count and the target socket count for each of the one or more applications, which are stored in the application management step, and of updating the target socket count of the request-source application stored in the application management step so as to have the recalculated target socket count; and

a response step of generating a response to the socket-count change request based on the target socket count recalculated in the scheduling step, and of notifying the response to the request-source application.