Energy efficient implementation of read-copy update for light workloads running on systems with many processors

• US 8,938,631 B2
• Filed: 06/30/2012
• Issued: 01/20/2015
• Est. Priority Date: 06/30/2012
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: McKenney, Paul E.
• Primary Examiner(s): TRAN, VINCENT HUY
• Application Number:
  US13/539,363
• Publication Number:
  US 20140006820A1
• Time in Patent Office: 934 Days
• Field of Search: 713/320, 711/147, 712/28
• US Class Current: 713/320
• CPC Class Codes: G06F 1/3206 Monitoring of events, devices or parameters that trigger a change in power modality
• CPC Class Codes: G06F 1/3287 by switching off individual functional units in the computer system
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A technique for determining if a processor in a multiprocessor system implementing a read-copy update (RCU) subsystem may be placed in a low power state. The technique may include performing a first predictive query of the RCU subsystem to request permission for the processor to enter the low power state. If permission is denied, the processor is not placed in the low power state. If permission is granted, the processor is placed in the low power state for a non-fixed duration. Regardless whether permission is denied or granted, a second confirming query of the RCU subsystem is performed to redetermined whether it is permissible for the processor to be in the low power state.

Claims

1. In a multiprocessor computer system having two or more processors operatively coupled to one or more memory devices and implementing a read-copy update (RCU) subsystem, a method for determining if a processor may be placed in a low power state, comprising:

performing a first predictive query of said RCU subsystem to request permission for one of said processors to enter said low power state;

if said permission is denied, refraining from placing said processor in said low power state;

if said permission is granted, placing said processor in said low power state for a non-fixed duration; and

regardless whether said permission is denied or granted, performing a second confirming query of said RCU subsystem to redetermine whether it is permissible for said processor to be in said low power state.

2. The method of claim 1, wherein said permission is granted if said processor has no pending RCU callbacks or is not in a holdoff period following a previous invocation of said second confirming query, and wherein said permission is denied only if said holdoff period is in effect.

3. The method of claim 2, wherein said second confirming query includes:

maintaining said processor in its current power state if said processor has no pending RCU callbacks;

maintaining said processor in its current power state if said processor has pending RCU callbacks and said holdoff period remains in effect;

maintaining said processor in its current power state if said processor has pending RCU callbacks but they are not ready for invocation, if said holdoff period is not in effect, and if said processor has no other RCU work to perform, and further setting a low power state time limit, such that if said processor is in said non-fixed duration low power state, said low power state becomes a fixed-duration low power state; and

performing callback flush loop processing if said holdoff period is not in effect and if said processor has pending RCU callbacks that are ready for invocation or has other RCU work to perform.

4. The method of claim 3, wherein said low power time limit is set using a programmed timer.

5. The method of claim 4, wherein said timer is set to a first timer value if there are non-lazy RCU callbacks and a second timer value that is longer than said first timer value if only lazy RCU callbacks are present.

6. The method of claim 1, further including said RCU subsystem processing an unlimited number RCU callbacks in a single invocation if said processor has no other work to perform.

7. The method of claim 6, wherein said processor is determined to have no other work to perform if it is in an idle state with no pending scheduling change and no other immediate processing that needs to be performed by said processor.

8. A multiprocessor system, comprising:

two or more processors;

a memory coupled to said processors, said memory including a non-transitory computer useable medium tangibly embodying at least one program of instructions executable by said processors to implement a read-copy update (RCU) subsystem and to perform operations for determining if a processor may be placed in a low power state, said operations comprising;

performing a first predictive query of said RCU subsystem to request permission for one of said processors to enter said low power state;

if said permission is denied, refraining from placing said processor in said low power state;

if said permission is granted, placing said processor in said low power state for a non-fixed duration; and

regardless whether said permission is denied or granted, performing a second confirming query of said RCU subsystem to redetermine whether it is permissible for said processor to be in said low power state.

9. The system of claim 8, wherein said permission is granted if said processor has no pending RCU callbacks or is not in a holdoff period following a previous invocation of said second confirming query, and wherein said permission is denied only if said holdoff period is in effect.

10. The system of claim 9, wherein said processing that attempts to place said processor in said low power state includes:

maintaining said processor in its current power state if said processor has no pending RCU callbacks;

maintaining said processor in its current power state if said processor has pending RCU callbacks and said holdoff period remains in effect;

maintaining said processor in its current power state power state if said processor has pending RCU callbacks but they are not ready for invocation, if said holdoff period is not in effect, and if said processor has no other RCU work to perform, and further setting a low power state time limit, such that if said processor is in said non-fixed duration low power state, said low power state becomes a fixed-duration low power state; and

performing callback flush loop processing if said holdoff period is not in effect and if said processor has pending RCU callbacks that are ready for invocation or has other RCU work to perform.

11. The system of claim 10 wherein said low power time limit is set using a programmed timer.

12. The system of claim 11, wherein said timer is set to a first timer value if there are non-lazy RCU callbacks and a second timer value that is longer than said first timer value if only lazy RCU callbacks are present.

13. The system of claim 8, further including said RCU subsystem processing an unlimited number RCU callbacks in a single invocation if said processor has no other work to perform.

14. The system of claim 13, wherein said processor is determined to have no other work to perform if it is in an idle state with no pending scheduling change and no other immediate processing that needs to be performed by said processor.

15. A computer program product, comprising:

one or more non-transitory machine-useable storage media;

program instructions provided by said one or more non-transitory machine-useable storage media for programming a multiprocessor data processing platform to implement a read-copy update (RCU) subsystem and to perform operations for determining if a processor may be placed in a low power state, said operations comprising;

performing a first predictive query of said RCU subsystem to request permission for one of said processors to enter said low power state;

if said permission is denied, refraining from placing said processor in said low power state;

if said permission is granted, placing said processor in said low power state for a non-fixed duration; and

regardless whether said permission is denied or granted, performing a second confirming query of said RCU subsystem to redetermine whether it is permissible for said processor to be in said low power state.

16. The computer program product of claim 15, wherein said permission is granted if said processor has no pending RCU callbacks or is not in a holdoff period following a previous invocation of said second confirming query, and wherein said permission is denied only if said holdoff period is in effect.

17. The computer program product of claim 16, wherein said processing that attempts to place said processor in said low power state includes:

maintaining said processor in its current power state if said processor has no pending RCU callbacks;

maintaining said processor in its current power state if said processor has pending RCU callbacks and said holdoff period remains in effect;

maintaining said processor in its current power state if said processor has pending RCU callbacks but they are not ready for invocation, if said holdoff period is not in effect, and if said processor has no other RCU work to perform, and further setting a low power state time limit, such that if said processor is in said non-fixed duration low power state, said low power state becomes a fixed-duration low power state; and

performing callback flush loop processing if said holdoff period is not in effect and if said processor has pending RCU callbacks that are ready for invocation or has other RCU work to perform.

18. The computer program product of claim 17 wherein said low power time limit is set using a programmed timer.

19. The computer program product of claim 18, wherein said timer is set to a first timer value if there are non-lazy RCU callbacks and a second timer value that is longer than said first timer value if only lazy RCU callbacks are present.

20. The computer program product of claim 15, further including said RCU subsystem processing an unlimited number RCU callbacks in a single invocation if said processor has no other work to perform.

21. The computer program product of claim 20, wherein said processor is determined to have no other work to perform if it is in an idle state with no pending scheduling change and no other immediate processing that needs to be performed by said processor.