CN114402272B - Power management method and apparatus - Google Patents

Power management method and apparatus Download PDF

Info

Publication number
CN114402272B
CN114402272B CN201980099694.XA CN201980099694A CN114402272B CN 114402272 B CN114402272 B CN 114402272B CN 201980099694 A CN201980099694 A CN 201980099694A CN 114402272 B CN114402272 B CN 114402272B
Authority
CN
China
Prior art keywords
power
power capping
mode
capping
computing system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201980099694.XA
Other languages
Chinese (zh)
Other versions
CN114402272A (en
Inventor
宋军
孟晓林
程霖
奉有泉
卢毅军
朱昊
李志兵
何玲芳
王冠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Cloud Computing Ltd
Original Assignee
Alibaba Cloud Computing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Cloud Computing Ltd filed Critical Alibaba Cloud Computing Ltd
Publication of CN114402272A publication Critical patent/CN114402272A/en
Application granted granted Critical
Publication of CN114402272B publication Critical patent/CN114402272B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G06F1/3243—Power saving in microcontroller unit
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G06F1/3287—Power saving characterised by the action undertaken by switching off individual functional units in the computer system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G06F1/329—Power saving characterised by the action undertaken by task scheduling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G06F9/4893—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues taking into account power or heat criteria
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Power Sources (AREA)

Abstract

Methods and apparatus for improved power management are provided. A power management component receives a power capping command. The power capping command includes a power capping target of the computing system. The power management component determines whether power consumption of the computing system meets the power capping target when executing 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 meet 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 a method and apparatus for coordinating different power capping modes.
Background
Power capping is a technique widely used in modern Data Centers (DC) to increase computation density on racks and avoid power outages. Hardware (e.g., chip, server) suppliers such as Original Design Manufacturers (ODMs) and Original Equipment Manufacturers (OEMs) and software (e.g., operating System (OS), virtualization management program) suppliers provide basic power capping capability.
However, the vendor does not put the power capping function together into a solution that can coordinate the different power capping modes to achieve the power capping goal.
Disclosure of Invention
This summary is not intended to identify essential features of the claimed subject matter, nor is it intended to be used in a limiting sense of the scope of the claimed subject matter.
Example implementations of power management are described below. In an implementation, a power management component receives a power capping command. The power capping command includes a power capping target for the computing system. The power management component determines whether power consumption of the computing system meets a power capping target when performing power capping in one of a first power capping mode and a second power capping mode. The power management component performs power capping in the first power capping mode and the second power capping mode in response to determining that power consumption of the computing system does not meet the power capping target when performing 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 goal of the computing system. Thus, power capping is more reliable and usable.
Drawings
The detailed description is set forth with reference to the drawings. In the drawings, the leftmost digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference symbols in different drawings indicates similar or identical items or features.
FIG. 1 illustrates an example block diagram of a computing system.
Fig. 2 illustrates an example flow chart of a process for coordinating different power capping modes.
Fig. 3A, 3B, and 3C illustrate in detail an example flowchart of a process for coordinating different power capping modes.
Fig. 4 illustrates an example apparatus for implementing the above-described processes and methods.
Detailed Description
The terms as used herein are expressed as follows.
Out-of-band (OOB) refers to a method of accessing a computing system without using the Operating System (OS) of the computing system.
In-band (IB) refers to a method of accessing a computing system via an OS of the computing system.
The Manageability Engine (ME) refers to logic that typically resides in the CPU external bridge chip on the Intel platform.
Node Manager (NM) refers to a piece of firmware or state machine in the ME that is responsible for power management of a computing system.
Telemetry data hubs refer to a piece of firmware or state machine in the ME that is responsible for collecting performance telemetry data from the processor.
The rest of the platform (RoP) refers to other computing components besides the main parts like CPU, GPU, platform Controller Hub (PCH), fans, power Supply Units (PSU).
Power capping refers to a method of limiting the power consumption of a computing system to not exceed a power limit/upper limit.
A Baseboard Management Controller (BMC) refers to a small embedded coprocessor that operates as an Intelligent Platform Management Interface (IPMI) bus master to perform system level power management, monitoring, logging, alerting, and the like.
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, a computing system 100 includes a RoP 102, a storage 104, a network 106, a fan 108, a Graphics Processing Unit (GPU)/Field Programmable Gate Array (FPGA) 110, a double data rate synchronous dynamic random access memory (DDR SDRAM)) 112, a Central Processing Unit (CPU) 114, a chipset 116, a BMC 118, an ME 120, a power capping pcode/ucode 122, a power management component 124, and an 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 may be a controller, console, or the like that communicates with the computing system 100.
The power management component 124 includes 3 parts, namely part a128, part B130, and part C132. Part a128 is an OOB power capping sub-agent. Part B130 is the coordinator. Part C132 is the IB power capping sub-agent. In implementations, the power management component 124 can be implemented in software, hardware, firmware, or any combination thereof.
The power management component 124 is configured to perform different power capping modes, such as IB power capping mode and OOB power capping mode. In IB power capping mode, power management component 124 is configured to run (as a service) or be ready to run on the OS of computing system 100 in response to management commands. In OOB power capping mode, power management component 124 is configured to use a management port to access a node manager (not shown) in ME 120. In that case, the power management component 124 is not running 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 a Mode Specific Register (MSR) to read/write the power capping pcode/ucode 122. The power management component 124 is further configured to communicate with an authentication 128.
OOB power capping sub-agent 128 is configured to perform power capping in OOB power capping mode.
IB power capping sub-agent 132 is configured to perform power capping in IB power capping mode.
Coordinator 130 is configured to coordinate/dispatch power capping tasksOOB power capping sub-agent 128 and/or IB power capping sub-agent 132. The coordinator 130 is further configured to calculate an OOB success rate R within a period (e.g., a last period) upon receiving the power capping command OOB % and IB success rate R IB % and assign power capping tasks to either OOB power capping sub-agent 128 or IB power capping sub-agent 132 or both to achieve the power capping target.
In an implementation, the OOB success rate may be calculated as follows. In period T, when the OOB power capping mode is performed on the computing system, the total number of attempts at power capping is N, and the number of attempts at power consumption of the computing system to meet the power capping target is N. OOB success rate R OOB ％＝n/N*100％。
In an implementation, IB success rate may be calculated as follows. During period T, when IB power capping mode is performed on the computing system, the total number of attempts at power capping is N and the number of attempts at power consumption of the computing system to meet the power capping target is N. IB success rate R IB ％＝n/N*100％。
In implementations, IB power capping mode or OOB power capping mode may be delayed or even denied when traffic and/or load is high. For example, in a heavily used computer, the CPU utilization is 100%, the memory bandwidth utilization is 80% +, the store queue is 100% + full and the network bandwidth utilization is 80% +. In OOB power capping mode, the power management component needs to pass through the IPMI protocol on a power management bus (PMBus) (not shown) with the help of the BMC as an embedded on-board coprocessor. When there are a large number of hardware errors, the BMC needs to handle high priority activities such as logging and alerting, but medium priority activities such as power capping commands may be ignored, deferred, or denied. A similar situation may occur in IB power capping mode. When utilization at a computing system is high, there is a chance that IB accesses are severely delayed or even suspended.
Different dimensions of the cloud service, such as availability, latency, reliability, throughput, etc., can be adjusted based on a Service Level Agreement (SLA) between the service provider and the customer. Generally, cloud services need to provide availability up to 99.99% or even better. Software and applications may use distributed and/or redundant designs to achieve this level of availability over unreliable infrastructure. Practice of the supersize cloud service provides increased density of server deployments, which significantly increases outage risk. The service provider may set a power buffer large enough to prevent the risk of power outage. Additionally, power capping is performed to control power consumption to reduce power outage risk. During power capping, the expected availability may be low, e.g., 99.9%. In implementations, the availability in OOB power capping mode may be around 95%, which may vary under different conditions, but well below 99.9% of the desired availability.
In an implementation, IB power capping mode and OOB power capping mode may be coordinated and combined to achieve a power capping goal of a computing system. Furthermore, the availability of cloud services under power capping may be improved.
Fig. 2 illustrates an example flow chart of a process 200 for coordinating different power capping modes.
In block 202, the power management component receives a power capping command. The power capping command includes a power capping target for the computing system. The power capping target may be dynamically set and/or adjusted based on actual needs.
In block 204, the power management component determines whether the power consumption of the computing system meets a power capping target when performing power capping in one of the first power capping mode and the second power capping mode.
In an implementation, the power management component determines whether a first power of the first power capping mode is greater than a first nominal success rate. The power management component performs power capping in the first power capping mode in response to determining that the first power forming in the first power capping mode is greater than a first nominal success rate. The first power may be calculated as follows. During period T, when the first power capping mode is performed on the computing system, the total number of attempts at power capping is N, and the number of attempts at power consumption of the computing system to meet the power capping target is N. The first power is N/N100%. The first nominal success rate may be determined by, but is not limited to, specifications, historical data, statistical data, test data, simulation data, empirical data, and the like. The power management component waits until the expiration of the first effective delay. The first effective delay is a period of time that the first power capping mode is active after the first power capping mode is implemented/executed. The first effective delay may be dynamically set and/or adjusted based on actual needs. The power management component determines whether power consumption of the computing system meets a power capping target when performing power capping in a first power capping mode.
In an implementation, the power management component determines whether a second power contribution of a second power capping mode is greater than a second nominal success rate. The second power may be calculated as follows. During period T, when the second power capping mode is performed on the computing system, the total number of attempts at power capping is N and the number of attempts at power consumption of the computing system to meet the power capping target is N. The second power is N/N100%. The second nominal success rate may be determined by, but is not limited to, specifications, historical data, statistical data, test data, simulation data, empirical data, and the like. The power management component performs power capping in the second power capping mode in response to determining that the second power of the second power capping mode is greater than the second nominal success rate. The power management component waits until the second effective delay expires. The second effective delay is a period of time that the second power capping mode is active after the second power capping mode is implemented/executed. The second effective delay may be dynamically set and/or adjusted based on actual needs. The power management component determines whether power consumption of the computing system meets a power capping target when performing power capping in the second power capping mode.
In an embodiment, the first power capping mode is an OOB power capping mode and the second power capping mode is an IB power capping mode.
In block 206, the power management component performs 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 meet the power capping target when performing power capping in one of the first power capping mode and the second power capping mode. For example, power capping may be performed in the first power capping mode and the second power capping mode simultaneously.
In an implementation, the power management component waits until both the first and second effective delays expire and determines whether the power consumption of the computing system meets a power capping target.
In an implementation, the power management component monitors whether a conflict occurs and stops performing power capping in one of the first power capping mode and the second power capping mode in response to monitoring that a conflict occurs.
In an implementation, the power management component checks whether a conflict occurs in the pcode/ucode settings.
Using the example process 200 described above, the first power capping mode and the second power capping mode are coordinated and combined to achieve a power capping goal of the computing system. Thus, power management during power capping is improved.
Fig. 3A, 3B, and 3C illustrate in detail an example flowchart of a process 300 for coordinating different power capping modes.
At block 302, the coordinator receives a power capping command. The power capping command includes a power capping target for the computing system. The power capping target may be dynamically set and/or adjusted based on actual needs.
At block 304, the coordinator determines the OOB success rate R OOB % is greater than nominal OOB success rate R OOB * Percent of the total weight of the composition. OOB success rate R OOB % algorithm is as described above with reference to fig. 1. The nominal OOB success rate R may be determined by, but not limited to, specifications, historical data, statistical data, test data, simulation data, empirical data, and the like OOB *％。
If the coordinator determines an OOB success rate R at block 304 OOB % greater than nominal OOB success rate R OOB * In%, then at block 306, the coordinator instructs the OOB power capping sub-agent to perform power capping in OOB power capping mode with the node manager.
If the coordinator determines an OOB success rate R at block 304 OOB % is not greater than nominal OOB success rate R OOB * In percent, the process proceeds to block 316.
At block 308, the coordinator waits until the OOB is effectively delayed by T OOB Until expiration. OOB effective delay T OOB Is the period of time that the OOB power capping mode is in effect after the OOB power capping mode is implemented/executed. OOB effective delay T may be dynamically set and/or adjusted based on actual needs OOB 。
At block 310, the coordinator checks the power consumption P of the computing system 1 。
At block 312, the coordinator determines the power consumption P of the computing system 1 Whether less than or equal to the power capping target.
If the coordinator determines at block 312 that computing system P 1 If the power consumption of (a) is less than or equal to the power capping target, then the coordinator updates the OOB success rate R at block 314 OOB ％。
If the coordinator determines at block 312 the power consumption P of the computing system 1 Not less than or equal to the power capping target, the coordinator prepares an initial value for IB power capping mode at block 316. In an implementation, the initial value includes IB success rate R IB % and nominal IB success rate R IB *％。
At block 318, the process 300 is complete.
As shown in fig. 3B, process 300 continues from block 316 and at block 320 the coordinator determines IB success rate R IB % is greater than nominal IB success rate R IB * Percent of the total weight of the composition. The algorithm for IB success rate RIB% is described above with reference to fig. 1. The nominal IB success rate R may be determined by, but not limited to, specifications, historical data, statistical data, test data, simulation data, empirical data, and the like IB *％。
If the coordinator determines at block 320 that IB success rate R IB % greater than nominal IB success rate R IB * In%, the coordinator instructs the IB power capping sub-agent to perform power capping in IB power capping mode at block 322.
At block 324, the coordinator waits until IB effectively delays T IB Until expiration. IB effective delay T IB Is the period of time that the IB power capping mode is active after the IB power capping mode is implemented/executed. The IB effective delay can be dynamically set and/or adjusted based on actual needsLate T IB 。
If the coordinator determines at block 320 that IB success rate R IB % is not greater than nominal IB success rate R IB * In%, then at block 326, the coordinator instructs the OOB power capping sub-agent to perform power capping in OOB power capping mode with the node manager. At the same time, the coordinator also instructs the IB power capping sub-agent to perform power capping in IB power capping mode. In an implementation, the power management component performs power capping in IB power capping mode and OOB power capping mode simultaneously.
At block 328, the coordinator waits until the OOB is effectively delayed by T OOB And IB effective delay T IB Until it expires.
After blocks 324 and 328, process 300 proceeds to block 330.
At block 330, the coordinator determines the power consumption P of the computing system 2 Whether less than or equal to the power capping target.
If the coordinator determines at block 330 the power consumption P of the computing system 2 Less than or equal to the power capping target, the coordinator updates IB success rate R at block 332 OOB ％。
If the coordinator determines at block 330 the power consumption P of the computing system 2 Not less than or equal to the power capping target, then power capping is performed with an additional power control mechanism at block 334. In an implementation, the additional power control mechanisms may include an idle state control mechanism that controls an idle state of the one or more processing components, an active state control mechanism that controls an active state of the one or more processing components (e.g., frequency scaling during an active period), and so forth.
At block 336 the coordinator waits until oob+ib is effectively delayed by T BOTH Until expiration. OOB+IB effective delay T BOTH Is the period of time that the power capping performed in both the OOB power capping mode and the IB power capping mode is effective after both the OOB power capping mode and the IB power capping mode are implemented/performed. The oob+ib effective delay may be dynamically set and/or adjusted based on actual needs.
At block 338, the coordinator determines the power consumption P of the computing system 3 Whether less than or equal to the power seal headAnd (5) marking.
If the coordinator determines at block 338 the power consumption P of the computing system 3 Not less than or equal to the power capping target, the coordinator initiates a failover operation sequence flow at block 340. Additionally or alternatively, the coordinator may take an instance running on the computing system offline. Additionally or alternatively, instances running on a computing system may be migrated to other computing systems as quickly as possible.
If the coordinator determines at block 338 that computing system P 3 If the power consumption of (a) is less than or equal to the power capping target, then process 300 is complete at block 342.
After blocks 332, 338 and 340, process 300 is complete at block 342.
Turning now to FIG. 3C and continuing from block 324, at block 344 the coordinator creates a monitoring process.
At block 346, the coordinator continues to check whether there is a conflict in the pcode/ucode settings.
If the coordinator determines at block 346 that there is a conflict in pcode/ucode settings, the coordinator stops performing power capping in a power capping mode at block 348. In an implementation, the coordinator stops performing power capping in IB power capping mode when there is a conflict. 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 to perform power capping in the OOB power capping mode.
If the coordinator determines at block 346 that there is no conflict in the pcode/ucode settings, the coordinator determines at block 350 an OOB effective delay T OOB And IB effective delay T IB Whether or not they have expired.
If the coordinator determines that the OOB is valid for delay T at block 350 OOB And IB effective delay T IB And expires, process 300 terminates at block 352.
If the coordinator determines that the OOB is valid for delay T at block 350 OOB Or IB effective delay T IB Without expiration, the process 300 returns to block 346.
After block 348, the process 300 terminates at block 352.
In the above example process 300, if the OOB success rate R OOB % and IB success rate R IB One of the% is high enough to reach the power capping target, then only one power capping mode is used. In an implementation, the OOB power capping mode may be selected over the IB power capping mode because the OOB power capping mode does not occupy OS resources. Alternatively, IB power capping mode may be selected over OOB power capping mode. If OOB success rate R OOB % and IB success rate R IB % who is insufficient to reach the power capping target, then power capping is performed in both OOB power capping mode and IB power capping mode. During dual mode power capping, if any conflict is detected, the coordinator may unconditionally terminate one mode, such as 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 above the power capping target, the coordinator initiates a failover operation sequence flow. Furthermore, the usability of the cloud service may be improved.
Fig. 4 illustrates an example block diagram of an apparatus 400 for implementing the above-described processes and methods.
The device 400 includes one or more processors 402 and a memory 404 communicatively coupled to the processors 402. Processor 402 executes one or more modules and/or processes to cause processor 402 to perform various functions. In implementations, the processor 402 may include a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), both a CPU and GPU, or other processing units or components known in the art. Additionally, each processor 402 may have its own local memory, which may also store program modules, program data, and/or one or more operating systems. In an implementation, the memory 404 may be volatile, such as RAM, non-volatile, such as ROM, flash memory, a miniature hard drive, a memory card, etc., or some combination thereof.
The device 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 that allows 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 connection, and wireless media such as acoustic, radio Frequency (RF), infrared and other wireless media.
Memory 404 may include one or more computer-executable modules (modules) that may be executed by processor 402. In an implementation, memory 404 may include, but is 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 that includes a power capping target for the computing system.
The determination module 412 is configured to determine whether the power consumption of the computing system meets a power capping target when performing power capping in one of the first power capping mode and the second power capping mode.
The determination module 412 is further configured to determine whether the first power 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 power of the first power capping mode is greater than the first nominal success rate, wait until the first effective delay expires, and determine whether the power consumption of the computing system satisfies a power capping target when performing power capping in the first power capping mode.
The determination module 412 is further configured to determine whether a second power contribution 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 power contribution of the second power capping mode is greater than the second nominal success rate, wait until the expiration of a second effective delay, and determine whether power consumption of the computing system satisfies a power capping target when performing power capping in the second power capping mode.
In an implementation, the first power capping mode is out-of-band (OOB) power capping and the second power capping mode is 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 power consumption of the computing system does not meet the power capping target when performing power capping in one of the first power capping mode and the second power capping mode. For example, power capping may be performed in the first power capping mode and the second power capping mode simultaneously.
The wait module 416 is configured to wait until both the first effective delay and the second effective delay expire.
The power consumption determination module 418 is configured to determine whether the power consumption of the computing system meets a power capping target.
The monitoring module 420 is configured to monitor whether a conflict occurs. The monitoring module 420 is further configured to check whether a conflict occurs in the pcode/ucode settings.
The stopping module 422 is configured to stop performing power capping in one of the first power capping mode and the second power capping mode when the monitoring module detects that a collision has occurred.
With the example apparatus 400 described above, the first power capping mode and the second power capping mode are coordinated and combined to achieve a power capping goal of the computing system. Thus, power management during power capping is improved.
The processes and systems discussed herein may be implemented in, but are not limited to, distributed computing environments, parallel computing environments, clustered computing environments, grid computing environments, cloud computing environments, electric vehicles, electrical facilities, and the like.
Some or all of the operations of the methods described above can be performed by executing computer readable instructions stored on a computer readable storage medium as defined below. The term "computer readable instructions" as used in the specification and claims includes routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer readable instructions can be implemented on a variety of 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 medium may include volatile memory, such as Random Access Memory (RAM), and/or nonvolatile memory, such as Read Only Memory (ROM), flash memory, and the like. The computer-readable storage media may also include additional removable storage devices and/or non-removable storage devices including, but not limited to, flash memory, magnetic storage, optical storage devices, and/or tape storage devices which may provide non-volatile storage of computer-readable instructions, data structures, program modules, and the like.
Non-transitory computer-readable storage media are examples of computer-readable media. Computer-readable media include at least two types of computer-readable media, namely computer-readable storage media and communication media. Computer-readable storage media includes volatile and nonvolatile, 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 disc 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 transport mechanism. As defined herein, computer-readable storage media does not include communication media.
Computer readable instructions stored on one or more non-transitory computer readable storage media, when executed by one or more processors, may perform the operations described above with reference to fig. 1-4. Generally, computer readable instructions include routines, programs, objects, components, data structures, etc. 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, the method comprising: receiving a power capping command, the power capping command comprising a power capping target of a computing system; determining whether power consumption of the computing system meets the power capping target when the power capping is performed 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 meet 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 if the power consumption of the computing system meets 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 power 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 power forming of the first power capping mode is greater than the first nominal success rate; waiting until the first effective delay expires; and determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the first power capping mode.
Clause 3, the method of clause 1, wherein determining if the power consumption of the computing system meets 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 that a second power 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 power of the second power capping mode is greater than the second nominal success rate; waiting until the second effective delay expires; and determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the second power capping mode.
Clause 4. The method of clause 1, further comprising: waiting until both the first and second effective delays expire; and determining whether the power consumption of the computing system meets the power capping target.
Clause 5. The method of clause 1, further comprising: monitoring whether a conflict occurs; stopping performing the power capping in one of the first power capping mode and the second power capping mode in response to detecting the occurrence of the conflict.
Clause 6. The method of clause 5, wherein monitoring if the conflict occurs comprises checking if the conflict occurs in a pcode/ucode setting.
Clause 7. The method of clause 1, wherein the first power capping mode is out-of-band (OOB) power capping and the second power capping mode is in-band (IB) power capping.
Clause 8, a computer-readable storage medium storing computer-readable instructions executable by one or more processors, the computer-readable instructions, 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 comprising a power capping target of a computing system; determining whether power consumption of the computing system meets the power capping target when the power capping is performed 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 meet 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 if the power consumption of the computing system meets 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 power 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 power forming of the first power capping mode is greater than the first nominal success rate; waiting until the first effective delay expires; and determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the first power capping mode.
Clause 10, the computer-readable storage medium of clause 8, wherein determining if the power consumption of the computing system meets 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 power 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 power of the second power capping mode is greater than the second nominal success rate; waiting until the second effective delay expires; and determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the second power capping mode.
Clause 11 the computer readable storage medium of clause 8, further comprising: waiting until both the first and second effective delays expire; and determining whether the power consumption of the computing system meets the power capping target.
Clause 12 the computer readable storage medium of clause 8, further comprising: monitoring whether a conflict occurs; stopping performing the power capping in one of the first power capping mode and the second power capping mode in response to detecting the occurrence of the conflict.
Clause 13 the computer readable storage medium of clause 12, wherein monitoring if the conflict occurs comprises checking if 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 out-of-band (OOB) power capping and the second power capping mode is in-band (IB) power capping.
Clause 15, an apparatus, the apparatus comprising: one or more processors; and a 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 comprising: a receiving module configured to receive a power capping command, the power capping command comprising a power capping target of a computing system; a determining module configured to determine whether power consumption of the computing system meets the power capping target when the power capping is performed 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 meet 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 clause 15, wherein the determination module is further configured to: determining whether a first power 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 power forming of the first power capping mode is greater than the first nominal success rate; waiting until the first effective delay expires; and determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the first power capping mode.
Clause 17 the device of clause 15, wherein the determination module is further configured to: determining whether a second power 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 power of the second power capping mode is greater than the second nominal success rate; waiting until the second effective delay expires; and determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the second power capping mode.
Clause 18 the device of clause 15, the computer-executable module further comprising: a wait module configured to wait until both the first effective delay and the second effective delay expire; and a power consumption determination module configured to determine whether the power consumption of the computing system meets the power capping target.
Clause 19 the device of clause 15, the computer-executable module further comprising: a monitoring module configured to monitor whether a 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 collision occurs.
Clause 20 the device of clause 19, wherein the monitoring module is further configured to check whether the conflict occurs in a pcode/ucode setting.
Clause 21 the device of clause 15, wherein the first power capping mode is out-of-band (OOB) power capping and the second power capping mode is in-band (IB) power capping.
Conclusion(s)
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 example forms of implementing the claims.

Claims (18)

1. A method of power management, the method comprising:
receiving a power capping command, the power capping command comprising a power capping target of a computing system;
determining whether power consumption of the computing system meets the power capping target when the power capping is performed in one of a first power capping mode and a second power capping mode, wherein determining whether to perform power capping in the respective capping mode is based on whether a success rate of the first or second power capping mode is greater than a respective nominal success rate; 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 meet the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode;
wherein the first power capping mode is out-of-band (OOB) power capping and the second power capping mode is in-band (IB) power capping.
2. The method of claim 1, wherein determining whether the power consumption of the computing system meets 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 power 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 power forming of the first power capping mode is greater than the first nominal success rate;
waiting until the first effective delay expires; and
determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the first power capping mode.
3. The method of claim 1, wherein determining whether the power consumption of the computing system meets 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 that a second power 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 power of the second power capping mode is greater than the second nominal success rate;
waiting until the second effective delay expires; and
determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the second power capping mode.
4. The method of claim 1, further comprising:
waiting until both the first and second effective delays expire; and
a determination is made as to whether the power consumption of the computing system meets the power capping target.
5. The method of claim 1, further comprising:
monitoring whether a conflict occurs;
stopping performing the power capping in one of the first power capping mode and the second power capping mode in response to detecting the occurrence of the conflict.
6. The method of claim 5, wherein monitoring whether the conflict occurs comprises checking whether the conflict occurs in a pcode/ucode setting.
7. A computer-readable storage medium storing computer-readable instructions executable by one or more processors, which 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 comprising a power capping target of a computing system;
determining whether power consumption of the computing system meets the power capping target when the power capping is performed in one of a first power capping mode and a second power capping mode, wherein determining whether to perform power capping in the respective capping mode is based on whether a success rate of the first or second power capping mode is greater than a respective nominal success rate; 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 meet the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode;
wherein the first power capping mode is out-of-band (OOB) power capping and the second power capping mode is in-band (IB) power capping.
8. The computer-readable storage medium of claim 7, wherein determining whether the power consumption of the computing system meets 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 power 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 power forming of the first power capping mode is greater than the first nominal success rate;
waiting until the first effective delay expires; and
determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the first power capping mode.
9. The computer-readable storage medium of claim 7, wherein determining whether the power consumption of the computing system meets 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 power 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 power of the second power capping mode is greater than the second nominal success rate;
waiting until the second effective delay expires; and
determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the second power capping mode.
10. The computer-readable storage medium of claim 7, further comprising:
waiting until both the first and second effective delays expire; and
a determination is made as to whether the power consumption of the computing system meets the power capping target.
11. The computer-readable storage medium of claim 7, further comprising:
monitoring whether a conflict occurs;
Stopping performing the power capping in one of the first power capping mode and the second power capping mode in response to detecting the occurrence of the conflict.
12. The computer-readable storage medium of claim 11, wherein monitoring whether the conflict occurs comprises checking whether the conflict occurs in a pcode/ucode setting.
13. A power management apparatus, the apparatus comprising:
one or more processors; and
a 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 comprising:
a receiving module configured to receive a power capping command, the power capping command comprising a power capping target of a computing system;
a determining module configured to determine whether power consumption of the computing system meets the power capping target when the power capping is performed in one of a first power capping mode and a second power capping mode, wherein determining whether to perform power capping in the respective capping mode is based on whether a success rate of the first or second power capping mode is greater than a respective nominal success rate; 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 meet the power capping target when performing the power capping in one of the first power capping mode and the second power capping mode.
14. The device of claim 13, wherein the determination module is further configured to:
determining whether a first power 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 power forming of the first power capping mode is greater than the first nominal success rate;
waiting until the first effective delay expires; and
determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the first power capping mode.
15. The device of claim 13, wherein the determination module is further configured to:
determining whether a second power 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 power of the second power capping mode is greater than the second nominal success rate;
waiting until the second effective delay expires; and
determining whether the power consumption of the computing system meets the power capping target when the power capping is performed in the second power capping mode.
16. The apparatus of claim 13, the computer-executable module further comprising:
a wait module configured to wait until both the first effective delay and the second effective delay expire; and
a power consumption determination module configured to determine whether the power consumption of the computing system meets the power capping target.
17. The apparatus of claim 13, the computer-executable module further comprising:
a monitoring module configured to monitor whether a 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 collision occurs.
18. The device of claim 17, wherein the monitoring module is further configured to check whether the conflict occurs in a pcode/ucode setting.
CN201980099694.XA 2019-09-27 2019-09-27 Power management method and apparatus Active CN114402272B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/108555 WO2021056416A1 (en) 2019-09-27 2019-09-27 Power management method and apparatus

Publications (2)

Publication Number Publication Date
CN114402272A CN114402272A (en) 2022-04-26
CN114402272B true CN114402272B (en) 2024-03-19

Family

ID=75165033

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201980099694.XA Active CN114402272B (en) 2019-09-27 2019-09-27 Power management method and apparatus

Country Status (2)

Country Link
CN (1) CN114402272B (en)
WO (1) WO2021056416A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101183917A (en) * 2007-12-24 2008-05-21 腾讯科技（深圳）有限公司 Multimedia data coding velocity regulating method and device
CN101477403A (en) * 2009-01-22 2009-07-08 浪潮电子信息产业股份有限公司 Automatic control method for system power consumption
CN108983946A (en) * 2018-06-13 2018-12-11 烽火通信科技股份有限公司 A kind of server energy consumption control method, system and equipment

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030196126A1 (en) * 2002-04-11 2003-10-16 Fung Henry T. System, method, and architecture for dynamic server power management and dynamic workload management for multi-server environment
US8001402B2 (en) * 2007-12-05 2011-08-16 International Business Machines Corporation Method for power capping with co-operative dynamic voltage and frequency scaling via shared p-state table
US8458499B2 (en) * 2009-08-07 2013-06-04 International Business Machines Corporation Method for reducing power state in a computer system out-of-band when a request for reducing the power state is not immediately serviceable in band according to a priority of the request
US10437303B2 (en) * 2016-05-20 2019-10-08 Dell Products L.P. Systems and methods for chassis-level view of information handling system power capping

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101183917A (en) * 2007-12-24 2008-05-21 腾讯科技（深圳）有限公司 Multimedia data coding velocity regulating method and device
CN101477403A (en) * 2009-01-22 2009-07-08 浪潮电子信息产业股份有限公司 Automatic control method for system power consumption
CN108983946A (en) * 2018-06-13 2018-12-11 烽火通信科技股份有限公司 A kind of server energy consumption control method, system and equipment

Also Published As

Publication number Publication date
WO2021056416A1 (en) 2021-04-01
CN114402272A (en) 2022-04-26

Similar Documents

Publication Publication Date Title
US8935563B1 (en) Systems and methods for facilitating substantially continuous availability of multi-tier applications within computer clusters
AU2011299337B2 (en) Controlled automatic healing of data-center services
US8424000B2 (en) Providing application high availability in highly-available virtual machine environments
JP5981020B2 (en) Dynamic interrupt reconfiguration for efficient power management
EP3087503B1 (en) Cloud compute scheduling using a heuristic contention model
US20160306678A1 (en) Automatic Analytical Cloud Scaling of Hardware Using Resource Sub-Cloud
US9547359B2 (en) Dynamic system management communication path selection
US8810584B2 (en) Smart power management in graphics processing unit (GPU) based cluster computing during predictably occurring idle time
US9032414B1 (en) Systems and methods for managing system resources allocated for backup validation
WO2018086467A1 (en) Method, apparatus and system for allocating resources of application clusters under cloud environment
US9952911B2 (en) Dynamically optimized device driver protocol assist threads
US20190018469A1 (en) Method and apparatus for limiting rack power consumption
US20150378782A1 (en) Scheduling of tasks on idle processors without context switching
US9148479B1 (en) Systems and methods for efficiently determining the health of nodes within computer clusters
US9250668B2 (en) Decoupled power and performance allocation in a multiprocessing system
US10114438B2 (en) Dynamic power budgeting in a chassis
US10996942B1 (en) System and method for graphics processing unit firmware updates
US11243603B2 (en) Power management of an event-based processing system
CN114402272B (en) Power management method and apparatus
US9501128B2 (en) Cooperative reduced power mode suspension for high input/output (‘I/O’) workloads
US8312126B2 (en) Managing at least one computer node
US11593121B1 (en) Remotely disabling execution of firmware components
US20190050282A1 (en) Information processing device, information processing method, and non-transitory computer-readable storage medium
US10719107B2 (en) Method and apparatus to maintain node power budget for systems that share a power supply
US11782490B2 (en) Software-defined fail-safe power draw control for rack power distribution units

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant