System, method, and computer program product for conditionally sending a request for data to a node based on a determination

• US 9,465,739 B2
• Filed: 10/17/2013
• Issued: 10/11/2016
• Est. Priority Date: 09/30/2009
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Garg, Gaurav, Hass, David T.
• Primary Examiner(s): ELMORE, STEPHEN C
• Application Number:
  US14/056,118
• Publication Number:
  US 20140040564A1
• Time in Patent Office: 1,090 Days
• Field of Search: 711/141, 711/121, 711/130, 711/144, 711/146, 711/147, 711/156
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0815 Cache consistency protocols
• CPC Class Codes: G06F 12/0831 using a bus scheme, e.g. with bus monitoring or watching means

Abstract

A system, method, and computer program product are provided for conditionally sending a request for data to a node based on a determination. In operation, a first request for data is sent to a cache of a first node. Additionally, it is determined whether the first request can be satisfied within the first node, where the determining includes at least one of determining a type of the first request and determining a state of the data in the cache. Furthermore, a second request for the data is conditionally sent to a second node, based on the determination.

Claims

1. A method, comprising:

sending a request for data to a cache of a first node;

receiving a response from the cache of the first node, wherein the response includes information relating to a state of the data;

determining a type of the request for the data based on the state of the data, the type comprising read or write;

fulfilling the request for the data at the first node based on the state of the data when the type is the read; and

sending the request for the data to a second node when the type is the write.

2. The method of claim 1, further comprising determining whether the data is valid based on the state of the data.

3. The method of claim 2, wherein the sending further comprises sending the request for the data to the second node after determining the data is not valid.

4. The method of claim 1, wherein the information relating to the state of the data includes information about whether the data is locally shared or globally shared.

5. The method of claim 4, wherein the fulfilling the data request comprises fulfilling the data request at the first node when the data is locally shared, and

wherein the sending the request for the data to the second node comprises sending the request for the data to the second node when the data is globally shared.

6. The method of claim 1, further comprising determining whether the data is valid or invalid.

7. The method of claim 6, wherein the determining the type further comprises sending a second request to a second cache of the first node when the data is invalid.

8. The method of claim 1, further comprising:

determining whether the data is locally shared or globally shared.

9. The method of claim 8, wherein the sending the request for the data to the second node comprises:

sending the request for the data to the second node when the type is the write and the data is globally shared.

10. The method of claim 8, further comprising:

fulfilling the request for the data based on the state of the data when the type is the write and the data is locally shared.

11. A first node in a multiprocessor system, comprising:

a cache; and

a controller configured to;

send a request for data to the cache;

receive a response from the cache, wherein the response includes information relating to a state of the data;

determine a type of the request for the data based on the state of the data, the type comprising read or write;

fulfill the request for the data based on the state of the data when the type is the read; and

send the request for the data to a second node when the type is the write.

12. The first node of claim 11, wherein the controller is further configured to determine whether the data is valid based on the state of the data.

13. The first node of claim 12, wherein the controller is configured to send the request for the data to the second node after determining the data in the cache is not valid.

14. The first node of claim 11 wherein the information relating to the state of the data includes information about whether the data is locally shared or globally shared.

15. The first node of claim 11, wherein the controller is configured to fulfill the request for the data when the data is locally shared, and

wherein the controller is configured to send the request for the data to the second node when the data is globally shared.

16. The first node of claim 11, wherein the controller is further configured to determine whether the data is valid or invalid.

17. The first node of claim 16, further comprising:

a second cache, and

wherein the controller is further configured to send a second request to the second cache when the data is invalid.

18. The first node of claim 11, wherein the controller is further configured to determine whether the data is locally shared or globally shared.

19. The first node of claim 18, wherein the controller is configured to send the request for the data to the second node when the type is the write and the data is globally shared.

20. The first node of claim 18, wherein the controller is further configured to fulfill the request for the data based on the state of the data when the type is the write and the data is locally shared.