UTILITY FUNCTION EXECUTION USING SCOUT THREADS

• US 20080141268A1
• Filed: 12/12/2006
• Published: 06/12/2008
• Est. Priority Date: 12/12/2006
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Song, Yonghong, Tirumalai, Partha P., Kalogeropulos, Spiros
• Application Number:
  US11/609,682
• Publication Number:
  US 20080141268A1
• Time in Patent Office: Days
• US Class Current: 718/107
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

Abstract

A method and mechanism for using threads in a computing system. A multithreaded computing system is configured to execute a first thread and a second thread. The first and second threads are configured to operate in a producer-consumer relationship. The second thread is configured to execute utility type functions in advance of the first thread reaching the functions in the program code. The second thread executes in parallel with the first thread and produces results from the execution which are made available for consumption by the first thread. Analysis of the program code is performed to identify such utility functions and modify the program code to support execution of the functions by the second thread.

Claims

1. A method for using threads in executable code, the method comprising:

concurrently executing a first thread and a second thread;

the second thread producing results by executing a function in a program sequence prior to the first thread reaching a point in the program sequence which includes the function; and

the first thread reaching said point in the program sequence, and consuming said results in lieu of executing said function.

2. The method as recited in claim 1, further comprising the first thread executing said function, in response to determining valid results corresponding to said function are not available.

3. The method as recited in claim 1, further comprising the second thread storing said results in a memory location shared by both the first thread and the second thread.

4. The method as recited in claim 1, further comprising analyzing said executable code and modifying the executable code to include an indication that said function is to be executed by the second thread.

5. The method as recited in claim 4, further comprising modifying said executable code to add instructions which create the second thread.

6. The method as recited in claim 1, wherein the function comprises a utility type function.

7. The method as recited in claim 6, wherein said utility type function is in a critical path of the program sequence.

8. A multithreaded multicore processor comprising:

a memory; and

a plurality of processing cores, wherein a first core of said cores is configured to execute a first thread, and a second core of said cores is configured to execute a second thread, wherein the first thread and second thread are concurrently executable;

wherein the second thread is configured to produce results by executing a function in a program sequence prior to the first thread reaching a point in the program sequence which includes the function; and

wherein the first thread is configured to consume said results in lieu of executing said function, in response to reaching said point in the program sequence.

9. The processor as recited in claim 8, wherein the first thread is further configured to execute said function, in response to determining valid results corresponding to said function are not available.

10. The processor as recited in claim 8, wherein the second thread is further configured to store said results in a memory location of the memory shared by both the first thread and the second thread.

11. The processor as recited in claim 8, wherein the second thread is configured to execute a duplicate of said function.

12. The processor as recited in claim 8, wherein the function comprises a utility type function.

13. The processor as recited in claim 12, wherein said utility type function is in a critical path of the program sequence.

14. A computer readable medium comprising program instructions, said program instructions being operable to cause:

concurrent execution of a first thread and a second thread;

the second thread to produce results by executing a function in a program sequence prior to the first thread reaching a point in the program sequence which includes the function; and

the first thread to consume said results in lieu of executing said function, in response to reaching said point in the program sequence.

15. The medium as recited in claim 14, wherein said program instructions are further operable to cause the first thread to execute said function, in response to determining valid results corresponding to said function are not available.

16. The medium as recited in claim 14, wherein said program instructions are further operable to cause the second thread to store said results in a memory location shared by both the first thread and the second thread.

17. The medium as recited in claim 14, wherein said program instructions are further operable to analyze said executable code and modify the executable code to include an indication that said function is to be executed by the second thread.

18. The medium as recited in claim 17, wherein said program instructions are further operable to modify said executable code to add instructions which create the second thread.

19. The medium as recited in claim 14, wherein the function comprises a utility type function.

20. The medium as recited in claim 19, wherein said utility type function is in a critical path of the program sequence.