Conventional computer servers typically incorporate the compute resources, e.g., central processing unit (CPU) and memory, and input/output (I/O) adaptors within the same enclosure in a datacenter. The few systems that make use of disaggregated I/O typically contain some I/O functionality that still export specific I/O fabrics that are still locally tied to the server. As a result, these hardware types are physically close to each other, and must be powered and cooled in the datacenter assuming this close proximity.
Server enclosures containing CPUs & memory continue to demand air cooling because the enclosures incorporate specialized I/O devices and other components that cannot be cooled by alternate cooling methods other than air cooling, e.g., exclusive heat conduction to the rack.
Servers that do have disaggregated I/O typically remain located near I/O equipment because I/O link cabling between these resources tends to be local to the server and there is often no need to separate them further.
The detailed description will refer to the following drawings in which like numbers refer to like objects, and in which:
Traditional server computing systems incorporate input/output (I/O) resources, i.e., I/O hardware, along with the compute resources, i.e., compute hardware, typically because of the need to communicate between the compute and I/O resources at fast speeds. Examples of compute resources include central processing unit (CPU) and memory.
An embodiment of a system and method disaggregate I/O resources (i.e., hardware and devices) from a server's compute resources, such as CPU and memory, by moving the server's local I/O devices to a remote location apart from the server's compute resources. An embodiment uses optical technology to separate direct-attach I/O root ports from CPUs and memory in a server architecture and to accomplish the fast communication speeds needed between the compute resources and long distances associated with remotely located I/O resources. Specifically, an embodiment uses fiber-optic cables (i.e., optical cables) and electrical-to-optical conversion to facilitate communication between the compute resources and the I/O resources. The compute resources and the remotely located I/O resources can be designed differently to allow for liquid cooling exclusively for the compute resources and air cooling for the I/O resources.
Further, the datacenter may be segregated into equipment locales that differ in their cooling requirements. With the segregation of the compute and I/O resources, the floor-space rack density of the compute resources can be increased, thus increasing power and cooling efficiency, and providing a safe way to integrate liquid cooling at the rack-level. As a result, datacenter power and cooling can be performed more efficiently, thus saving cost at the datacenter level.
Further, the optical cables can connect many servers to many I/O devices and use fewer links than traditional I/O fabrics. The I/O devices may be housed in a separate I/O enclosure, which may use traditional air cooling in the datacenter. Without the overhead of having high-powered CPUs and memories present in the I/O enclosure, these I/O devices will consume less energy using the traditional air cooling infrastructure of the datacenter.
Referring to
Referring to
Referring to
Separating the compute resources from the I/O resources achieves cost savings associated with power and cooling of server equipment in the datacenter. The datacenter infrastructure can be optimized around the type of equipment being deployed in these different sections of the datacenter. For example, the CPU and memory may be placed in a datacenter room that requires little air movement since the liquid cooling plumbing to the room can remove all of the heat involved in these types of products. In an adjacent room, conventional heating, ventilation, and air conditioning device (HVAC) or CRAC air conditioning units may be utilized for the I/O hardware. The cost savings involved within the datacenter may be used to offset the extra cost involved in optically cabling between the compute and I/O resources.
The advantages of the system for separating compute and I/O resources in the datacenter to enable space and power savings are as follows. The I/O hardware are separated from the server's compute hardware, such as CPU and memory, opening the opportunity to design products separately from each other. If products can be designed separately from each other, different means of cooling can be used for each product. Liquid cooling can be used for the compute hardware, while air cooling can be used for the I/O hardware, without the need to co-join cooling methods into a single product. The system further facilitates more efficient setup of datacenter infrastructure in order to save cost of power and cooling to servers. Without the I/O hardware, the server uses less floor space in the datacenter, thus saving electricity, equipment, and facilities cost to datacenter operators.
When the system is conductively cooled using a central heat exchanger 140, the system provides liquid cooling at the rack-level without bringing liquid into the same enclosure as the compute hardware itself. Quick disconnects are not needed since all liquid cooling interfaces are conduction plates, i.e., cold plates 102. Adoption of liquid cooling into the compute rack 110 may be more favorable and may lead to quicker deployment and faster savings for datacenter customers.
Further, the remote I/O devices are connected to the server using a switched communications fabric, which is more generic by connecting many servers to many I/O devices. As a result, the datacenter operator has more freedom to separate the server from the I/O devices at longer distances, and to separate different equipment into different locales of the datacenter.
The memory 402 may include random access memory (RAM) or similar types of memory. The secondary storage device 412 may include a hard disk drive, floppy disk drive, CD-ROM drive, flash memory, or other types of non-volatile data storage, and may correspond with various databases or other resources. The processor 414 may execute instructions to perform the method steps described herein. These instructions may be stored in the memory 402, the secondary storage 412, or received from the Internet or other network. The input & display devices 416 may include, respectively, any device for entering data into the computer 400, such as a keyboard, keypad, cursor-control device, touch-screen (possibly with a stylus), or microphone, and any type of device for presenting a visual image, such as, for example, a computer monitor, flat-screen display, or display panel. An output device connected to the input/output cards 408 may include any type of device for presenting data in hard copy format, such as a printer, and other types of output devices including speakers or any device for providing data in audio form. The computer can possibly include multiple input devices, output devices, and display devices.
Although the computer is depicted with various components, one skilled in the art will appreciate that the computer can contain additional or different components. In addition, although aspects of an implementation consistent with the method for providing physically separated compute and I/O resources in the datacenter to enable space and power savings are described as being stored in memory, one skilled in the art will appreciate that these aspects can also be stored on or read from other types of computer program products or computer-readable media, such as secondary storage devices, including hard, disks, floppy disks, or CD-ROM; or other forms of RAM or ROM. The computer-readable media may include instructions for controlling the computer to perform a particular method.
The terms and descriptions used herein are set forth by way of illustration only and are not meant as limitations. Those skilled in the art will recognize that many variations are possible within the spirit and scope of the invention as defined in the following claims, and their equivalents, in which all terms are to be understood in their broadest possible sense unless otherwise indicated.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2009/069604 | 12/28/2009 | WO | 00 | 1/25/2012 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2011/081620 | 7/7/2011 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6619697 | Griffioen et al. | Sep 2003 | B2 |
7020359 | Mayer | Mar 2006 | B2 |
7139452 | Mayer et al. | Nov 2006 | B2 |
7373268 | Viredaz et al. | May 2008 | B1 |
7477514 | Campbell et al. | Jan 2009 | B2 |
7564685 | Clidaras et al. | Jul 2009 | B2 |
7596476 | Rasmussen et al. | Sep 2009 | B2 |
7660121 | Campbell et al. | Feb 2010 | B2 |
7903925 | Cooke et al. | Mar 2011 | B2 |
8064200 | West et al. | Nov 2011 | B1 |
8416834 | DeCusatis et al. | Apr 2013 | B2 |
20030200330 | Oelke et al. | Oct 2003 | A1 |
20050235671 | Belady et al. | Oct 2005 | A1 |
20060187639 | Carswell | Aug 2006 | A1 |
20070297136 | Konshak | Dec 2007 | A1 |
20080158818 | Clidaras et al. | Jul 2008 | A1 |
20090086432 | Campbell et al. | Apr 2009 | A1 |
20120215902 | DeCusatis et al. | Aug 2012 | A1 |
Number | Date | Country | |
---|---|---|---|
20120134678 A1 | May 2012 | US |