1. Field of the Invention
The field of the invention is data processing, or, more specifically, methods and products for managing power consumption of a computer and computers for which power consumption is managed.
2. Description of Related Art
The development of the EDVAC computer of 1948 is often cited as the beginning of the computer era. Since that time, computers have evolved into extremely complicated devices. Today's computers are much more sophisticated than early systems such as the EDVAC. Computers typically include a combination of hardware and software components, application programs, operating systems, processors, buses, memory, input/output devices, and so on. As advances in semiconductor processing and computer architecture push the performance of the computer higher and higher, more sophisticated computer software has evolved to take advantage of the higher performance of the hardware, resulting in computers today that are much more powerful than just a few years ago.
Computer systems today may consume a large amount of power and generate a large amount of heat. To control power consumption and heat generation of computers, operating system (‘OS’) and computer processor designers have implemented power management techniques that are carried out by the OS, like the Advanced Configuration and Power Interface (‘ACPI’) modules of most modern operating systems. Such OS-based power management techniques, manage power consumption of a computer in dependence upon the performance of the computer processor. Other power management techniques have been implemented in computers in software not executing as part of the OS. In fact, such non-OS-based power management techniques are typically implemented in software executing on a processor, such as a service processor, that is not the computer's primary processor. Such non-OS-based power management techniques manage power consumption of a computer processor only in dependence measured temperature, current, power values, and the like, not in dependence upon the performance of the computer processor. While both the OS-based and non-OS-based may manage power consumption in one computer concurrently, there is currently no cooperation between such OS-based power management and non-OS-based power management techniques. As such, OS-based and non-OS-based power management techniques often conflict in managing power consumption of the computer system.
Methods and products for managing power consumption of a computer and computers for which power consumption is managed. The computer includes the computer including a computer processor and embodiments of the present invention include providing, by an in-band power manger to an out-of-band power manager, a proposed performance state (‘p-state’) for the computer processor; determining, by the out-of-band power manager, in dependence upon a power setpoint and currently-measured operating metrics of the computer processor, whether to approve the proposed p-state; and if the out-of-band power manager approves the proposed p-state, setting operating parameters of the computer processor according to the approved p-state.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.
Exemplary methods, computers, and products for power management in a computer in accordance with the present invention are described with reference to the accompanying drawings, beginning with
The computer (152) comprises automated computing machinery for which power consumption is managed in accordance with embodiments of the present invention. An example of such automated computing machinery for which power consumption may be managed according to embodiments of the present invention is a blade server. A server, as the term is used in this specification, refers generally to a multi-user computer that provides a service (e.g. database access, file transfer, remote access) or resources (e.g. file space) over a network connection. The term ‘server,’ as context requires, refers inclusively to the server's computer hardware as well as any server application software or operating system software running on the server. A server application is an application program that accepts connections in order to service requests from users by sending back responses. A server application can run on the same computer as the client application using it, or a server application can accept connections through a computer network. Examples of server applications include file server, database server, backup server, print server, mail server, web server, FTP servers, application servers, VPN servers, DHCP servers, DNS servers, WINS servers, logon servers, security servers, domain controllers, backup domain controllers, proxy servers, firewalls, and so on.
Blade servers are self-contained servers, designed for high density. A blade enclosure provides services such as power, cooling, networking, various interconnects and management—though different blade providers have differing principles around what should and should not be included in the blade itself—and sometimes in the enclosure altogether. Together, a set of blade servers installed in a blade enclosure or ‘blade center’ for a blade system. As a practical matter, all computers are implemented with electrical components requiring power that produces heat. Components such as processors, memory, hard drives, power supplies, storage and network connections, keyboards, video components, a mouse, and so on, merely support the basic computing function, yet they all add bulk, heat, complexity, and moving parts that are more prone to failure than solid-state components. In the blade paradigm, most of these functions are removed from the blade computer, being either provided by the blade enclosure (DC power) virtualized (iSCSI storage, remote console over IP), or discarded entirely (serial ports). The blade itself becomes simpler, smaller, and amenable to dense installation with many blade servers in a single blade enclosure.
The computer (152) of
Also stored in RAM (168) is an operating system (154). Operating systems useful for managing power consumption of a computer according to embodiments of the present invention include UNIX™, Linux™, Microsoft XP™, Microsoft Vista™, AIX™, IBM's i5/OS™, and others as will occur to those of skill in the art. The operating system (154) in the example of
The term ‘in-band’ as used in this specification refers to a power manager of a computer that executes on a computer processor for which operating parameters are varied in managing power consumption of the computer according to embodiments of the present invention. For ease of understanding, such computer processor may be though of as a ‘primary,’ ‘main,’ or ‘in-band’ processor that executes user-level software applications, an operating system, and the like. In the computer of
The in-band power manager (132) may determine a p-state to propose in dependence upon performance metrics of a computer processor. Performance metrics (128) of a computer processor (156) are information that describes actual performance of the computer processor. Examples of performance metrics (128) include a measure of computer processor utilization, values of hardware performance counters, and so on as will occur to those of skill in the art. Hardware performance counters, also called hardware counters, are a set of special-purpose registers implemented in many microprocessors to store counts of hardware-related activities within a computer. Examples of counts of hardware-related activities stored in the hardware performance counters include data cache misses, instruction cache, misses, cycles stalled waiting for memory access, cycles with no instruction issued, cycles with maximum instruction issued, and so on as will occur to those of skill in the art.
A performance state (‘p-state’) defines an operational state of a computer processor by specifying a core voltage level for the computer processor and a clock speed of the computer processor. A core voltage of a computer processor is the voltage level of the voltage regulator of the computer processor. P-states may be organized into a number of different levels where lower level p-states generally represent greater performance by a processor, higher core voltage levels, and higher clock speeds, and higher level p-states generally represent lower performance by a processor, lower core voltage levels, and lower clock speeds. The power of a computer processor is proportional to the clock speed and core voltage of the processor. The core voltage of a computer processor then is affected then by variations in clock speed. Readers of skill in the art will immediately that core voltage and clock speed are variable and lowering either value reduces power consumption of the computer processor. When a computer processor is under a low load, as indicated by the performance metrics (128) of the computer processor, the in-band power manager (130) may set the current p-state of the computer processor to a higher p-state, thereby reducing power consumption by the computer processor with very little, if any, reduction in performance by the computer processor. Examples of technologies that vary p-states of a computer processor include Intel's SpeedStep™ technologies, AMD's PowerNow!™ and Cool‘n’Quiet™ technologies, VIA's LongHaul™ technologies, and the like. Readers of skill in the art will recognize that each of these technologies may be improved to be useful for managing power consumption of a computer according to embodiments of the present invention.
In the example of
As mentioned above, the computer (152) of
A service processor (138) is a specialized microcontroller which may be embedded on the motherboard of a computer. Different types of sensors built into a computer report to the service processor on metrics such as temperature, cooling fan speeds, operating system status, and so on. The service processor (138) may monitor the sensors and send alerts to a system administrator via a network if any of the monitored metrics exceed predefined limits, indicating a potential failure of the computer. An administrator may also remotely communicate with a service processor to take corrective action such as resetting or power cycling the computer to get a stalled operating system executing properly.
One example of a service processor is a baseboard management controller (‘BMC’) used in many blade servers. The BMC's basic functions are defined by the Intelligent Platform Management Interface (‘IPMI’) architecture. The BMC may manage an interface between system management software and platform hardware. Physical interfaces to a BMC may include SMBus busses, an RS-232 serial console, address and data lines, and an Intelligent Platform Management Bus (‘IPMB’) that enables the BMC to accept IPMI request messages from other management controllers in the system.
In the example of
Currently-measured operating metrics (134) of the computer processor (156) are measurements of parameters of an operating computer processor. Examples of currently-measured operating metrics (134) of the computer processor (156) include a computer processor's current draw, power usage, case temperature, and so on as will occur to those of skill in the art.
A setpoint is a target value that an out-of-band power manager attempts to achieve through control of the computer processor. A power setpoint is a data structure that defines one or more preferred operating points for a particular operating state (145) of a computer processor. The out-of-band power manager uses the power setpoint to control power consumption, case temperature, and other operating metrics of the computer processor during operation of the processor.
An operating state (145) of a computer processor may be defined by one or more operating parameters of a computer processor, such as core voltage and clock speed of the processor. The out-of-band power manager attempts to achieve the power setpoint by varying the operating state (145) of the computer processor, that is varying operating parameters of the computer processor, throughout operation of the computer processor. ‘Achieving’ a power setpoint as used here means that a currently-measured operating metric of the same type as a preferred operating metric of the power setpoint is approximately equal to that preferred operating metric. Consider, for example, a power setpoint that defines a preferred operating metric for power consumption of computer processor at 10 watts. If the currently-measured operating metric for the power consumption of the computer processor is 10.0001 watts, the currently-measured operating metric is approximately equal to the preferred operating metric defined in the power setpoint and the preferred operating metric for the power setpoint is ‘achieved.’
The out-of-band power manager (132) may vary the operating state dynamically during operation of the computer processor to achieve an optimum combination of power savings, case temperature, and computer processor performance. The out-of-band manger (132) may vary the operating state by calculating and setting a value for any of the operating parameters of the computer processor.
In computers of the prior art having an in-band and out-of-band power manager, there is no cooperation between the in-band and out-of-band power managers. Instead, p-states are set entirely by the in-band power manager in dependence upon only performance metrics, not a power setpoint or currently-measured operating metrics of the computer processor. In computers for which power consumption is managed according to embodiments of the present invention, by contrast, a p-state is proposed by the in-band power manager, in dependence upon the performance metrics, and approved, by the out-of-band power manager, in dependence upon a power setpoint and the currently-measured operating metrics of the computer processor. That is, in computers for which power is managed according to embodiments of the present invention, a p-state is set for a computer processor through cooperation between the in-band and out-of-band power managers in dependence upon more than performance metrics alone.
The out-of-band power manager (132) in the example of
If the out-of-band power manager (132) approves the proposed p-state (204), the system of
The computer (152) of
The example computer (152) of
The exemplary computer (152) of
The arrangement of computers, servers, networks, and other devices making up the exemplary system illustrated in
The method of
The method of
If the out-of-band power manager (132) does not approve the proposed p-state (204), the method of
The method of
For further explanation,
The method of
The method of
The method of
Periodically requesting a current p-state may be useful in reducing communications and processing overhead in embodiments where the out-of-band power manager approves the proposed p-state more often than not. Such embodiments may occur when operating metrics of the computer processor remain in a normal range during operation and computer processor load varies, but not to extremes. Consider, for example, an embodiment in which nine out of every ten proposed p-states is approved. Notifying the in-band power manager of every approval increases communications between the in-band and out-of-band power manager by comparison to only periodically notifying the in-band power manger. In such embodiments the in-band power manager, after providing a proposed p-state, may operate under the assumption that the p-state was approved and implemented by the out-of-band power manager.
As an alternative to notifying (308) the in-band power manager (130) of the approved p-state (226) only when the in-band power manager (130) requests the current p-state, the method of
As yet another alternative to notifying (308) the in-band power manager (130) of the approved p-state (226) only when the in-band power manager (130) requests the current p-state, the method of
Exemplary embodiments of the present invention are described largely in the context of a fully functional computer for managing power consumption of a computer. Readers of skill in the art will recognize, however, that the present invention also may be embodied in a computer program product disposed on signal bearing media for use with any suitable data processing system. Such signal bearing media may be transmission media or recordable media for machine-readable information, including magnetic media, optical media, or other suitable media. Examples of recordable media include magnetic disks in hard drives or diskettes, compact disks for optical drives, magnetic tape, and others as will occur to those of skill in the art. Examples of transmission media include telephone networks for voice communications and digital data communications networks such as, for example, Ethernets™ and networks that communicate with the Internet Protocol and the World Wide Web as well as wireless transmission media such as, for example, networks implemented according to the IEEE 802.11 family of specifications. Persons skilled in the art will immediately recognize that any computer having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a program product. Persons skilled in the art will recognize immediately that, although some of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.
It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.
Number | Name | Date | Kind |
---|---|---|---|
3602703 | Polenz | Aug 1971 | A |
5623450 | Phillips et al. | Apr 1997 | A |
5630148 | Norris | May 1997 | A |
5719800 | Mittal et al. | Feb 1998 | A |
5745375 | Reinhardt et al. | Apr 1998 | A |
5812860 | Horden et al. | Sep 1998 | A |
5941991 | Kageshima | Aug 1999 | A |
6002878 | Gehman et al. | Dec 1999 | A |
6038636 | Brown, III et al. | Mar 2000 | A |
6125334 | Hurd | Sep 2000 | A |
6141021 | Bickford et al. | Oct 2000 | A |
6385113 | Longwell et al. | May 2002 | B1 |
6513145 | Venkitakrishnan | Jan 2003 | B1 |
6624816 | Jones, Jr. | Sep 2003 | B1 |
6628469 | Hoyt | Sep 2003 | B1 |
6657634 | Sinclair et al. | Dec 2003 | B1 |
6661671 | Franke et al. | Dec 2003 | B1 |
6665806 | Shimizu | Dec 2003 | B1 |
6766420 | Rawson, III | Jul 2004 | B2 |
6795896 | Hart | Sep 2004 | B1 |
6820222 | Swoboda | Nov 2004 | B2 |
6862672 | Furudate et al. | Mar 2005 | B1 |
6916815 | Vite et al. | Jul 2005 | B2 |
7002884 | Schmidt et al. | Feb 2006 | B2 |
7010656 | Gupta | Mar 2006 | B2 |
7036030 | Altmejd | Apr 2006 | B1 |
7043647 | Hansen et al. | May 2006 | B2 |
7069463 | Oh | Jun 2006 | B2 |
7134011 | Fung | Nov 2006 | B2 |
7155621 | Dai | Dec 2006 | B2 |
7155623 | Lefurgy et al. | Dec 2006 | B2 |
7219241 | Cooper et al. | May 2007 | B2 |
7240225 | Brewer et al. | Jul 2007 | B2 |
7284067 | Leigh | Oct 2007 | B2 |
7318164 | Rawson, III | Jan 2008 | B2 |
7345689 | Janus et al. | Mar 2008 | B2 |
7353415 | Zaretsky et al. | Apr 2008 | B2 |
7444526 | Felter et al. | Oct 2008 | B2 |
7516348 | Ofer | Apr 2009 | B1 |
7581130 | Carroll et al. | Aug 2009 | B2 |
7607030 | Goodrum et al. | Oct 2009 | B2 |
7788513 | Vaden | Aug 2010 | B2 |
20010032298 | Emons | Oct 2001 | A1 |
20020004912 | Fung | Jan 2002 | A1 |
20020087896 | Cline et al. | Jul 2002 | A1 |
20020133792 | Raghunathan et al. | Sep 2002 | A1 |
20030051104 | Riedel | Mar 2003 | A1 |
20030056125 | O'Conner et al. | Mar 2003 | A1 |
20030105984 | Masuyama et al. | Jun 2003 | A1 |
20030112582 | Sanders et al. | Jun 2003 | A1 |
20030117759 | Cooper | Jun 2003 | A1 |
20030120772 | Husain et al. | Jun 2003 | A1 |
20030125886 | Spitaels et al. | Jul 2003 | A1 |
20030188222 | Abbondanzio et al. | Oct 2003 | A1 |
20030229821 | Ma | Dec 2003 | A1 |
20040003303 | Oehler et al. | Jan 2004 | A1 |
20040024831 | Yang et al. | Feb 2004 | A1 |
20040030939 | Barr et al. | Feb 2004 | A1 |
20040030941 | Barr et al. | Feb 2004 | A1 |
20040148060 | Lee | Jul 2004 | A1 |
20040243886 | Klein | Dec 2004 | A1 |
20040268166 | Farkas et al. | Dec 2004 | A1 |
20050015632 | Chheda et al. | Jan 2005 | A1 |
20050060590 | Bradley et al. | Mar 2005 | A1 |
20050060591 | Yoshiyama et al. | Mar 2005 | A1 |
20050102544 | Brewer et al. | May 2005 | A1 |
20050134593 | Janus et al. | Jun 2005 | A1 |
20050138438 | Bodas | Jun 2005 | A1 |
20050229226 | Relan et al. | Oct 2005 | A1 |
20050244131 | Uehara | Nov 2005 | A1 |
20050262365 | Lint et al. | Nov 2005 | A1 |
20050289361 | Sutardja | Dec 2005 | A1 |
20050289362 | Merkin et al. | Dec 2005 | A1 |
20050289367 | Clark et al. | Dec 2005 | A1 |
20060007203 | Chen et al. | Jan 2006 | A1 |
20060156041 | Zaretsky et al. | Jul 2006 | A1 |
20060161794 | Chiasson et al. | Jul 2006 | A1 |
20060190745 | Matsushima et al. | Aug 2006 | A1 |
20060230299 | Zaretsky et al. | Oct 2006 | A1 |
20060248354 | Pineda De Gyvez et al. | Nov 2006 | A1 |
20060248356 | Won et al. | Nov 2006 | A1 |
20060253715 | Ghiasi et al. | Nov 2006 | A1 |
20070033425 | Clark | Feb 2007 | A1 |
20070073969 | Guha et al. | Mar 2007 | A1 |
20070162632 | Ng et al. | Jul 2007 | A1 |
20070162692 | Nishimoto et al. | Jul 2007 | A1 |
20070162776 | Carpenter et al. | Jul 2007 | A1 |
20070245161 | Shaw et al. | Oct 2007 | A1 |
20070260897 | Cochran et al. | Nov 2007 | A1 |
20080018653 | Liu | Jan 2008 | A1 |
20080077817 | Brundridge et al. | Mar 2008 | A1 |
20080094403 | Bakalash et al. | Apr 2008 | A1 |
20080204460 | Marinkovic et al. | Aug 2008 | A1 |
20080229050 | Tillgren | Sep 2008 | A1 |
20080320203 | Fitzgerald | Dec 2008 | A1 |
20090070611 | Bower et al. | Mar 2009 | A1 |
20090089595 | Brey et al. | Apr 2009 | A1 |
20090132842 | Brey et al. | May 2009 | A1 |
20090235105 | Branover et al. | Sep 2009 | A1 |
Number | Date | Country |
---|---|---|
20 2004 018 289 | Mar 2005 | DE |
WO 2005069148 | Jul 2005 | WO |
WO 2007140404 | Dec 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20090327765 A1 | Dec 2009 | US |