US20080178018A1 - Data structure for budgeting power for multiple devices - Google Patents
Data structure for budgeting power for multiple devices Download PDFInfo
- Publication number
- US20080178018A1 US20080178018A1 US11/655,383 US65538307A US2008178018A1 US 20080178018 A1 US20080178018 A1 US 20080178018A1 US 65538307 A US65538307 A US 65538307A US 2008178018 A1 US2008178018 A1 US 2008178018A1
- Authority
- US
- United States
- Prior art keywords
- power
- devices
- computer
- readable medium
- budget
- 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.)
- Granted
Links
Images
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
- H04L41/344—Out-of-band transfers
Definitions
- a data center may include racks of servers, networking equipment, and other electronic devices. To determine how many devices a data center may handle, a power rating value of the power supply unit of each device may be used. This value is referred to as ‘label power’ and is typically much higher than the maximum power the particular device could ever draw. Using the ‘label power’ results in budgeting too much power for each device, and, as a result, servers may be populated more sparsely than they need to be. Data center floor space is very expensive and this under utilization has a negative effect on the total cost of ownership for the data center.
- aspects of the subject matter described herein relate to a data structure for budgeting power for multiple devices.
- devices are allotted a power budget.
- the devices are each capable of operating at one or more power levels.
- a console queries the devices to obtain the power capabilities of the devices.
- the console stores the power capabilities in a data structure.
- the data structure together with the power budget may then be used to instruct each device to operate at a particular power level.
- the data structure includes fields for storing power levels for the devices as well as fields that associate the power levels with the devices.
- the data structure includes a group field that associates the devices with the power budget.
- FIG. 1 is a block diagram representing an exemplary general-purpose computing environment into which aspects of the subject matter described herein may be incorporated;
- FIG. 2 is a block diagram of an exemplary system in which aspects of the subject matter described herein may operate;
- FIG. 3 illustrates some exemplary data structures that may be used in accordance with aspects of the subject matter described herein;
- FIG. 4 illustrates an exemplary set of data structures that may be used in accordance with aspects of the subject matter described herein;
- FIG. 5 is a flow diagram that generally represents exemplary actions that may occur in creating and using a power data structure in according with aspects of the subject matter described herein;
- FIG. 6 is a flow diagram that generally represents exemplary actions that may occur in using a power data structure in according with aspects of the subject matter described herein.
- FIG. 1 illustrates an example of a suitable computing system environment 100 on which aspects of the subject matter described herein may be implemented.
- the computing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of aspects of the subject matter described herein. Neither should the computing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment 100 .
- aspects of the subject matter described herein are operational with numerous other general purpose or special purpose computing system environments or configurations.
- Examples of well known computing systems, environments, and/or configurations that may be suitable for use with aspects of the subject matter described herein include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microcontroller-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
- aspects of the subject matter described herein may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer.
- program modules include routines, programs, objects, components, data structures, and so forth, which perform particular tasks or implement particular abstract data types.
- aspects of the subject matter described herein may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote computer storage media including memory storage devices.
- an exemplary system for implementing aspects of the subject matter described herein includes a general-purpose computing device in the form of a computer 110 .
- Components of the computer 110 may include, but are not limited to, a processing unit 120 , a system memory 130 , and a system bus 121 that couples various system components including the system memory to the processing unit 120 .
- the system bus 121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.
- ISA Industry Standard Architecture
- MCA Micro Channel Architecture
- EISA Enhanced ISA
- VESA Video Electronics Standards Association
- PCI Peripheral Component Interconnect
- Computer 110 typically includes a variety of computer-readable media.
- Computer-readable media can be any available media that can be accessed by the computer 110 and includes both volatile and nonvolatile media, and removable and non-removable media.
- Computer-readable media may comprise computer storage media and communication media.
- Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 110 .
- Communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.
- the system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132 .
- ROM read only memory
- RAM random access memory
- BIOS basic input/output system
- RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120 .
- FIG. 1 illustrates operating system 134 , application programs 135 , other program modules 136 , and program data 137 .
- the computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media.
- FIG. 1 illustrates a hard disk drive 141 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 151 that reads from or writes to a removable, nonvolatile magnetic disk 152 , and an optical disk drive 155 that reads from or writes to a removable, nonvolatile optical disk 156 such as a CD ROM or other optical media.
- removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like.
- the hard disk drive 141 is typically connected to the system bus 121 through a non-removable memory interface such as interface 140
- magnetic disk drive 151 and optical disk drive 155 are typically connected to the system bus 121 by a removable memory interface, such as interface 150 .
- hard disk drive 141 is illustrated as storing operating system 144 , application programs 145 , other program modules 146 , and program data 147 . Note that these components can either be the same as or different from operating system 134 , application programs 135 , other program modules 136 , and program data 137 . Operating system 144 , application programs 145 , other program modules 146 , and program data 147 are given different numbers herein to illustrate that, at a minimum, they are different copies.
- a user may enter commands and information into the computer 20 through input devices such as a keyboard 162 and pointing device 161 , commonly referred to as a mouse, trackball or touch pad.
- Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, a touch-sensitive screen of a handheld PC or other writing tablet, or the like.
- These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB).
- a monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190 .
- computers may also include other peripheral output devices such as speakers 197 and printer 196 , which may be connected through an output peripheral interface 190 .
- the computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180 .
- the remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110 , although only a memory storage device 181 has been illustrated in FIG. 1 .
- the logical connections depicted in FIG. 1 include a local area network (LAN) 171 and a wide area network (WAN) 173 , but may also include other networks.
- LAN local area network
- WAN wide area network
- Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
- the computer 110 When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170 .
- the computer 110 When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173 , such as the Internet.
- the modem 172 which may be internal or external, may be connected to the system bus 121 via the user input interface 160 or other appropriate mechanism.
- program modules depicted relative to the computer 110 may be stored in the remote memory storage device.
- FIG. 1 illustrates remote application programs 185 as residing on memory device 181 . It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
- a baseboard management controller (e.g., BMC 198 ) may be embedded on the computer 110 to allow the computer 110 to communicate with other devices out-of-band (e.g., without using an operating system).
- the BMC 198 may be able to report temperature, cooling fan speeds, power mode, operating system status, and the like to a console (such as console 205 of FIG. 2 ).
- the BMC 198 may include a processor that is capable of operating at a very low power draw when other components of the computer 110 are turned off.
- the BMC 198 may communicate what power capabilities the computer 110 has and may be able to set the power level of the computer 110 . Power capabilities include the different power level(s) at which the computer 110 is able to operate.
- a data center may include many servers and electronic devices as shown in FIG. 2 .
- the data center needs to be able to supply enough power to the devices and also needs to be able to have enough cooling capacity to keep the devices at a safe operating temperature.
- Many of the devices in a data center may be mounted in racks while other of the devices may be free-standing.
- Each rack may be assigned a particular power budget. For correct operation, the combined power consumed by the devices in a rack should not exceed its assigned power budget. Doing so may cause a breaker to switch off or may cause too much heat which may adversely affect other components in the rack or in other racks. On the other hand, it is beneficial to utilize as much of the budget as needed so that rack and floor space in the data center are not wasted.
- FIG. 2 is a block diagram of an exemplary system in which aspects of the subject matter described herein may operate.
- the system includes a console 205 (e.g., a central management console), racks 210 - 211 , devices 215 - 225 , and communication channels 230 - 231 .
- the devices 215 - 225 may include servers (e.g., servers 215 - 222 ), network devices (e.g., network device 223 ), blade servers (e.g., blade server 225 ), and other devices (e.g., other device 225 ).
- the rack 210 houses the servers 215 - 217 , the network device 223 , and the blade server 225 while the rack 211 houses the servers 218 - 221 and the other device 225 .
- the server 222 may be free-standing and may be located outside of a rack.
- An exemplary device that may be used as a server such as one of servers 215 - 222 is the computer 110 of FIG. 1 configured with appropriate hardware and software.
- a data center may have more or fewer devices like the ones represented in FIG. 2 .
- the communication channel 230 may include one or more networks that connect the devices 215 - 225 to the console 205 and to other devices and or networks such as the Internet (not shown).
- a suitable networking protocol such as the TCP/IP protocol, token ring protocol, or some other network protocol may be used to communicate via the communication channel 230 .
- the communication channel 231 may comprise a network, point-to-point links (e.g., serial connections), or other communication link that allows communication with the devices 215 - 225 “out-of-band.”
- Out-of-band in this sense refers to being able to communicate with the devices without regard to the operating system on the devices 215 - 225 .
- a baseboard management controller may be embedded on a device to allow the console 205 to communicate with the device out-of-band.
- An exemplary BMC e.g., BMC 198
- the BMC may be able to report temperature, cooling fan speeds, power mode, operating system status, and the like to the console 205 .
- the BMC may communicate what power capabilities its corresponding device has and may be able to set the power level of the device. Power capabilities include the different power level(s) at which a device is able to operate.
- the console 205 may store these power capabilities in one or more data structures located on a storage device 235 .
- the storage device 235 may comprise computer-readable media such as the computer-readable media described in conjunction with FIG. 1 , for example. Some exemplary formats of these data structures are described in more detail in conjunction with FIGS. 3 and 4 .
- the one or more data structures (hereinafter sometimes referred to simply as the “data structure”) includes the various power level(s) at which each device is able to operate and includes a way of identifying the device associated with each power level.
- the data structure may associate a location (e.g., rack) with each device.
- the data structure may also include a power budget that is associated with a set of devices. These set of devices may be physically collocated (e.g., in a single rack), or may be spread throughout a data center.
- the data structure does not include information regarding how the devices are able to implement a power level.
- the data structure may not include what components a device powers on or off or places in an increased or reduced power state to achieve a power level. Instead, the data structure may simply include the power levels at which the device is capable of operating. In other words, the details of which components are running in which power modes on a particular server are transparent to a console using the data structure.
- omitting power information about components of each device provides flexibility to describe new power levels that may be introduced in the future. For example, a data structure that was structured to obtain power information about a pre-determined set of hardware may not work properly if new hardware is developed.
- having the device determine which components to place in a different power state based on a console commanded power level allows device manufacturers to cause their devices to operate within certain tested configurations.
- the power management software on the console 205 may accurately determine how much power is needed by a set of devices and how much power from a budget is remaining for a set of devices. Where location information is included, the power management software may determine whether additional devices may be added to a set of devices (e.g., on a rack) and still consume less power than the power budget allocated to the set of devices.
- a device may be instructed to operate at a supported power level by sending a command to the device to operate at the power level. In one embodiment, if the device is under control of an operating system, this may be done through the communication channel 230 by communicating with the operating system (or software executing thereon). In another embodiment, this may be done out-of-band via the communication channel 231 regardless of whether the device is under control of an operating system.
- the device receives the command, it determines which components to power on or off or to reduce or increase in power consumption to meet the power level specified by the command. For example, when operating above its minimum power consumption, a CPU may be instructed to decrease its power consumption.
- FIG. 3 illustrates some exemplary data structures that may be used in accordance with aspects of the subject matter described herein.
- the data structure 300 includes a server ID field 305 , a power profile field 310 , and a power level field 315 .
- the power level field 315 indicates a maximum power that the device may consume when assigned to its associated power profile
- the server ID field 305 includes entries that associate the power levels with devices. These entries may include unique identifiers that identify the devices.
- the power profile field 310 may be omitted from the data structure 300 .
- a device may be instructed to operate at a power no greater than a particular power level by sending the power level to the device.
- the titles of each field and the title of the data structure itself are optional and need not be stored in the data structure.
- the data structure 300 includes an entry for each power level of each device for which power budgeting is desired.
- another field may be added to or associated with the data structure 300 that includes a location (e.g., rack number, physical location as indicated, for example, by coordinates, etc.) or grouping of devices that are affected by a common power budget. This field may be used in conjunction with a power budget data structure 320 to allocate power to each device in the group.
- the power budget data structure 320 may include the power budget for all collections of devices in a data center.
- a data structure may also be used to indicate the power profiles that are currently active on the devices.
- the data structure may include a device ID field and a power profile field for each device. This data structure may be used in conjunction with the power capabilities data structure 300 to determine the current power level for each device, for example.
- FIG. 4 illustrates an exemplary set of data structures that may be used in accordance with aspects of the subject matter described herein.
- the data structures 405 - 415 correspond to three separate devices and include information that indicates the power capabilities of each of the devices.
- the data structures 405 - 415 may be stored in such a way as to indicate with which device they are associated.
- the data structures 405 - 415 may each be stored together with an identifier that identifies their respective devices.
- they may be stored in an object oriented database that includes a single device identifier for each data structure to identify its associated device.
- an additional field or data item may be associated with each data structure. This additional field or data item may be used to identify a set of devices that are governed by the same power budget.
- FIG. 5 is a flow diagram that generally represents exemplary actions that may occur in creating and using a power data structure in according with aspects of the subject matter described herein. At block 505 , the actions begin.
- a power budget for a set of devices is obtained.
- the console 205 may obtain the power budget for the rack 210 .
- the devices are queried for their power capabilities.
- the console 205 queries the servers 215 - 217 , the network device 223 , and the blade server 225 for their power capabilities.
- the console 205 may query each device individually through an out-of-band or in-band connection.
- a power capability includes a power level at which a device is capable of operating.
- the power capabilities of the devices are received.
- the console 205 receives the power capabilities from the servers 215 - 217 , the network device 223 , and the blade server 225 .
- these power capabilities are stored in a data structure.
- the power capabilities data structure 300 is stored on the storage device 235 .
- the data structure is used to instruct devices to operate at a particular power level.
- the console 205 instructs each of the servers 215 - 217 , the network device 223 , and the blade server 225 to operate at particular power levels.
- the power level from device to device may be different even if the devices are similar or identical.
- FIG. 6 is a flow diagram that generally represents exemplary actions that may occur in using a power data structure in according with aspects of the subject matter described herein. At block 605 , the actions begin.
- power capabilities of devices are obtained from the data structure. For example, referring to FIG. 4 , the power capabilities from the data structures 405 - 415 are obtained.
- the power budget for the devices is obtained.
- the console 205 obtains the power budget from a data store (e.g., the storage 235 ) or a user.
- the remaining power left in a power budget after accounting for power consumed by the devices is determined. For example, referring to FIG. 2 , the console 205 determines what power is remaining (if any) or by how much the power is exceeded after accounting for the power consumed by the devices in the rack 210 .
- action is taken based on the power capabilities and the power budget.
- This action may include, for example, instructing one or more devices to operate at specified power levels, indicating how much power is remaining of a power budget, determining where a new device can be placed (based on remaining power budget), determining a device that needs to be moved to another power budget, and so forth.
Abstract
Description
- A data center may include racks of servers, networking equipment, and other electronic devices. To determine how many devices a data center may handle, a power rating value of the power supply unit of each device may be used. This value is referred to as ‘label power’ and is typically much higher than the maximum power the particular device could ever draw. Using the ‘label power’ results in budgeting too much power for each device, and, as a result, servers may be populated more sparsely than they need to be. Data center floor space is very expensive and this under utilization has a negative effect on the total cost of ownership for the data center.
- Briefly, aspects of the subject matter described herein relate to a data structure for budgeting power for multiple devices. In aspects, devices are allotted a power budget. The devices are each capable of operating at one or more power levels. A console queries the devices to obtain the power capabilities of the devices. The console stores the power capabilities in a data structure. The data structure together with the power budget may then be used to instruct each device to operate at a particular power level. The data structure includes fields for storing power levels for the devices as well as fields that associate the power levels with the devices. In addition, the data structure includes a group field that associates the devices with the power budget.
- This Summary is provided to briefly identify some aspects of the subject matter that is further described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
- The phrase “subject matter described herein” refers to subject matter described in the Detailed Description unless the context clearly indicates otherwise. The term “aspects” should be read as “at least one aspect.” Identifying aspects of the subject matter described in the Detailed Description is not intended to identify key or essential features of the claimed subject matter.
- The aspects described above and other aspects of the subject matter described herein are illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which:
-
FIG. 1 is a block diagram representing an exemplary general-purpose computing environment into which aspects of the subject matter described herein may be incorporated; -
FIG. 2 is a block diagram of an exemplary system in which aspects of the subject matter described herein may operate; -
FIG. 3 illustrates some exemplary data structures that may be used in accordance with aspects of the subject matter described herein; -
FIG. 4 illustrates an exemplary set of data structures that may be used in accordance with aspects of the subject matter described herein; -
FIG. 5 is a flow diagram that generally represents exemplary actions that may occur in creating and using a power data structure in according with aspects of the subject matter described herein; -
FIG. 6 is a flow diagram that generally represents exemplary actions that may occur in using a power data structure in according with aspects of the subject matter described herein. -
FIG. 1 illustrates an example of a suitablecomputing system environment 100 on which aspects of the subject matter described herein may be implemented. Thecomputing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of aspects of the subject matter described herein. Neither should thecomputing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in theexemplary operating environment 100. - Aspects of the subject matter described herein are operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with aspects of the subject matter described herein include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microcontroller-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
- Aspects of the subject matter described herein may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and so forth, which perform particular tasks or implement particular abstract data types. Aspects of the subject matter described herein may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
- With reference to
FIG. 1 , an exemplary system for implementing aspects of the subject matter described herein includes a general-purpose computing device in the form of acomputer 110. Components of thecomputer 110 may include, but are not limited to, aprocessing unit 120, asystem memory 130, and asystem bus 121 that couples various system components including the system memory to theprocessing unit 120. Thesystem bus 121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus. -
Computer 110 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by thecomputer 110 and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by thecomputer 110. Communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media. - The
system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements withincomputer 110, such as during start-up, is typically stored in ROM 131.RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on byprocessing unit 120. By way of example, and not limitation,FIG. 1 illustratesoperating system 134,application programs 135,other program modules 136, andprogram data 137. - The
computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,FIG. 1 illustrates ahard disk drive 141 that reads from or writes to non-removable, nonvolatile magnetic media, amagnetic disk drive 151 that reads from or writes to a removable, nonvolatilemagnetic disk 152, and anoptical disk drive 155 that reads from or writes to a removable, nonvolatileoptical disk 156 such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. Thehard disk drive 141 is typically connected to thesystem bus 121 through a non-removable memory interface such asinterface 140, andmagnetic disk drive 151 andoptical disk drive 155 are typically connected to thesystem bus 121 by a removable memory interface, such asinterface 150. - The drives and their associated computer storage media, discussed above and illustrated in
FIG. 1 , provide storage of computer-readable instructions, data structures, program modules, and other data for thecomputer 110. InFIG. 1 , for example,hard disk drive 141 is illustrated as storingoperating system 144,application programs 145,other program modules 146, andprogram data 147. Note that these components can either be the same as or different fromoperating system 134,application programs 135,other program modules 136, andprogram data 137.Operating system 144,application programs 145,other program modules 146, andprogram data 147 are given different numbers herein to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer 20 through input devices such as akeyboard 162 and pointingdevice 161, commonly referred to as a mouse, trackball or touch pad. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, a touch-sensitive screen of a handheld PC or other writing tablet, or the like. These and other input devices are often connected to theprocessing unit 120 through auser input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). Amonitor 191 or other type of display device is also connected to thesystem bus 121 via an interface, such as avideo interface 190. In addition to the monitor, computers may also include other peripheral output devices such asspeakers 197 andprinter 196, which may be connected through an outputperipheral interface 190. - The
computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as aremote computer 180. Theremote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to thecomputer 110, although only amemory storage device 181 has been illustrated inFIG. 1 . The logical connections depicted inFIG. 1 include a local area network (LAN) 171 and a wide area network (WAN) 173, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet. - When used in a LAN networking environment, the
computer 110 is connected to theLAN 171 through a network interface oradapter 170. When used in a WAN networking environment, thecomputer 110 typically includes amodem 172 or other means for establishing communications over theWAN 173, such as the Internet. Themodem 172, which may be internal or external, may be connected to thesystem bus 121 via theuser input interface 160 or other appropriate mechanism. In a networked environment, program modules depicted relative to thecomputer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,FIG. 1 illustratesremote application programs 185 as residing onmemory device 181. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. - A baseboard management controller (e.g., BMC 198) may be embedded on the
computer 110 to allow thecomputer 110 to communicate with other devices out-of-band (e.g., without using an operating system). TheBMC 198 may be able to report temperature, cooling fan speeds, power mode, operating system status, and the like to a console (such asconsole 205 ofFIG. 2 ). TheBMC 198 may include a processor that is capable of operating at a very low power draw when other components of thecomputer 110 are turned off. In addition, theBMC 198 may communicate what power capabilities thecomputer 110 has and may be able to set the power level of thecomputer 110. Power capabilities include the different power level(s) at which thecomputer 110 is able to operate. - A data center may include many servers and electronic devices as shown in
FIG. 2 . The data center needs to be able to supply enough power to the devices and also needs to be able to have enough cooling capacity to keep the devices at a safe operating temperature. Many of the devices in a data center may be mounted in racks while other of the devices may be free-standing. Each rack may be assigned a particular power budget. For correct operation, the combined power consumed by the devices in a rack should not exceed its assigned power budget. Doing so may cause a breaker to switch off or may cause too much heat which may adversely affect other components in the rack or in other racks. On the other hand, it is beneficial to utilize as much of the budget as needed so that rack and floor space in the data center are not wasted. -
FIG. 2 is a block diagram of an exemplary system in which aspects of the subject matter described herein may operate. The system includes a console 205 (e.g., a central management console), racks 210-211, devices 215-225, and communication channels 230-231. - The devices 215-225 may include servers (e.g., servers 215-222), network devices (e.g., network device 223), blade servers (e.g., blade server 225), and other devices (e.g., other device 225). The
rack 210 houses the servers 215-217, thenetwork device 223, and theblade server 225 while therack 211 houses the servers 218-221 and theother device 225. Theserver 222 may be free-standing and may be located outside of a rack. An exemplary device that may be used as a server such as one of servers 215-222 is thecomputer 110 ofFIG. 1 configured with appropriate hardware and software. A data center may have more or fewer devices like the ones represented inFIG. 2 . - The
communication channel 230 may include one or more networks that connect the devices 215-225 to theconsole 205 and to other devices and or networks such as the Internet (not shown). A suitable networking protocol such as the TCP/IP protocol, token ring protocol, or some other network protocol may be used to communicate via thecommunication channel 230. - The
communication channel 231 may comprise a network, point-to-point links (e.g., serial connections), or other communication link that allows communication with the devices 215-225 “out-of-band.” Out-of-band in this sense refers to being able to communicate with the devices without regard to the operating system on the devices 215-225. - In one embodiment, a baseboard management controller (BMC) may be embedded on a device to allow the
console 205 to communicate with the device out-of-band. An exemplary BMC (e.g., BMC 198) is described in conjunction withFIG. 1 . As described previously, the BMC may be able to report temperature, cooling fan speeds, power mode, operating system status, and the like to theconsole 205. In addition, the BMC may communicate what power capabilities its corresponding device has and may be able to set the power level of the device. Power capabilities include the different power level(s) at which a device is able to operate. - The
console 205 may store these power capabilities in one or more data structures located on astorage device 235. Thestorage device 235 may comprise computer-readable media such as the computer-readable media described in conjunction withFIG. 1 , for example. Some exemplary formats of these data structures are described in more detail in conjunction withFIGS. 3 and 4 . In general, the one or more data structures (hereinafter sometimes referred to simply as the “data structure”) includes the various power level(s) at which each device is able to operate and includes a way of identifying the device associated with each power level. In addition, the data structure may associate a location (e.g., rack) with each device. The data structure may also include a power budget that is associated with a set of devices. These set of devices may be physically collocated (e.g., in a single rack), or may be spread throughout a data center. - In one embodiment, the data structure does not include information regarding how the devices are able to implement a power level. For example, the data structure may not include what components a device powers on or off or places in an increased or reduced power state to achieve a power level. Instead, the data structure may simply include the power levels at which the device is capable of operating. In other words, the details of which components are running in which power modes on a particular server are transparent to a console using the data structure.
- As used herein, when a device is operating at a power level, this does not necessarily mean that the device consumes the entire amount of the power level at all times. Rather, it means that the device is expected to consume no more than the power level. The device may consume less power when it has less work to do, for example. When the device is fully loaded with work to do, it should not (but may accidentally) consume more power than the power level at which it is operating.
- In this embodiment, omitting power information about components of each device provides flexibility to describe new power levels that may be introduced in the future. For example, a data structure that was structured to obtain power information about a pre-determined set of hardware may not work properly if new hardware is developed. In addition, having the device determine which components to place in a different power state based on a console commanded power level allows device manufacturers to cause their devices to operate within certain tested configurations.
- Using the data structure, the power management software on the console 205 (or on any other machine capable of accessing the storage device 235) may accurately determine how much power is needed by a set of devices and how much power from a budget is remaining for a set of devices. Where location information is included, the power management software may determine whether additional devices may be added to a set of devices (e.g., on a rack) and still consume less power than the power budget allocated to the set of devices.
- A device may be instructed to operate at a supported power level by sending a command to the device to operate at the power level. In one embodiment, if the device is under control of an operating system, this may be done through the
communication channel 230 by communicating with the operating system (or software executing thereon). In another embodiment, this may be done out-of-band via thecommunication channel 231 regardless of whether the device is under control of an operating system. When the device receives the command, it determines which components to power on or off or to reduce or increase in power consumption to meet the power level specified by the command. For example, when operating above its minimum power consumption, a CPU may be instructed to decrease its power consumption. -
FIG. 3 illustrates some exemplary data structures that may be used in accordance with aspects of the subject matter described herein. Thedata structure 300 includes aserver ID field 305, apower profile field 310, and apower level field 315. Thepower level field 315 indicates a maximum power that the device may consume when assigned to its associated power profile Theserver ID field 305 includes entries that associate the power levels with devices. These entries may include unique identifiers that identify the devices. - In one embodiment, the
power profile field 310 may be omitted from thedata structure 300. In this embodiment, a device may be instructed to operate at a power no greater than a particular power level by sending the power level to the device. - The titles of each field and the title of the data structure itself are optional and need not be stored in the data structure.
- The
data structure 300 includes an entry for each power level of each device for which power budgeting is desired. In another embodiment, another field may be added to or associated with thedata structure 300 that includes a location (e.g., rack number, physical location as indicated, for example, by coordinates, etc.) or grouping of devices that are affected by a common power budget. This field may be used in conjunction with a powerbudget data structure 320 to allocate power to each device in the group. In one embodiment, the powerbudget data structure 320 may include the power budget for all collections of devices in a data center. - A data structure (not shown) may also be used to indicate the power profiles that are currently active on the devices. In one embodiment, the data structure may include a device ID field and a power profile field for each device. This data structure may be used in conjunction with the power
capabilities data structure 300 to determine the current power level for each device, for example. -
FIG. 4 illustrates an exemplary set of data structures that may be used in accordance with aspects of the subject matter described herein. The data structures 405-415 correspond to three separate devices and include information that indicates the power capabilities of each of the devices. The data structures 405-415 may be stored in such a way as to indicate with which device they are associated. For example, the data structures 405-415 may each be stored together with an identifier that identifies their respective devices. As another example, they may be stored in an object oriented database that includes a single device identifier for each data structure to identify its associated device. - In addition, an additional field or data item may be associated with each data structure. This additional field or data item may be used to identify a set of devices that are governed by the same power budget.
- It will be recognized by those skilled in the art that there are many ways in which to create data structures that identify power capabilities of devices. There are also many ways of associating each data structure with a particular device. To be operable with aspects of the subject matter described herein, the information that is needed is the power levels of each device and a mechanism for identifying a particular device for a given power level. As long as this needed information is available, any of these ways may be used without departing from the spirit or scope of the subject matter described herein.
-
FIG. 5 is a flow diagram that generally represents exemplary actions that may occur in creating and using a power data structure in according with aspects of the subject matter described herein. Atblock 505, the actions begin. - At
block 510, a power budget for a set of devices is obtained. For example, referring toFIG. 2 , theconsole 205 may obtain the power budget for therack 210. - At
block 515, the devices are queried for their power capabilities. For example, referring toFIG. 2 , theconsole 205 queries the servers 215-217, thenetwork device 223, and theblade server 225 for their power capabilities. Theconsole 205 may query each device individually through an out-of-band or in-band connection. A power capability includes a power level at which a device is capable of operating. - At
block 520, the power capabilities of the devices are received. For example, referring toFIG. 2 , theconsole 205 receives the power capabilities from the servers 215-217, thenetwork device 223, and theblade server 225. - At
block 525, these power capabilities are stored in a data structure. For example, referring toFIGS. 2 and 3 , the powercapabilities data structure 300 is stored on thestorage device 235. - At
block 530, the data structure is used to instruct devices to operate at a particular power level. For example, referring toFIG. 2 , theconsole 205 instructs each of the servers 215-217, thenetwork device 223, and theblade server 225 to operate at particular power levels. The power level from device to device may be different even if the devices are similar or identical. - At
block 535, the actions end. -
FIG. 6 is a flow diagram that generally represents exemplary actions that may occur in using a power data structure in according with aspects of the subject matter described herein. Atblock 605, the actions begin. - At
block 610, power capabilities of devices are obtained from the data structure. For example, referring toFIG. 4 , the power capabilities from the data structures 405-415 are obtained. - At
block 615, the power budget for the devices is obtained. For example, referring toFIG. 2 , theconsole 205 obtains the power budget from a data store (e.g., the storage 235) or a user. - At
block 620, the remaining power left in a power budget after accounting for power consumed by the devices is determined. For example, referring toFIG. 2 , theconsole 205 determines what power is remaining (if any) or by how much the power is exceeded after accounting for the power consumed by the devices in therack 210. - AT
block 625, action is taken based on the power capabilities and the power budget. This action may include, for example, instructing one or more devices to operate at specified power levels, indicating how much power is remaining of a power budget, determining where a new device can be placed (based on remaining power budget), determining a device that needs to be moved to another power budget, and so forth. - At
block 630, the actions end. - As can be seen from the foregoing detailed description, aspects have been described related to a data structure for budgeting power for multiple devices. While aspects of the subject matter described herein are susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit aspects of the claimed subject matter to the specific forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of various aspects of the subject matter described herein.
Claims (20)
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/655,383 US7793120B2 (en) | 2007-01-19 | 2007-01-19 | Data structure for budgeting power for multiple devices |
CN2008800026358A CN101589574B (en) | 2007-01-19 | 2008-01-04 | Data structure for budgeting power for multiple devices |
EP08713569A EP2127212A4 (en) | 2007-01-19 | 2008-01-04 | Data structure for budgeting power for multiple devices |
JP2009546458A JP2010517142A (en) | 2007-01-19 | 2008-01-04 | Data structure for allocating power to multiple devices |
PCT/US2008/050294 WO2008088951A1 (en) | 2007-01-19 | 2008-01-04 | Data structure for budgeting power for multiple devices |
TW097101253A TWI360753B (en) | 2007-01-19 | 2008-01-11 | Data structure for budgeting power for multiple de |
JP2012005657U JP3180006U (en) | 2007-01-19 | 2012-09-18 | Power management equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/655,383 US7793120B2 (en) | 2007-01-19 | 2007-01-19 | Data structure for budgeting power for multiple devices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20080178018A1 true US20080178018A1 (en) | 2008-07-24 |
US7793120B2 US7793120B2 (en) | 2010-09-07 |
Family
ID=39636331
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/655,383 Active 2029-07-09 US7793120B2 (en) | 2007-01-19 | 2007-01-19 | Data structure for budgeting power for multiple devices |
Country Status (6)
Country | Link |
---|---|
US (1) | US7793120B2 (en) |
EP (1) | EP2127212A4 (en) |
JP (2) | JP2010517142A (en) |
CN (1) | CN101589574B (en) |
TW (1) | TWI360753B (en) |
WO (1) | WO2008088951A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080313492A1 (en) * | 2007-06-12 | 2008-12-18 | Hansen Peter A | Adjusting a Cooling Device and a Server in Response to a Thermal Event |
US20100292854A1 (en) * | 2009-05-13 | 2010-11-18 | Microsoft Corporation | Integrating energy budgets for power management |
US7861102B1 (en) * | 2007-04-30 | 2010-12-28 | Hewlett-Packard Development Company, L.P. | Unified power management architecture |
US20120136484A1 (en) * | 2010-11-30 | 2012-05-31 | Inventec Corporation | Data center |
US20120209442A1 (en) * | 2011-02-11 | 2012-08-16 | General Electric Company | Methods and apparatuses for managing peak loads for a customer location |
US20140006815A1 (en) * | 2012-06-28 | 2014-01-02 | Enrique G. Castro-Leon | Power management control of remote servers |
US20140189298A1 (en) * | 2012-12-27 | 2014-07-03 | Teresa Morrison | Configurable ring network |
US10067547B2 (en) | 2012-06-28 | 2018-09-04 | Intel Corporation | Power management control of remote servers |
US20220134250A1 (en) * | 2019-06-23 | 2022-05-05 | Andrew David Hospodor | Method and Apparatus for Sharing Co-Generated Energy When Processing Essential Elements from Plant Matter |
US11700082B1 (en) * | 2019-07-23 | 2023-07-11 | Cable Television Laboratories, Inc. | Systems and methods for proactive network maintenance |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7996690B2 (en) * | 2008-01-24 | 2011-08-09 | Dell Products L.P. | System and method for dynamic utilization-based power allocation in a modular information handling system |
US8996890B2 (en) * | 2008-02-07 | 2015-03-31 | Dell Products L.P. | Method for power conservation in virtualized environments |
CN101515161A (en) * | 2008-02-18 | 2009-08-26 | 国际商业机器公司 | Centralized energy management method and system |
JP5239796B2 (en) * | 2008-12-03 | 2013-07-17 | 日本電気株式会社 | Rack mount system, rack apparatus, and rack apparatus control method |
US9032129B2 (en) * | 2009-10-14 | 2015-05-12 | Silicon Laboratories Norway As | Advanced energy profiler |
EP2403183B1 (en) * | 2010-06-30 | 2013-01-02 | Alcatel Lucent | Method for managing power consumption in a communication network |
CN102323852B (en) * | 2011-08-22 | 2014-03-26 | 迈普通信技术股份有限公司 | Modular power supply and device for testing state and power of modular power supply and method |
WO2013101180A1 (en) * | 2011-12-30 | 2013-07-04 | Intel Corporation | Pcie device power state control |
US8930736B2 (en) | 2012-03-01 | 2015-01-06 | Microsoft Corporation | Inferred electrical power consumption of computing devices |
US9207744B2 (en) | 2012-10-18 | 2015-12-08 | Huawei Technologies Co., Ltd. | Method and apparatus for adjusting device power consumption |
CN102916835B (en) * | 2012-10-18 | 2015-09-09 | 华为技术有限公司 | A kind of method and device adjusting equipment power dissipation |
US9606783B2 (en) | 2013-10-14 | 2017-03-28 | International Business Machines Corporation | Dynamic code selection based on data policies |
US9483094B2 (en) | 2014-02-11 | 2016-11-01 | Microsoft Technology Licensing, Llc | Backup power management for computing systems |
US9874922B2 (en) * | 2015-02-17 | 2018-01-23 | Intel Corporation | Performing dynamic power control of platform devices |
CN109753138B (en) * | 2018-12-14 | 2021-10-08 | 新华三技术有限公司 | Power consumption management method and device, electronic equipment and computer readable storage medium |
Citations (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5483656A (en) * | 1993-01-14 | 1996-01-09 | Apple Computer, Inc. | System for managing power consumption of devices coupled to a common bus |
US5532945A (en) * | 1994-06-17 | 1996-07-02 | Intel Corporation | Power budgetting in a computer system having removable devices |
US5560022A (en) * | 1994-07-19 | 1996-09-24 | Intel Corporation | Power management coordinator system and interface |
US5694607A (en) * | 1994-12-22 | 1997-12-02 | Intel Corporation | System power consumption tracking and reporting |
US5919264A (en) * | 1997-03-03 | 1999-07-06 | Microsoft Corporation | System and method for using data structures to share a plurality of power resources among a plurality of devices |
US5964879A (en) * | 1994-12-22 | 1999-10-12 | Intel Corporation | Method and system for dynamically power budgeting with device specific characterization of power consumption using device driver programs |
US6498460B1 (en) * | 2001-12-14 | 2002-12-24 | Compaq Information Technologies Group, L.P. | Prioritization-based power management protocol in a computer system |
US20030037150A1 (en) * | 2001-07-31 | 2003-02-20 | Nakagawa O. Sam | System and method for quality of service based server cluster power management |
US6651178B1 (en) * | 2000-02-29 | 2003-11-18 | 3Com Corporation | Communication module having power supply requirement identification |
US6859882B2 (en) * | 1990-06-01 | 2005-02-22 | Amphus, Inc. | System, method, and architecture for dynamic server power management and dynamic workload management for multi-server environment |
US20050091550A1 (en) * | 2000-12-13 | 2005-04-28 | Matsushita Electric Industrial Co., Ltd. | Power control device for processor |
US6986069B2 (en) * | 2002-07-01 | 2006-01-10 | Newisys, Inc. | Methods and apparatus for static and dynamic power management of computer systems |
US20060082222A1 (en) * | 2002-10-15 | 2006-04-20 | David Pincu | Rack level power management |
US7043647B2 (en) * | 2001-09-28 | 2006-05-09 | Hewlett-Packard Development Company, L.P. | Intelligent power management for a rack of servers |
US7051215B2 (en) * | 2003-06-13 | 2006-05-23 | Intel Corporation | Power management for clustered computing platforms |
US7058828B2 (en) * | 2002-08-12 | 2006-06-06 | Hewlett-Packard Development Company, L.P. | System, method and apparatus for the frequency management of blades in a bladed architecture based on performance requirements |
US20060136754A1 (en) * | 2004-12-16 | 2006-06-22 | Dell Products L.P. | Power-on management for remote power-on signals to high density server module |
US20080133946A1 (en) * | 2004-05-20 | 2008-06-05 | Cisco Technology, Inc. | Methods and apparatus for provisioning phantom power to remote devices |
US7493503B2 (en) * | 2005-12-22 | 2009-02-17 | International Business Machines Corporation | Programmable throttling in blade/chassis power management |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3362127B2 (en) * | 2000-04-28 | 2003-01-07 | 京セラミタ株式会社 | Power saving mode control system, server machine |
JP2002142385A (en) * | 2000-10-30 | 2002-05-17 | Canon Inc | Server device, network equipment, network system, and control method therefor |
US20030055969A1 (en) | 2001-09-17 | 2003-03-20 | International Business Machines Corporation | System and method for performing power management on a distributed system |
JP2003263249A (en) * | 2002-03-11 | 2003-09-19 | Yamaha Corp | Power supply management apparatus and system having power saving mode |
US7272732B2 (en) * | 2003-06-30 | 2007-09-18 | Hewlett-Packard Development Company, L.P. | Controlling power consumption of at least one computer system |
JP2005202506A (en) * | 2004-01-13 | 2005-07-28 | Hitachi Ltd | Power management system in blade server |
JP2005312142A (en) * | 2004-04-20 | 2005-11-04 | Hitachi Ltd | Power consumption management system |
JP4543780B2 (en) * | 2004-06-25 | 2010-09-15 | 日本電気株式会社 | Power management system, power management method and program |
US20060156041A1 (en) * | 2005-01-07 | 2006-07-13 | Lee Zaretsky | System and method for power management of plural information handling systems |
US7386743B2 (en) | 2005-06-09 | 2008-06-10 | International Business Machines Corporation | Power-managed server and method for managing power consumption |
-
2007
- 2007-01-19 US US11/655,383 patent/US7793120B2/en active Active
-
2008
- 2008-01-04 JP JP2009546458A patent/JP2010517142A/en active Pending
- 2008-01-04 WO PCT/US2008/050294 patent/WO2008088951A1/en active Application Filing
- 2008-01-04 CN CN2008800026358A patent/CN101589574B/en active Active
- 2008-01-04 EP EP08713569A patent/EP2127212A4/en not_active Ceased
- 2008-01-11 TW TW097101253A patent/TWI360753B/en not_active IP Right Cessation
-
2012
- 2012-09-18 JP JP2012005657U patent/JP3180006U/en not_active Expired - Lifetime
Patent Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6859882B2 (en) * | 1990-06-01 | 2005-02-22 | Amphus, Inc. | System, method, and architecture for dynamic server power management and dynamic workload management for multi-server environment |
US5483656A (en) * | 1993-01-14 | 1996-01-09 | Apple Computer, Inc. | System for managing power consumption of devices coupled to a common bus |
US5532945A (en) * | 1994-06-17 | 1996-07-02 | Intel Corporation | Power budgetting in a computer system having removable devices |
US5560022A (en) * | 1994-07-19 | 1996-09-24 | Intel Corporation | Power management coordinator system and interface |
US5694607A (en) * | 1994-12-22 | 1997-12-02 | Intel Corporation | System power consumption tracking and reporting |
US5964879A (en) * | 1994-12-22 | 1999-10-12 | Intel Corporation | Method and system for dynamically power budgeting with device specific characterization of power consumption using device driver programs |
US5919264A (en) * | 1997-03-03 | 1999-07-06 | Microsoft Corporation | System and method for using data structures to share a plurality of power resources among a plurality of devices |
US6651178B1 (en) * | 2000-02-29 | 2003-11-18 | 3Com Corporation | Communication module having power supply requirement identification |
US20050091550A1 (en) * | 2000-12-13 | 2005-04-28 | Matsushita Electric Industrial Co., Ltd. | Power control device for processor |
US20030037150A1 (en) * | 2001-07-31 | 2003-02-20 | Nakagawa O. Sam | System and method for quality of service based server cluster power management |
US6990593B2 (en) * | 2001-07-31 | 2006-01-24 | Hewlett-Packard Development Company, L.P. | Method for diverting power reserves and shifting activities according to activity priorities in a server cluster in the event of a power interruption |
US7043647B2 (en) * | 2001-09-28 | 2006-05-09 | Hewlett-Packard Development Company, L.P. | Intelligent power management for a rack of servers |
US6498460B1 (en) * | 2001-12-14 | 2002-12-24 | Compaq Information Technologies Group, L.P. | Prioritization-based power management protocol in a computer system |
US6986069B2 (en) * | 2002-07-01 | 2006-01-10 | Newisys, Inc. | Methods and apparatus for static and dynamic power management of computer systems |
US7058828B2 (en) * | 2002-08-12 | 2006-06-06 | Hewlett-Packard Development Company, L.P. | System, method and apparatus for the frequency management of blades in a bladed architecture based on performance requirements |
US20060082222A1 (en) * | 2002-10-15 | 2006-04-20 | David Pincu | Rack level power management |
US7051215B2 (en) * | 2003-06-13 | 2006-05-23 | Intel Corporation | Power management for clustered computing platforms |
US20080133946A1 (en) * | 2004-05-20 | 2008-06-05 | Cisco Technology, Inc. | Methods and apparatus for provisioning phantom power to remote devices |
US20060136754A1 (en) * | 2004-12-16 | 2006-06-22 | Dell Products L.P. | Power-on management for remote power-on signals to high density server module |
US7493503B2 (en) * | 2005-12-22 | 2009-02-17 | International Business Machines Corporation | Programmable throttling in blade/chassis power management |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7861102B1 (en) * | 2007-04-30 | 2010-12-28 | Hewlett-Packard Development Company, L.P. | Unified power management architecture |
US20080313492A1 (en) * | 2007-06-12 | 2008-12-18 | Hansen Peter A | Adjusting a Cooling Device and a Server in Response to a Thermal Event |
US9261933B2 (en) | 2009-05-13 | 2016-02-16 | Microsoft Technology Licensing, Llc | Integrating energy budgets for power management |
US20100292854A1 (en) * | 2009-05-13 | 2010-11-18 | Microsoft Corporation | Integrating energy budgets for power management |
US8433931B2 (en) | 2009-05-13 | 2013-04-30 | Microsoft Corporation | Integrating energy budgets for power management |
US20120136484A1 (en) * | 2010-11-30 | 2012-05-31 | Inventec Corporation | Data center |
US20120209442A1 (en) * | 2011-02-11 | 2012-08-16 | General Electric Company | Methods and apparatuses for managing peak loads for a customer location |
US20140006815A1 (en) * | 2012-06-28 | 2014-01-02 | Enrique G. Castro-Leon | Power management control of remote servers |
US9454199B2 (en) * | 2012-06-28 | 2016-09-27 | Intel Corporation | Power management control of remote servers |
US10067547B2 (en) | 2012-06-28 | 2018-09-04 | Intel Corporation | Power management control of remote servers |
US20140189298A1 (en) * | 2012-12-27 | 2014-07-03 | Teresa Morrison | Configurable ring network |
US20220134250A1 (en) * | 2019-06-23 | 2022-05-05 | Andrew David Hospodor | Method and Apparatus for Sharing Co-Generated Energy When Processing Essential Elements from Plant Matter |
US11865473B2 (en) * | 2019-06-23 | 2024-01-09 | Andrew David Hospodor | Method and apparatus for sharing co-generated energy when processing essential elements from plant matter |
US11700082B1 (en) * | 2019-07-23 | 2023-07-11 | Cable Television Laboratories, Inc. | Systems and methods for proactive network maintenance |
Also Published As
Publication number | Publication date |
---|---|
EP2127212A1 (en) | 2009-12-02 |
CN101589574B (en) | 2012-11-28 |
US7793120B2 (en) | 2010-09-07 |
CN101589574A (en) | 2009-11-25 |
TW200839536A (en) | 2008-10-01 |
EP2127212A4 (en) | 2012-05-02 |
WO2008088951A1 (en) | 2008-07-24 |
JP2010517142A (en) | 2010-05-20 |
TWI360753B (en) | 2012-03-21 |
JP3180006U (en) | 2012-11-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7793120B2 (en) | Data structure for budgeting power for multiple devices | |
US20080178029A1 (en) | Using priorities to select power usage for multiple devices | |
US7793126B2 (en) | Using priorities and power usage to allocate power budget | |
US7272732B2 (en) | Controlling power consumption of at least one computer system | |
US7421623B2 (en) | Systems, methods, and media for controlling temperature in a computer system | |
CN100381978C (en) | System and method for power management of plural information handling systems | |
JP5496518B2 (en) | Centralized power management method, device-side agent, centralized power management controller, and centralized power management system | |
US9524012B2 (en) | Power system utilizing processor core performance state control | |
US20090055665A1 (en) | Power Control of Servers Using Advanced Configuration and Power Interface (ACPI) States | |
TWI411913B (en) | System and method for limiting processor performance | |
US8065537B2 (en) | Adjusting cap settings of electronic devices according to measured workloads | |
US10528119B2 (en) | Dynamic power routing to hardware accelerators | |
US8677160B2 (en) | Managing power consumption of a computer | |
US8103884B2 (en) | Managing power consumption of a computer | |
US10076067B2 (en) | System and method of controlling an air mover | |
US7636861B2 (en) | Bus technique for controlling power states of blades in a blade enclosure | |
JP2005115940A (en) | Rack equipment management information coordination system and method | |
US20220350383A1 (en) | Slot airflow based on a configuration of the chassis | |
TWI467377B (en) | Method of powering on server |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MCGRANE, SEAN NICHOLAS;PARCHEM, JOHN M.;BERARD, STEPHEN ROLAND;REEL/FRAME:018903/0535;SIGNING DATES FROM 20070110 TO 20070111 Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MCGRANE, SEAN NICHOLAS;PARCHEM, JOHN M.;BERARD, STEPHEN ROLAND;SIGNING DATES FROM 20070110 TO 20070111;REEL/FRAME:018903/0535 |
|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MCGRANE, SEAN NICHOLAS;PARCHEM, JOHN M.;BERARD, STEPHEN ROLAND;REEL/FRAME:020224/0376;SIGNING DATES FROM 20070110 TO 20070111 Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MCGRANE, SEAN NICHOLAS;PARCHEM, JOHN M.;BERARD, STEPHEN ROLAND;SIGNING DATES FROM 20070110 TO 20070111;REEL/FRAME:020224/0376 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034542/0001 Effective date: 20141014 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |