WO2021056416A1

WO2021056416A1 - Power management method and apparatus

Info

Publication number: WO2021056416A1
Application number: PCT/CN2019/108555
Authority: WO
Inventors: Jun Song; Xiaolin Meng; Lin Cheng; Youquan FENG; Yijun Lu; Hao Zhu; Zhibing Li; Lingfang HE; Guan Wang
Original assignee: Alibaba Group Holding Limited
Priority date: 2019-09-27
Filing date: 2019-09-27
Publication date: 2021-04-01
Also published as: CN114402272B; CN114402272A

Abstract

Methods and apparatus are provided for improving power management. A power management component receives a power capping command. The power capping command includes a power capping target for a computing system. The power management component determines whether a power consumption of the computing system satisfies the power capping target when performing the power capping in one of a first power capping mode and a second power capping mode. The power management component performs the power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode.

Description

POWER MANAGEMENT METHOD AND APPARATUS

TECHNICAL FIELD

The present disclosure relates to the field of power management and, more particularly, to methods and apparatuses for coordinating different power capping modes.

BACKGROUND

Power capping is a widely used technology in modern Data Centers (DCs) to increase on-rack compute density and avoid power outage. Hardware (e.g. chip, server) vendors such as Original Design Manufacturer (ODM) and Original Equipment Manufacturer (OEM) ) and software (e.g. Operating System (OS) , virtualization hypervisor) vendors provide basic power capping capabilities.

However, the vendors do not put together the power capping functional blocks into a solution in which different power capping modes can be coordinated to achieve a power capping target.

SUMMARY

This summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in limiting the scope of the claimed subject matter.

The following describes example implementations of power management. In implementations, a power management component receives a power capping command. The power capping command includes a power capping target for a computing system. The power management component determines whether a power consumption of the computing system satisfies the power capping target when performing the power capping in one of a first power capping mode and a second power capping mode. The power management component performs the power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode. The first power capping mode is an Out-of-Band (OOB) power capping mode, and the second power capping mode is an In-Band (IB) power capping mode.

Thus, the OOB power capping mode and the IB power capping mode are coordinated and combined to achieve the power capping target of the computing system. Therefore, power capping is more reliable and available.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit (s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.

FIG. 1 illustrates an example block diagram of a computing system.

FIG. 2 illustrates an example flowchart of a process for coordinating different power capping modes.

FIGs. 3A, 3B, and 3C illustrate an example flowchart of a process for coordinating different power capping modes in details.

FIG. 4 illustrates an example apparatus for implementing the processes and methods described above.

DETAILED DESCRIPTION

Terminologies as used herein are denoted as follows.

Out-of-Band (OOB) refers to a method to access a computing system without using the operating system (OS) of the computing system.

In-Band (IB) refers to a method to access a computing system via the OS of the computing system.

Management Engine (ME) refers to a logic typically residing in an off-CPU bridge chip on Intel platforms.

Node Manager (NM) refers to a piece of firmware or state machine in ME, responsible for power management of the computing system.

Telemetry Hub refers to a piece of firmware or state machine in ME, responsible for collecting performance telemetries from processors.

Rest of Platform (RoP) refers to other compute components except major parts like CPUs, GPUs, Platform Controller Hub (PCH) , fans, Power Supply Unit (PSU) .

Power capping refers to a method to limit the power consumption of the computing system not to exceed a power limit/cap.

Board Management Controller (BMC) refers to a small embedded co-processor working as an Intelligent Platform Management Interface (IPMI) bus master to perform system-level power management, monitoring, logging, alarming, etc.

FIG. 1 illustrates an example block diagram of a computing system 100. The computing system may be implemented in a large-scale distributed computing environment.

Referring to FIG. 1, the computing system 100 includes RoP 102, storage 104, network 106, fans 108, Graphics Processing Unit (GPU) /Field Programmable Gate Array (FPGA) 110, Double Data Rate Synchronous Dynamic Random-Access Memory (DDR SDRAM) 112, Central Processing Unit (CPU) 114, Chipsets 116, BMC 118, ME 120, power capping pcode/ucode 122, power management component 124, and authentication 126. The computing system 100 is configured to get/set commands from a power capping master (not shown) . In implementations, the power capping master can be a controller, a console, etc. which communicates with the computing system 100.

The power management component 124 includes 3 parts, i.e., part A 128, part B 130, and part C 132. Part A 128 is an OOB power capping sub-agent. Part B 130 is a coordinator. Part C 132 is an IB power capping sub-agent. In implementations, the power management component 124 can be implemented with software, hardware, firmware, or any combination thereof.

The power management component 124 is configured to perform different power capping modes, for example, IB power capping mode and OOB power capping mode. In the IB power capping mode, the power management component 124 is configured to run (as a service) or be ready to run on an OS of the computing system 100 to respond to management commands. In the OOB power capping mode, the power management component 124 is configured to use a management port to access a Node Manager (not shown) in the ME 120. In that case, the power management component 124 does not run on the OS of the computing system 100.

The power management component 124 is further configured to communicate with the BMC 118 via a network interface to receive power management commands and send responses. The power management component 124 is further configured to access Mode Specific Register (MSR) to read/write power capping pcode/ucode 122. The power management component 124 is further configured to communicate with the authentication 128.

The OOB power capping sub-agent 128 is configured to perform power capping in the OOB power capping mode.

The IB power capping sub-agent 132 is configured to perform power capping in the IB power capping mode.

The coordinator 130 is configured to coordinate/dispatch power capping tasks to the OOB power capping sub-agent 128 and/or the IB power capping sub-agent 132. The coordinator 130 is further configured to, upon receiving a power capping command, calculate an OOB success rate R _OOB%and an IB success rate R _OOB%in a period (e.g., a most recent period) and dispatch the power capping task to either the OOB power capping sub-agent 128 or the IB power capping sub-agent 132, or both to achieve the power capping target.

In implementations, the OOB success rate may be calculated as follows. In a period T, when the OOB power capping mode is performed on the computing system, a total number of attempts of power capping is N, and the number of attempts where the power consumption of the computing system satisfies the power capping target is n. The OOB success rate R _OOB%is =n/N*100%.

In implementations, the IB success rate may be calculated as follows. In a period T, when the IB power capping mode is performed on the computing system, a total number of attempts of power capping is N, and the number of attempts where the power consumption of the computing system satisfies the power capping target is n. The IB success rate R _IB%is = n/N*100%.

In implementations, either the IB power capping mode or the OOB power capping mode could be delayed or even denied when the traffic and/or load are high. For example, in a heavily used computer, the CPU utilization is 100%, the memory bandwidth utilization is 80%+, the storage queues are 100%+full, and the network bandwidth utilization is 80%+. In the OOB power capping mode, the power management component needs to go through IPMI protocol on the Power Management Bus (PMBus) (not shown) with the help of BMC which is an embedded on-board co-processor. When there are a large number of hardware errors, the BMC needs to process high-priority activities such as logging and alarming, but may ignore, defer or reject medium-priority activities such as power capping commands. A similar situation may occur in the IB power capping mode. When the utilization at the computing system is high, there is a chance that the IB access is seriously delayed or even suspended.

Different dimensions of cloud service, such as availability, latency, reliability, throughput, etc., can be regulated based on the Service Level Agreement (SLA) between the service provider and the customer. Usually, the cloud service needs to provide availability as high as 99.99%or even better. The software and application may use distributed and/or redundant design to achieve such level of availability over unreliable infrastructure. The practice of hyper-scale cloud service provides a server deployment with increased density, which significantly raises the outage risk. The service provider may set a power buffer large enough to prevent the outage risk. Additionally, power capping is performed to control the power consumption to reduce the outage risk. During power capping, the desired availability can be lower, for example, 99.9%. In implementations, the availability under the OOB power capping mode may be around 95%, which may vary under different conditions, but is far below the desired availability of 99.9%.

In implementations, the IB power capping mode and the OOB power capping mode may be coordinated and combined to achieve the power capping target of the computing system. Moreover, the availability of cloud service under power capping may be improved.

FIG. 2 illustrates an example flowchart of a process 200 for coordinating different power capping modes.

At block 202, a power management component receives a power capping command. The power capping command includes a power capping target for a computing system. The power capping target may be set and/or adjusted dynamically based on actual needs.

At block 204, the power management component determines whether a power consumption of the computing system satisfies the power capping target when performing power capping in one of a first power capping mode and a second power capping mode.

In implementations, the power management component determines whether a first success rate of the first power capping mode is greater than a first nominal success rate. The power management component performs the power capping in the first power capping mode in response to determining that the first success rate of the first power capping mode is greater than the first nominal success rate. The first success rate may be calculated as follows. In a period T, when the first power capping mode is performed on the computing system, a total number of attempts of power capping is N, and the number of attempts where the power consumption of the computing system satisfies the power capping target is n. The first success rate is n /N *100%. The first nominal success rate may be determined by, but not limited to, the specification, historical data, statistical data, test data, simulation data, empirical data, etc. The power management component waiting until a first effective delay expires. The first effective delay is a period for the first power capping mode to take effect after the first power capping mode is enforced/performed. The first effective delay may be set and/or adjusted dynamically based on actual needs. The power management component determines whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the first power capping mode.

In implementations, the power management component determines whether a second success rate of the second power capping mode is greater than a second nominal success rate. The second success rate may be calculated as follows. In a period T, when the second power capping mode is performed on the computing system, a total number of attempts of power capping is N, and the number of attempts where the power consumption of the computing system satisfies the power capping target is n. The second success rate is n/N*100%. The second nominal success rate may be determined by, but not limited to, the specification, historical data, statistical data, test data, simulation data, empirical data, etc. The power management component performs the power capping in the second power capping mode in response to determining that the second success rate of the second power capping mode is greater than the second nominal success rate. The power management component waits until a second effective delay expires. The second effective delay is a period for the second power capping mode to take effect after the second power capping mode is enforced/performed. The second effective delay may be set and/or adjusted dynamically based on actual needs. The power management component determines whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the second power capping mode.

In implementations, the first power capping mode is an OOB power capping mode, and the second power capping mode is an IB power capping mode.

At block 206, the power management component performs the power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode. For example, the power capping may be performed in the first power capping mode and the second power capping mode simultaneously.

In implementations, the power management component waits until both the first effective delay and the second effective delay expire, and determines whether the power consumption of the computing system satisfies the power capping target.

In implementations, the power management component monitors whether conflict occurs and stops performing the power capping in one of the first power capping mode and the second power capping mode in response to monitoring that the conflict occurs.

In implementations, the power management component checks whether the conflict occurs in a pcode/ucode setting.

With the above example process 200, the first power capping mode and the second power capping mode are coordinated and combined to achieve the power capping target of the computing system. Therefore, power management during power capping is improved.

FIGs. 3A, 3B, and 3C illustrate an example flowchart of a process 300 for coordinating different power capping modes in details.

At block 302, the coordinator receives a power capping command. The power capping command includes a power capping target for a computing system. The power capping target may be set and/or adjusted dynamically based on actual needs.

At block 304, the coordinator determines whether an OOB success rate R _OOB%is greater than a nominal OOB success rate R _OOB*%. The algorithm of the OOB success rate R _OOB%is as described above with reference to FIG. 1. The nominal OOB success rate R _OOB*%may be determined by, but not limited to, the specification, historical data, statistical data, test data, simulation data, empirical data, etc.

If the coordinator determines that the OOB success rate R _OOB%is greater than the nominal OOB success rate R _OOB*%at block 304, then at block 306, the coordinator instructs the OOB power capping sub-agent to perform power capping in the OOB power capping mode with the Node Manager.

If the coordinator determines that the OOB success rate R _OOB%is not greater than the nominal OOB success rate R _OOB*%at block 304, the process proceeds to block 316.

At block 308, the coordinator waits until an OOB effective delay T _OOB expires. The OOB effective delay T _OOB is a period for the OOB power capping mode to take effect after the OOB power capping mode is enforced/performed. The OOB effective delay T _OOB may be set and/or adjusted dynamically based on actual needs.

At block 310, the coordinator checks the power consumption P ₁ of the computing system.

At block 312, the coordinator determines whether the power consumption P ₁ of the computing system is less than or equal to the power capping target.

If the coordinator determines that the power consumption of the computing system P ₁ is less than or equal to the power capping target at block 312, the coordinator updates the OOB success rate R _OOB%at block 314.

If the coordinator determines that the power consumption P ₁ of the computing system is not less than or equal to the power capping target at block 312, the coordinator prepares initial values for the IB power capping mode at block 316. In implementations, the initial values include an IB success rate R _IB%and a nominal IB success rate R _IB*%.

At block 318, the process 300 is done.

As shown in FIG. 3B, the process 300 continues from block 316, and at block 320, the coordinator determines whether the IB success rate R _IB%is greater than the nominal IB success rate R _IB*%. The algorithm of the IB success rate R _IB%is as described above with reference to FIG. 1. The nominal IB success rate R _IB*%may be determined by, but not limited to, the specification, historical data, statistical data, test data, simulation data, empirical data, etc.

If the coordinator determines that the IB success rate R _IB%is greater than the nominal IB success rate R _IB*%at block 320, the coordinator instructs the IP power capping sub-agent to perform power capping in the IB power capping mode at block 322.

At block 324, the coordinator waits until an IB effective delay T _IB expires. The IB effective delay T _IB is a period for the IB power capping mode to take effect after the IB power capping mode is enforced/performed. The IB effective delay T _IB may be set and/or adjusted dynamically based on actual needs.

If the coordinator determines that the IB success rate R _IB%is not greater than the nominal IB success rate R _IB*%at block 320, then at block 326, the coordinator instructs the OOB power capping sub-agent to perform power capping in the OOB power capping mode with the Node Manager. Meanwhile, the coordinator also instructs the IP power capping sub-agent to perform power capping in the IB power capping mode. In implementations, the power management component performs the power capping in the IB power capping mode and the IB power capping mode simultaneously.

At block 328, the coordinator waits until both the OOB effective delay T _OOB and the IB effective delay T _IB expire.

After block 324 and block 328, the process 300 proceeds to block 330.

At block 330, the coordinator determines whether the power consumption P ₂ of the computing system is less than or equal to the power capping target.

If the coordinator determines that the power consumption P ₂ of the computing system is less than or equal to the power capping target at block 330, the coordinator updates the IB success rate R _OOB%at block 332.

If the coordinator determines that the power consumption P ₂ of the computing system is not less than or equal to the power capping target at block 330, the power capping is performed with additional power control mechanisms at block 334. In implementations, additional power control mechanisms may include an idle state control mechanism which controls idle states of one or more processing components, an active state control mechanism (e.g. frequency scaling during active period) which controls active states of one or more processing components, etc.

At block 336 the coordinator waits until an OOB+IB effective delay T _BOTH expire. The OOB+IB effective delay T _BOTH is a period for the power capping performed in both OOB and IB power capping modes to take effect after both the OOB and IB power capping modes are enforced/performed. The OOB+IB effective delay may be set and/or adjusted dynamically based on actual needs.

At block 338, the coordinator determines whether the power consumption P ₃ of the computing system is less than or equal to the power capping target.

If the coordinator determines that the power consumption P ₃ of the computing system is not less than or equal to the power capping target at block 338, the coordinator initiates a failover operation sequence flow at block 340. Additionally or alternatively, the coordinator may put the instances running on the computing system offline. Additionally or alternatively, the instances running on the computing system may be migrated to other computing systems as soon as possible.

If the coordinator determines that the power consumption of the computing system P ₃ is less than or equal to the power capping target at block 338, the process 300 is done at block 342.

After block 332, block 338, and block 340, the process 300 is done at block 342.

Now turning to FIG, 3C and continuing from block 324, at block 344, the coordinator creates a monitoring process.

At block 346, the coordinator keeps checking whether there is conflict in the pcode/ucode setting.

If the coordinator determines that there is conflict in the pcode/ucode setting at block 346, the coordinator stops performing power capping in one power capping mode at block 348. In implementations, the coordinator stops performing power capping in the IB power capping mode when the conflict exists. However, the coordinator continues to perform power capping in the OOB power capping mode. The IB power capping mode is stopped first because the OOB power capping mode does not occupy the OS of the computing system. Alternatively, the coordinator may stop performing power capping in the OOB power capping mode while continuing performing power capping in the OOB power capping mode.

If the coordinator determines that there is no conflict in the pcode/ucode setting at block 346, the coordinator determines whether both the OOB effective delay T _OOB and the IB effective delay T _IB expire at block 350.

If the coordinator determines that both the OOB effective delay T _OOB and the IB effective delay T _IB expire at block 350, the process 300 terminates at block 352.

If the coordinator determines that the OOB effective delay T _OOB or the IB effective delay T _IB does not expire at block 350, the process 300 goes back to block 346.

After block 348, the process 300 terminates at block 352.

In the above example process 300, if one of the OOB success rate R _OOB%and the IB success rate R _IB%is high enough to achieve the power capping target, then only one power capping mode is used. In implementations, the OOB power capping mode may be selected over the IB power capping mode, because the OOB power capping mode does not occupy the OS resource. Alternatively, the IB power capping mode may be selected over the OOB power capping mode. If none of the OOB success rate R _OOB%and the IB success rate R _IB%is sufficient to achieve the power capping target, the power capping is performed in both the OOB power capping mode and the IB power capping mode. During the dual-mode power capping, if any conflict is detected, the coordinator may unconditionally terminate one mode, for example, the IB power capping mode. Alternatively, the coordinator may terminate the OOB power capping mode. If both modes have been used and the power consumption of the computing system is still higher than the power capping target, the coordinator initiates the failover operation sequence flow. Moreover, the availability of cloud service may be improved.

FIG. 4 illustrates an example block diagram of an apparatus 400 for implementing the processes and methods described above.

The apparatus 400 includes one or more processors 402 and memory 404 communicatively coupled to the processor (s) 402. The processor (s) 402 executes one or more modules and/or processes to cause the processor (s) 402 to perform a variety of functions. In implementations, the processor (s) 402 may include a central processing unit (CPU) , a graphics processing unit (GPU) , both CPU and GPU, or other processing units or components known in the art. Additionally, each of the processor (s) 402 may possess its own local memory, which also may store program modules, program data, and/or one or more operating systems. In implementations, the memory 404 may be volatile, such as RAM, non-volatile, such as ROM, flash memory, miniature hard drive, memory card, and the like, or some combination thereof.

The apparatus 400 may additionally include an input/output (I/O) interface 406 for receiving and outputting data. The apparatus 400 may also include a communication module 408 allowing the apparatus 400 to communicate with other devices (not shown) over a network (not shown) . The network may include the Internet, wired media such as a wired network or direct-wired connections, and wireless media such as acoustic, radio frequency (RF) , infrared, and other wireless media.

The memory 404 may include one or more computer-executable modules (modules) that are executable by the processor (s) 402. In implementations, the memory 404 may include, but not limited to, a receiving module 410, a determining module 412, a power capping module 414, a waiting module 416, a power consumption determining module 418, a monitoring module 420, and a stopping module 422.

The receiving module 410 is configured to receive a power capping command, the power capping command including a power capping target for a computing system.

The determining module 412 is configured to determine whether a power consumption of the computing system satisfies the power capping target when performing the power capping in one of a first power capping mode and a second power capping mode.

The determining module 412 is further configured to determine whether a first success rate of the first power capping mode is greater than a first nominal success rate, perform power capping in the first power capping mode in response to determining that the first success rate of the first power capping mode is greater than the first nominal success rate, wait until a first effective delay expires, and determine whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the first power capping mode.

The determining module 412 is further configured to determine whether a second success rate of the second power capping mode is greater than a second nominal success rate, perform power capping in the second power capping mode in response to determining that the second success rate of the second power capping mode is greater than the second nominal success rate, wait until a second effective delay expires, and determine whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the second power capping mode.

In implementations, the first power capping mode is an Out-of-Band (OOB) power capping, and the second power capping mode is an In-Band (IB) power capping.

The power capping module 414 is configured to perform power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode. For example, the power capping may be performed in the first power capping mode and the second power capping mode simultaneously.

The waiting module 416 is configured to wait until both a first effective delay and a second effective delay expire.

The power consumption determining module 418 is configured to determine whether the power consumption of the computing system satisfies the power capping target.

The monitoring module 420 is configured to monitor whether conflict occurs. The monitoring module 420 is further configured to check whether the conflict occurs in a pcode/ucode setting.

The stopping module 422 is configured to stop performing the power capping in one of the first power capping mode and the second power capping mode when the monitoring module monitors that the conflict occurs.

With the above example apparatus 400, the first power capping mode and the second power capping mode are coordinated and combined to achieve the power capping target of the computing system. Therefore, power management during power capping is improved.

Processes and systems discussed herein may be implemented in, but not limited to, distributed computing environment, parallel computing environment, cluster computing environment, grid computing environment, cloud computing environment, electrical vehicles, power facilities, etc.

Some or all operations of the methods described above can be performed by execution of computer-readable instructions stored on a computer-readable storage medium, as defined below. The term “computer-readable instructions” as used in the description and claims, include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.

The computer-readable storage media may include volatile memory (such as random access memory (RAM) ) and/or non-volatile memory (such as read-only memory (ROM) , flash memory, etc. ) . The computer-readable storage media may also include additional removable storage and/or non-removable storage including, but not limited to, flash memory, magnetic storage, optical storage, and/or tape storage that may provide non-volatile storage of computer-readable instructions, data structures, program modules, and the like.

A non-transient computer-readable storage medium is an example of computer-readable media. Computer-readable media includes at least two types of computer-readable media, namely computer-readable storage media and communications media. Computer-readable storage media includes volatile and non-volatile, removable and non-removable media implemented in any process or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media includes, but is not limited to, phase change memory (PRAM) , static random-access memory (SRAM) , dynamic random-access memory (DRAM) , other types of random-access memory (RAM) , read-only memory (ROM) , electrically erasable programmable read-only memory (EEPROM) , flash memory or other memory technology, compact disk read-only memory (CD-ROM) , digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. As defined herein, computer-readable storage media do not include communication media.

The computer-readable instructions stored on one or more non-transitory computer-readable storage media that, when executed by one or more processors, may perform operations described above with reference to FIGs. 1-4. Generally, computer-readable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes.

EXAMPLE CLAUSES

Clause 1. A method comprising: receiving a power capping command, the power capping command including a power capping target for a computing system; determining whether a power consumption of the computing system satisfies the power capping target when performing the power capping in one of a first power capping mode and a second power capping mode; and performing the power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode.

Clause 2. The method of clause 1, wherein determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode comprises: determining whether a first success rate of the first power capping mode is greater than a first nominal success rate; performing the power capping in the first power capping mode in response to determining that the first success rate of the first power capping mode is greater than the first nominal success rate; waiting until a first effective delay expires; and determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the first power capping mode.

Clause 3. The method of clause 1, wherein determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode comprises: determining whether a second success rate of the second power capping mode is greater than a second nominal success rate; performing the power capping in the second power capping mode in response to determining that the second success rate of the second power capping mode is greater than the second nominal success rate; waiting until a second effective delay expires; and determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the second power capping mode.

Clause 4. The method of clause 1, further comprising: waiting until both a first effective delay and a second effective delay expire; and determining whether the power consumption of the computing system satisfies the power capping target.

Clause 5. The method of clause 1, further comprising: monitoring whether conflict occurs; stopping performing the power capping in one of the first power capping mode and the second power capping mode in response to monitoring that the conflict occurs.

Clause 6. The method of clause 5, wherein monitoring whether the conflict occurs comprises checking whether the conflict occurs in a pcode/ucode setting.

Clause 7. The method of clause 1, wherein the first power capping mode is an Out-of-Band (OOB) power capping, and the second power capping mode is an In-Band (IB) power capping.

Clause 8. A computer-readable storage medium storing computer-readable instructions executable by one or more processors, that when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving a power capping command, the power capping command including a power capping target for a computing system; determining whether a power consumption of the computing system satisfies the power capping target when performing the power capping in one of a first power capping mode and a second power capping mode; and performing the power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode.

Clause 9. The computer-readable storage medium of clause 8, wherein determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode comprises: determining whether a first success rate of the first power capping mode is greater than a first nominal success rate; performing the power capping in the first power capping mode in response to determining that the first success rate of the first power capping mode is greater than the first nominal success rate; waiting until a first effective delay expires; and determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the first power capping mode.

Clause 10. The computer-readable storage medium of clause 8, wherein determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode comprises: determining whether a second success rate of the second power capping mode is greater than a second nominal success rate; performing the power capping in the second power capping mode in response to determining that the second success rate of the second power capping mode is greater than the second nominal success rate; waiting until a second effective delay expires; and determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the second power capping mode.

Clause 11. The computer-readable storage medium of clause 8, further comprising: waiting until both a first effective delay and a second effective delay expire; and determining whether the power consumption of the computing system satisfies the power capping target.

Clause 12. The computer-readable storage medium of clause 8, further comprising: monitoring whether conflict occurs; stopping performing the power capping in one of the first power capping mode and the second power capping mode in response to monitoring that the conflict occurs.

Clause 13. The computer-readable storage medium of clause 12, wherein monitoring whether the conflict occurs comprises checking whether the conflict occurs in a pcode/ucode setting.

Clause 14. The computer-readable storage medium of clause 8, wherein the first power capping mode is an Out-of-Band (OOB) power capping, and the second power capping mode is an In-Band (IB) power capping.

Clause 15. An apparatus comprising: one or more processors; and memory communicatively coupled to the one or more processors, the memory storing computer-executable modules executable by the one or more processors, the computer-executable modules including: a receiving module, configured to receive a power capping command, the power capping command including a power capping target for a computing system; a determining module, configured to determine whether a power consumption of the computing system satisfies the power capping target when performing the power capping in one of a first power capping mode and a second power capping mode; and a power capping module, configured to perform power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode.

Clause 16. The apparatus of clause 15, wherein the determining module is further configured to: determine whether a first success rate of the first power capping mode is greater than a first nominal success rate; perform power capping in the first power capping mode in response to determining that the first success rate of the first power capping mode is greater than the first nominal success rate; wait until a first effective delay expires; and determine whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the first power capping mode.

Clause 17. The apparatus of clause 15, wherein the determining module is further configured to: determine whether a second success rate of the second power capping mode is greater than a second nominal success rate; perform power capping in the second power capping mode in response to determining that the second success rate of the second power capping mode is greater than the second nominal success rate; wait until a second effective delay expires; and determine whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the second power capping mode.

Clause 18. The apparatus of clause 15, the computer-executable modules further comprising: a waiting module, configured to wait until both a first effective delay and a second effective delay expire; and a power consumption determining module, configured to determine whether the power consumption of the computing system satisfies the power capping target.

Clause 19. The apparatus of clause 15, the computer-executable modules further comprising: a monitoring module, configured to monitor whether conflict occurs; a stopping module, configured to stop performing the power capping in one of the first power capping mode and the second power capping mode when the monitoring module monitors that the conflict occurs.

Clause 20. The apparatus of clause 19, wherein the monitoring module is further configured to check whether the conflict occurs in a pcode/ucode setting.

Clause 21. The apparatus of clause 15, wherein the first power capping mode is an Out-of-Band (OOB) power capping, and the second power capping mode is an In-Band (IB) power capping.

CONCLUSION

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.

Claims

A method comprising:

receiving a power capping command, the power capping command including a power capping target for a computing system;

determining whether a power consumption of the computing system satisfies the power capping target when performing power capping in one of a first power capping mode and a second power capping mode; and

performing the power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode.
The method of claim 1, wherein determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode comprises:

determining whether a first success rate of the first power capping mode is greater than a first nominal success rate;

performing the power capping in the first power capping mode in response to determining that the first success rate of the first power capping mode is greater than the first nominal success rate;

waiting until a first effective delay expires; and

determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the first power capping mode.
The method of claim 1, wherein determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode comprises:

determining whether a second success rate of the second power capping mode is greater than a second nominal success rate;

performing the power capping in the second power capping mode in response to determining that the second success rate of the second power capping mode is greater than the second nominal success rate;

waiting until a second effective delay expires; and

determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the second power capping mode.
The method of claim 1, further comprising:

waiting until both a first effective delay and a second effective delay expire; and

determining whether the power consumption of the computing system satisfies the power capping target.
The method of claim 1, further comprising:

monitoring whether conflict occurs;

stopping performing the power capping in one of the first power capping mode and the second power capping mode in response to monitoring that the conflict occurs.
The method of claim 5, wherein monitoring whether the conflict occurs comprises checking whether the conflict occurs in a pcode/ucode setting.
The method of claim 1, wherein the first power capping mode is an Out-of-Band (OOB) power capping mode, and the second power capping mode is an In-Band (IB) power capping mode.
A computer-readable storage medium storing computer-readable instructions executable by one or more processors, that when executed by the one or more processors, cause the one or more processors to perform operations comprising:

receiving a power capping command, the power capping command including a power capping target for a computing system;

determining whether a power consumption of the computing system satisfies the power capping target when performing power capping in one of a first power capping mode and a second power capping mode; and

performing the power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode.
The computer-readable storage medium of claim 8, wherein determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode comprises:

determining whether a first success rate of the first power capping mode is greater than a first nominal success rate;

performing the power capping in the first power capping mode in response to determining that the first success rate of the first power capping mode is greater than the first nominal success rate;

waiting until a first effective delay expires; and

determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the first power capping mode.
The computer-readable storage medium of claim 8, wherein determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode comprises:

determining whether a second success rate of the second power capping mode is greater than a second nominal success rate;

performing the power capping in the second power capping mode in response to determining that the second success rate of the second power capping mode is greater than the second nominal success rate;

waiting until a second effective delay expires; and

determining whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the second power capping mode.
The computer-readable storage medium of claim 8, further comprising:

waiting until both a first effective delay and a second effective delay expire; and

determining whether the power consumption of the computing system satisfies the power capping target.
The computer-readable storage medium of claim 8, further comprising:

monitoring whether conflict occurs;

stopping performing the power capping in one of the first power capping mode and the second power capping mode in response to monitoring that the conflict occurs.
The computer-readable storage medium of claim 12, wherein monitoring whether the conflict occurs comprises checking whether the conflict occurs in a pcode/ucode setting.
The computer-readable storage medium of claim 8, wherein the first power capping mode is an Out-of-Band (OOB) power capping, and the second power capping mode is an In-Band (IB) power capping.
An apparatus comprising:

one or more processors; and

memory communicatively coupled to the one or more processors, the memory storing computer-executable modules executable by the one or more processors, the computer-executable modules including:

a receiving module, configured to receive a power capping command, the power capping command including a power capping target for a computing system;

a determining module, configured to determine whether a power consumption of the computing system satisfies the power capping target when performing power capping in one of a first power capping mode and a second power capping mode; and

a power capping module, configured to perform the power capping in the first power capping mode and the second power capping mode in response to determining that the power consumption of the computing system does not satisfy the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode.
The apparatus of claim 15, wherein the determining module is further configured to:

determine whether a first success rate of the first power capping mode is greater than a first nominal success rate;

perform the power capping in the first power capping mode in response to determining that the first success rate of the first power capping mode is greater than the first nominal success rate;

wait until a first effective delay expires; and

determine whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the first power capping mode.
The apparatus of claim 15, wherein the determining module is further configured to:

determine whether a second success rate of the second power capping mode is greater than a second nominal success rate;

perform the power capping in the second power capping mode in response to determining that the second success rate of the second power capping mode is greater than the second nominal success rate;

wait until a second effective delay expires; and

determine whether the power consumption of the computing system satisfies the power capping target when performing the power capping in the second power capping mode.
The apparatus of claim 15, the computer-executable modules further comprising:

a waiting module, configured to wait until both a first effective delay and a second effective delay expire; and

a power consumption determining module, configured to determine whether the power consumption of the computing system satisfies the power capping target.
The apparatus of claim 15, the computer-executable modules further comprising:

a monitoring module, configured to monitor whether conflict occurs;

a stopping module, configured to stop performing the power capping in one of the first power capping mode and the second power capping mode when the monitoring module monitors that the conflict occurs.
The apparatus of claim 19, wherein the monitoring module is further configured to check whether the conflict occurs in a pcode/ucode setting.
The apparatus of claim 15, wherein the first power capping mode is an Out-of-Band (OOB) power capping, and the second power capping mode is an In-Band (IB) power capping.