Energy Efficient Implementation Of Read-Copy Update For Light Workloads Running On Systems With Many Processors

• US 20130061071A1
• Filed: 09/03/2011
• Published: 03/07/2013
• Est. Priority Date: 09/03/2011
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: McKenney, Paul E.
• Application Number:
  US13/225,425
• Publication Number:
  US 20130061071A1
• Time in Patent Office: Days
• US Class Current: 713/320
• CPC Class Codes: G06F 1/3206 Monitoring of events, devices or parameters that trigger a change in power modality

Abstract

A technique for determining if a processor in a multiprocessor system implementing a read-copy update (RCU) subsystem may be placed in low power state. The technique may include determining whether the processor has any RCU callbacks that are ready for invocation or the RCU subsystem requires grace period advancement processing from the processor. The processor may be placed in a low power state if either (1) a first condition holds wherein the processor has one or more pending RCU callbacks, but does not have any RCU callbacks that are ready for invocation and the RCU subsystem does not require grace period advancement processing from the processor, (2) a second condition holds wherein the processor does not have any pending RCU callbacks.

Claims

1. In a multiprocessor computing 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 low power state, comprising:

determining whether said processor has any RCU callbacks that are ready for invocation or said RCU subsystem requires grace period advancement processing from said processor; and

placing said processor in a low power state if either;

a first condition holds wherein said processor has one or more pending RCU callbacks, but does not have any RCU callbacks that are ready for invocation and said RCU subsystem does not require grace period advancement processing from said processor;

or

a second condition holds wherein said processor does not have any pending RCU callbacks.

2. The method of claim 1, further including setting a callback flag when placing said processor in a low power state when said first condition holds in order to note that said processor has one or more pending RCU callbacks.

3. The method of claim 2, further including performing callback flush loop processing to invoke or advance RCU callbacks if a third condition holds wherein said processor has one or more pending RCU callbacks, and such callbacks are ready for invocation or said RCU subsystem requires grace period advancement processing from said processor.

4. The method of claim 3, further including clearing said callback flag if it has been set for said processor and if said callback flush loop processing is performed and said processor has no more callbacks.

5. The method of claim 4, further including checking at the end of an RCU grace period whether other processors are in a low power state and have said callback flag set, and if so, waking said other processors from their low power state so that their callbacks may be processed.

6. The method of claim 1, wherein said method is performed for each processor in said system when attempting to place said processors in a low power state.

7. The method of claim 3, wherein said callback flush loop processing is repeated for a predetermined loop count or until said first condition or said second condition is reached.

8. A multiprocessor system, comprising:

two or more processors;

a memory coupled to said processors, said memory including a 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 low power state, said operations comprising;

determining whether said processor has any RCU callbacks that are ready for invocation or said RCU subsystem requires grace period advancement processing from said processor; and

placing said processor in a low power state if either;

a first condition holds wherein said processor has one or more pending RCU callbacks, but does not have any RCU callbacks that are ready for invocation and said RCU subsystem does not require grace period advancement processing from said processor;

or

a second condition holds wherein said processor does not have any pending RCU callbacks.

9. The system of claim 8, wherein said operations further include setting a callback flag when placing said processor in a low power state when said first condition holds in order to note that said processor has one or more pending RCU callbacks.

10. The system of claim 9, further including performing callback flush loop processing to invoke or advance RCU callbacks if a third condition holds wherein said processor has one or more pending RCU callbacks, and such callbacks are ready for invocation or said RCU subsystem requires grace period advancement processing from said processor.

11. The system of claim 10, wherein said operations further include clearing said callback flag if it has been set for said processor if said callback flush loop processing is performed and said processor has no more callbacks.

12. The system of claim 11, wherein said operations further include checking at the end of an RCU grace period whether other processors are in a low power state and have said callback flag set, and if so, waking said other processors from their low power state so that their callbacks may be processed.

13. The system of claim 8, wherein said operations are performed for each processor in said system when attempting to place said processors in a low power state.

14. The system of claim 10, wherein said callback flush loop processing is repeated for a predetermined loop count or until said first condition or said second condition is reached.

15. A computer program product, comprising:

one or more machine-useable storage media;

program instructions provided by said one or more 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 low power state, said operations comprising;

determining whether said processor has any RCU callbacks that are ready for invocation or said RCU subsystem requires grace period advancement processing from said processor; and

placing said processor in a low power state if either;

a first condition holds wherein said processor has one or more pending RCU callbacks, but does not have any RCU callbacks that are ready for invocation and said RCU subsystem does not require grace period advancement processing from said processor;

or

a second condition holds wherein said RCU subsystem does require grace period advancement processing from said processor, but said processor does not have any pending RCU callbacks.

16. The computer program product of claim 15, wherein said operations further include setting a callback flag when placing said processor in a low power state when said first condition holds in order to note that said processor has one or more pending RCU callbacks.

17. The computer program product of claim 16, further including performing callback flush loop processing to invoke or advance RCU callbacks if a third condition holds wherein said processor has one or more pending RCU callbacks, and such callbacks are ready for invocation or said RCU subsystem requires grace period advancement processing from said processor.

18. The computer program product of claim 17, wherein said operations further include clearing said callback flag if it has been set for said processor and if said callback flush loop processing is performed and said processor has no more callbacks.

19. The computer program product of claim 18, wherein said operations further include checking at the end of an RCU grace period whether other processors are in a low power state and have said callback flag set, and if so, waking said other processors from their low power state so that their callbacks may be processed.

20. The computer program product of claim 15, wherein said operations are performed for each processor in said system when attempting to place said processors in a low power state.

21. The computer program product of claim 17, wherein said callback flush loop processing is repeated for a predetermined loop count or until said first condition or said second condition is reached.