Embodiments of the disclosure relate generally to memory sub-systems, and more specifically, relate to memory sub-systems employing thermal islanding heat isolation.
A memory sub-system can include one or more memory devices that store data. The memory devices can be, for example, non-volatile memory devices and volatile memory devices. In general, a host system can utilize a memory sub-system to store data at the memory devices and to retrieve data from the memory devices.
The present disclosure will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the disclosure.
Aspects of the present disclosure are directed to a memory system employing thermal islanding isolation. In some embodiments, the memory system employing thermal islanding isolation may include a thermal islanding barrier (e.g., an air gap, thermal insulating material, or both) in a memory sub-system. A memory sub-system can be a storage system, storage device, a memory module, or a combination of such. An example of a memory sub-system is a storage system such as a solid-state drive (SSD). Examples of storage devices and memory modules are described below in conjunction with
A memory device can be a non-volatile memory device. One example of non-volatile memory devices is a negative-and (NAND) memory device (also known as flash technology). Other examples of non-volatile memory devices are described below in conjunction with
Each of the memory devices can include one or more arrays of memory cells. Depending on the cell type, a cell can store one or more bits of binary information, and has various logic states that correlate to the number of bits being stored. The logic states can be represented by binary values, such as “0” and “1”, or combinations of such values. There are various types of cells, such as single level cells (SLCs), multi-level cells (MLCs), triple level cells (TLCs), and quad-level cells (QLCs). For example, a SLC can store one bit of information and has two logic states, while a TLC can store multiple bits of information and has eight logic states.
Another example of a memory device can be a volatile memory device. A volatile memory device can include a memory array, which can be a dynamic random access memory (DRAM) array, SRAM array, STT RAM array, PCRAM array, TRAM array, and/or RRAM array, for instance. In general, a volatile memory device stores data while the memory device is powered but generally does not store data when the memory device is powered down or is powered off. A memory sub-system, such as a SSD, can include a combination of non-volatile memory devices and volatile memory devices.
During operation, components of a memory sub-system (e.g., a SSD) can experience fluctuations in thermal conditions, such as operating temperatures. For example, because electrical current is utilized to provide power to the components (e.g., memory devices, a power regulation area, controllers, etc.) of a memory sub-system, the memory sub-system and the components thereof can exhibit temperature fluctuations during operation. Such fluctuations can become more pronounced based on the type of workload the memory sub-system and components thereof are subjected to. For example, some types of workloads that can be characterized by high volumes of operations can give rise to greater temperature fluctuations in the memory sub-system and the components thereof than workloads that are characterized by low volumes of operations. Further, a memory sub-system can experience temperature fluctuations based on the environment in which the memory sub-system is deployed, an amount of time the memory sub-system is continually operating, and/or a form factor of the memory sub-system, which can dictate the placement and available footprint allowable for the components of the memory device to be deployed.
Although some amount of temperature fluctuation is tolerable within a memory sub-system, the memory sub-system can be adversely affected if such temperature fluctuations exceed certain thresholds. For example, if a memory sub-system is exposed to temperatures that are greater than a threshold safe operating temperature range, the memory sub-system can experience degraded performance and, in some instances, can fail.
Due to the technological evolution of memory sub-system technology, which is, at least in part driven by user (e.g., client, customer, etc.) expectations, there are constantly evolving issues regarding thermal control with respect to memory sub-systems, such as SSDs. For example, because storage media (e.g., memory device) trends are becoming more sensitive to thermal variations given increasing power level demands and/or the implementation of ever-faster storage protocols, thermal control in a memory sub-system continues to become increasingly important in order to mitigate degraded performance and/or failures that can occur when a memory sub-system is exposed to temperatures that approach or exceed a threshold safe operating temperature range. Further, form factors for memory sub-systems and the constituent components thereof are also trending towards a reduction in size due to, for example, the increasing prevalence of compact computing devices (e.g., smartphones, phablets, tablets, laptops, etc.) which can result in more heat being generated in a smaller space.
In conventional approaches, thermal control and/or thermal mitigation in memory sub-systems generally involves spreading components of a memory sub-system, such as a SSD, across a widest area possible to reduce the overall maximum temperature on any part of the memory sub-system. Such approaches can therefore rely on coupling the memory sub-system controller and/or application specific integrated circuits (ASICs) that perform controller functions for the memory sub-system together with the memory devices (e.g., storage media associated with the memory sub-system) and a power regulation area (e.g., power regulation circuitry to provide power to the components of the memory sub-system) on a printed circuit board (PCB). In general, a “power regulation area” refers to an area of a memory sub-system that includes circuitry or other components that are configured to provide and/or manage power (e.g., signals indicative of a voltage, a current, etc.) to operate other components of the memory sub-system. In these approaches, a heatsink, or other similar generally monolithic device(s) is provided to dissipate or otherwise spread heat across the components coupled to the PCB to mitigate adverse effects that can arise when the memory sub-system is exposed to temperatures that are greater than a threshold safe operating temperature range.
Although such approaches can allow for heat to be dissipated across the PCB thereby providing a cooling effect to some components of the memory sub-system, undesired effects may also occur. For example, by spreading the thermal load of the hottest components (e.g., power supplies, a power regulation areas, and/or controllers, among others) throughout the memory sub-system and therefore to components that are generally heat sensitive (e.g., memory devices), various issues can arise. For example, an increase in the temperature and/or thermal load experienced by the memory devices as a result of heat being transferred from the hottest components to the heat sensitive components can lead to the memory devices incurring increased error rates, reduced media life, and/or undesirable cross temperature behaviors.
These undesired effects can be further pronounced in some small form factor implementations (e.g., M.2 form factor architectures, U.2 form factor architectures, etc.) where thermal management is of utmost concern due to the constrained space available to house the components of a memory sub-system. In some approaches, thermal management can be provided through the use of multiple temperature sensors, component placement, and/or complicated firmware algorithms to maintain components of the memory sub-system within a particular thermal operating range. However, adding additional components such as multiple heat sensors and processing capability to perform the complicated firmware algorithms can further exacerbate issues associated with the limited available physical space in small form factor devices. Further, memory sub-system consumers are becoming more sophisticated in understanding that the temperature of the memory devices in a memory sub-system is generally the thermal priority and, because their data being accurately stored is of key concern, are more frequently requesting that memory sub-system operating temperature values are specified in terms of the memory device operating temperatures.
These and other trends and concerns have uncovered inadequacies in approaches that utilize conventional thermal management strategies such as the employment of a heat sink to maximize the spread of heat across the memory sub-system (e.g., across the PCB of the memory sub-system). For example, in contemporary memory sub-systems, the traditional strategy of maximizing the heat spread through the use of a heat sink can induce more complex endurance issues as the memory device(s), which generally account for only a small to moderate contribution to the heat generated by the memory sub-system, are less tolerant to the increased thermal load from other components of the memory device, such as the controller(s), power regulation area(s), power supplies, etc.
Aspects of the present disclosure address the above and other deficiencies by providing a special purpose heat sink (e.g., a thermal islanding heatsink that includes a monolithic heat sink and a thermal insulating barrier) that isolates heat transfer from the hot components (e.g., the controller(s), power regulation area(s), power supplies, etc.) to the memory devices with a thermally insulative material that is placed in between different “thermal zones” of the memory sub-system. Notably, the different “thermal zones” can include three or more different thermal zones such as a “warm zone”, a “cool zone”, and a “hot zone” in the same memory sub-system (e.g., on the same side of a PCB in the memory sub-system) may yield improved memory sub-system performance attributable at least to having different types of memory devices in different thermal zones, as detailed herein, in contrast to other approaches that do not employ thermal zones or employ only two different thermal zones.
Additionally, the special purpose heat sink(s) (e.g., the thermal islanding heatsink) described herein can allow for heat transfer between the hot components (e.g., controllers, power regulators, etc.), warm components (e.g., flash memory devices, etc.), and/or the cooler components (e.g., DRAM devices, etc.) to be reduced in comparison to the approaches described above, thereby improving error rates, increasing media life, increasing an amount of time between performance of thermal throttling operations, reducing a frequency of media scan operations, and/or mitigating undesirable cross temperature behaviors of the memory sub-system that can arise due to thermal behaviors of the memory sub-system. While the special purpose heat sink of the present disclosure, in connection with the component layouts described herein, are generally described with regard to providing thermal mitigation for components that are deployed along a top portion of the PCB, it is understood that such approaches may alternatively or in addition be deployed with components located on the bottom portion of the PCB of a memory sub-system, which is generally not possible using the monolithic heat sink paradigms of the approaches describe above.
A memory sub-system 110 can be a storage device, a memory module, or a hybrid of a storage device and memory module. Examples of a storage device include a solid-state drive (SSD), a flash drive, a universal serial bus (USB) flash drive, an embedded Multi-Media Controller (eMMC) drive, a Universal Flash Storage (UFS) drive, a secure digital (SD) card, and a hard disk drive (HDD). Examples of memory modules include a dual in-line memory module (DIMM), a small outline DIMM (SO-DIMM), and various types of non-volatile dual in-line memory modules (NVDIMMs).
The computing system 100 can be a computing device such as a desktop computer, laptop computer, server, network server, mobile device, a vehicle (e.g., airplane, drone, train, automobile, or other conveyance), Internet of Things (IoT) enabled device, embedded computer (e.g., one included in a vehicle, industrial equipment, or a networked commercial device), or such computing device that includes memory and a processing device.
The computing system 100 can include a host system 120 that is coupled to one or more memory sub-systems 110. In some embodiments, the host system 120 is coupled to different types of memory sub-system 110.
The host system 120 can include a processor chipset and a software stack executed by the processor chipset. The processor chipset can include one or more cores, one or more caches, a memory controller (e.g., an SSD controller), and a storage protocol controller (e.g., PCle controller, SATA controller). The host system 120 uses the memory sub-system 110, for example, to write data to the memory sub-system 110 and read data from the memory sub-system 110.
The host system 120 includes a processing device 121. The processing unit 121 can be a central processing unit (CPU) that is configured to execute an operating system. In some embodiments, the processing unit 121 comprises a complex instruction set computer architecture, such an x86 or other architecture suitable for use as a CPU for a host system 120.
The host system 120 can be coupled to the memory sub-system 110 via a physical host interface. Examples of a physical host interface include, but are not limited to, a serial advanced technology attachment (SATA) interface, a peripheral component interconnect express (PCIe) interface, universal serial bus (USB) interface, Fibre Channel, Serial Attached SCSI (SAS), Small Computer System Interface (SCSI), a double data rate (DDR) memory bus, a dual in-line memory module (DIMM) interface (e.g., DIMM socket interface that supports Double Data Rate (DDR)), Open NAND Flash Interface (ONFI), Double Data Rate (DDR), Low Power Double Data Rate (LPDDR), or any other interface. The physical host interface can be used to transmit data between the host system 120 and the memory sub-system 110. The host system 120 can further utilize an NVM Express (NVMe) interface to access components (e.g., memory devices 130) when the memory sub-system 110 is coupled with the host system 120 by the PCle interface. The physical host interface can provide an interface for passing control, address, data, and other signals between the memory sub-system 110 and the host system 120.
The memory devices 130, 140 can include any combination of the different types of non-volatile memory devices and/or volatile memory devices. The volatile memory devices (e.g., memory device 140) can be, but are not limited to, random access memory (RAM), such as dynamic random-access memory (DRAM) and synchronous dynamic random access memory (SDRAM).
Some examples of non-volatile memory devices (e.g., memory device 130) include negative-and (NAND) type flash memory and write-in-place memory, such as three-dimensional cross-point (“3D cross-point”) memory device, which is a cross-point array of non-volatile memory cells. A cross-point array of non-volatile memory can perform bit storage based on a change of bulk resistance, in conjunction with a stackable cross-gridded data access array. Additionally, in contrast to many flash-based memories, cross-point non-volatile memory can perform a write in-place operation, where a non-volatile memory cell can be programmed without the non-volatile memory cell being previously erased. NAND type flash memory includes, for example, two-dimensional NAND (2D NAND) and three-dimensional NAND (3D NAND).
Each of the memory devices 130, 140 can include one or more arrays of memory cells. One type of memory cell, for example, single level cells (SLC) can store one bit per cell. Other types of memory cells, such as multi-level cells (MLCs), triple level cells (TLCs), quad-level cells (QLCs), and penta-level cells (PLC) can store multiple bits per cell. In some embodiments, each of the memory devices 130 can include one or more arrays of memory cells such as SLCs, MLCs, TLCs, QLCs, or any combination of such. In some embodiments, a particular memory device can include an SLC portion, and an MLC portion, a TLC portion, a QLC portion, or a PLC portion of memory cells. The memory cells of the memory devices 130 can be grouped as pages that can refer to a logical unit of the memory device used to store data. With some types of memory (e.g., NAND), pages can be grouped to form blocks.
Although non-volatile memory components such as three-dimensional cross-point arrays of non-volatile memory cells and NAND type memory (e.g., 2D NAND, 3D NAND) are described, the memory device 130 can be based on any other type of non-volatile memory or storage device, such as such as, read-only memory (ROM), phase change memory (PCM), self-selecting memory, other chalcogenide based memories, ferroelectric transistor random-access memory (FeTRAM), ferroelectric random access memory (FeRAM), magneto random access memory (MRAM), Spin Transfer Torque (STT)-MRAM, conductive bridging RAM (CBRAM), resistive random access memory (RRAM), oxide based RRAM (OxRAM), negative-or (NOR) flash memory, and electrically erasable programmable read-only memory (EEPROM).
The memory sub-system controller 115 (or controller 115 for simplicity) can communicate with the memory devices 130 to perform operations such as reading data, writing data, or erasing data at the memory devices 130 and other such operations. The memory sub-system controller 115 can include hardware such as one or more integrated circuits and/or discrete components, a buffer memory, or a combination thereof. The hardware can include digital circuitry with dedicated (i.e., hard-coded) logic to perform the operations described herein. The memory sub-system controller 115 can be a microcontroller, special purpose logic circuitry (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), or other suitable processor.
The memory sub-system controller 115 can include a processor 117 (e.g., a processing device) configured to execute instructions stored in a local memory 119. In the illustrated example, the local memory 119 of the memory sub-system controller 115 includes an embedded memory configured to store instructions for performing various processes, operations, logic flows, and routines that control operation of the memory sub-system 110, including handling communications between the memory sub-system 110 and the host system 120.
In some embodiments, the local memory 119 can include memory registers storing memory pointers, fetched data, etc. The local memory 119 can also include read-only memory (ROM) for storing micro-code. While the example memory sub-system 110 in
In general, the memory sub-system controller 115 can receive commands or operations from the host system 120 and can convert the commands or operations into instructions or appropriate commands to achieve the desired access to the memory device 130 and/or the memory device 140. The memory sub-system controller 115 can be responsible for other operations such as wear leveling operations, garbage collection operations, error detection and error-correcting code (ECC) operations, encryption operations, caching operations, and address translations between a logical address (e.g., logical block address (LBA), namespace) and a physical address (e.g., physical block address, physical media locations, etc.) that are associated with the memory devices 130. The memory sub-system controller 115 can further include host interface circuitry to communicate with the host system 120 via the physical host interface. The host interface circuitry can convert the commands received from the host system into command instructions to access the memory device 130 and/or the memory device 140 as well as convert responses associated with the memory device 130 and/or the memory device 140 into information for the host system 120.
The memory sub-system 110 can also include additional circuitry or components that are not illustrated. In some embodiments, the memory sub-system 110 can include a cache or buffer (e.g., DRAM) and address circuitry (e.g., a row decoder and a column decoder) that can receive an address from the memory sub-system controller 115 and decode the address to access the memory device 130 and/or the memory device 140.
In some embodiments, the memory device 130 includes local media controllers 135 that operate in conjunction with memory sub-system controller 115 to execute operations on one or more memory cells of the memory devices 130. An external controller (e.g., memory sub-system controller 115) can externally manage the memory device 130 (e.g., perform media management operations on the memory device 130). In some embodiments, a memory device 130 is a managed memory device, which is a raw memory device combined with a local controller (e.g., local controller 135) for media management within the same memory device package. An example of a managed memory device is a managed NAND (MNAND) device.
In some embodiments, the memory sub-system 110 can be resident on a mobile computing device such as a smartphone, laptop, phablet, Internet-of-Things device, autonomous vehicle, or the like (e.g., the computing system 100 can be a mobile computing device). As used herein, the term “resident on” refers to something that is physically located on a particular component. For example, the memory sub-system 110 being “resident on” the mobile computing device refers to a condition in which the hardware that comprises the memory sub-system 110 is physically located on the mobile computing device. The term “resident on” may be used interchangeably with other terms such as “deployed on” or “located on,” herein. Further, as used herein, the term “mobile computing device” generally refers to a handheld computing device that has a slate or phablet form factor. In general, a slate form factor can include a display screen that is between approximately 3 inches and 5.2 inches (measured diagonally), while a phablet form factor can include a display screen that is between approximately 5.2 inches and 7 inches (measured diagonally). Examples of “mobile computing devices” are not so limited, however, and in some embodiments, a “mobile computing device” can refer to an IoT device, among other types of edge computing devices.
The example memory sub-system 210 and/or or the memory sub-system 211 can be referred to in the alternative as a “system” or an “apparatus,” herein. As used herein, an “apparatus” or “system” can refer to, but is not limited to, any of a variety of structures or combinations of structures, such as a circuit or circuitry, a die or dice, a module or modules, a device or devices, or a system or systems, for example. For example, the memory sub-system 210 and/or the memory sub-system 211 can include a one or more memory modules (e.g., single in-line memory modules, dual in-line memory modules, etc.). In a number of embodiments, the memory sub-system 210 and/or the memory sub-system 211 can include a multi-chip device. A multi-chip device can include a number of different memory types and/or memory modules (e.g., the memory device(s) 230 and/or the memory device(s) 240). Accordingly, the memory sub-system 210 and/or the memory sub-system 211 can include non-volatile or volatile memory on any type of a module. In addition, each of the components (e.g., the controller 215, the power regulation area “PWR. REG.” 214, the memory device(s) 230-1/230-2, and/or the memory device(s) 240-1) can be separately referred to herein as an “apparatus” or a “system” given the context of the disclosure.
As shown in
In some embodiments, the controller 215, the power regulation area 214, the memory devices 230-1 and 230-2 and the memory device 240-1, 240-2, 240-3, . . . 240-M may have access to (e.g., may be coupled to) a heat sink, such as the monolithic heat sink 318 illustrated in
As mentioned above, certain components of the memory sub-system 210 and the memory sub-system 211 (e.g., the controller 215 and the power regulation area 214) generally generate more heat during operation than the memory devices 230 and/or the memory devices 240. However, as described in more detail in connection with
The memory sub-system 211 illustrated in
As discussed above, the controller 215 and the power regulation area 214 as illustrated in
In contrast to
The memory sub-system 310 includes a controller 315, a power regulation area 314, a memory device 340-2, and a memory device 330-1. The controller 315, the power regulation area 314, the memory device 340-2, and the memory device 330-1 can be analogous to the controller 215, the power regulation area 214, the memory devices 240-2, and the memory device 230-1 illustrated in
Similar to the memory sub-system 310, the memory sub-system 311 includes a controller 315, a power regulation area 314, a memory device 340-1, and memory device 330-1, . . . 330-N. The controller 315, the power regulation area 314, the memory device 340-1, and the memory devices 330-1, . . . , 330-N can be analogous to the controller 215, the power regulation area 214, the memory device 240-1, and the memory devices 230-1, . . . 230-N illustrated in
As shown in
As described above in connection with conventional approaches, the heat sink 318 can be coupled to a top portion (e.g., to the top portion of the memory sub-system 210 illustrated in
The memory sub-system 416 illustrated in
In contrast to the memory sub-systems 210 illustrated in
In some embodiments, the first thermal barrier 422-1 and the second thermal barrier 422-2 (which may be referred to collectively as the thermal barrier 422) may be the same type of thermal barrier (e.g., may be formed of the same type of thermal insulating material). For instance, each of the first thermal barrier 422-1 and the second thermal barrier 422-2 may be formed of a thermally insulating material other than air. However, in some embodiments, the first thermal barrier 422-1 and the second thermal barrier 442-2 may be formed of different materials. In some embodiments, each the first thermal barrier 422-1 and the second thermal barrier 422-2 may have a complex shape, as described herein.
The thermal barriers 422-1, 422-2 shown in
The thermal barrier 422 can provide a physical barrier between the components that generate more heat during operation of the memory sub-system 416 (e.g., the controller 415 and the power regulation area 414) and the components that generate less heat during operation of the memory sub-system 416 (e.g., the memory devices 430, 440). In some embodiments, as described in connection with
The thermal barrier 422 can be formed from a thermally insulative material (e.g., materials having a relatively low thermal conductivity, such as an acrylic material). Embodiments are not so limited, however, and in some embodiments, the thermal barrier 422 can be an air gap (e.g., a region that contains air). As described herein, the thermal insulating barrier can include an air gap and/or a thermally insulting material, such as an acrylic material. In addition to, or in the alternative, the thermal insulating barrier can be provided as a complex shape as described in connection with
The size (e.g., the height, width, etc.) of the thermal barrier 422 can be configured for different applications and/or expected thermal behaviors of the memory sub-system 416, 423. For example, the size (e.g., one or more dimensions) of the thermal barrier 422 can be larger for a memory sub-system 416, 423 that experiences higher thermal characteristics than for a memory sub-system 416, 423 that experiences lower thermal characteristics. Stated differently, the thermal barrier 422 can be larger for memory sub-system architectures that generate a greater amount of heat and/or to offer more protection the memory devices 430 and/or the memory device 440 than for memory sub-system architectures that generate a lesser amount of heat and/or require less protection the memory devices 430 and/or the memory device 440.
In a non-limiting example, an apparatus (e.g., the memory sub-system 416) includes a memory device (e.g., at least one of the memory devices 430 and/or at least one of the memory devices 440), a controller 415, and a power regulation area 414. Accordingly, the thermal insulating barrier can be implemented to reduce heat transfer from a portion of the apparatus (e.g., a portion of the apparatus that includes the controller 415 and/or the power regulation area 414) to a portion of the apparatus that includes a non-volatile memory device and/or a volatile memory device. For example, the apparatus can include a second memory device and the memory device (e.g., a first memory device) can be a non-volatile memory device while the second memory device can be a volatile memory device. In such embodiments, the memory device and the second memory device are on a first side of the thermal insulating barrier and the power regulation area and/or the controller is/are on a second side of the thermal insulating barrier.
For example, as shown in
As shown in
As shown in
In the embodiments illustrated in
Continuing with this non-limiting example, the thermal insulating barrier is deployed between i) the controller 515 and the power regulation area 514 and ii) at least one of the non-volatile memory device and the volatile memory device. That is, the thermal insulating barrier is physically located between i) the controller 515 and the power regulation area 514 and ii) at least one of the non-volatile memory device and at least one of the volatile memory device. Such selective isolation of components can promote additional cooling to be directed to the cool zone and/or the warm zone which may include components (memory devices) with a higher temperature sensitivity than the components (e.g., the controller and/or the power regulation area) included in the hot zone.
As described above, the controller 515 and the power regulation area 514 are disposed on a top portion of the PCB 508 and similarly, the non-volatile memory device and the volatile memory device are disposed on a top portion of the PCB 508. In such embodiments, a “warm zone” of the heat sink (and/or the thermal insulating barrier) may be in physical contact with at least the one of the non-volatile memory device and a “cool zone” of the heatsink may be in physical contact with at least one of the volatile memory devices.
The thermal insulating barrier can be deployed between i) the controller 515 and the power regulation area 514 and ii) at least one non-volatile memory device and/or at least one volatile memory device, as described above. In some embodiments, although not explicitly shown in
In this non-limiting example, the thermal insulating barrier is formed entirely through the monolithic heat sink such that the thermal insulating barrier extends beyond an area defined by the monolithic heat sink. Stated alternatively, the thermal insulating barrier can be formed such that the thermal insulating barrier extends through the monolithic heat sink and the PCB 508 to provide thermal mitigation to components of the memory sub-system 516 that are disposed on a top portion of the PCB 508, as described above. Embodiments are not so limited, however, and the thermal insulating barrier can be formed such that the thermal insulating barrier extends above the monolithic heat sink (e.g., in a larger lateral dimension with respect to the z-axis shown in at least
In some embodiments, the heat pipe 662 may couple a first zone 681 (e.g., a hot zone) to a second zone 682 (e.g., a cool zone), where the heat pipe is configured to transport heat from the first zone 681 to the second zone 682. During operation of the apparatus, the first zone 681 is characterized by having a higher temperature than the second 682 zone and a third zone 683 (e.g., a warm zone), and the second zone 682 is characterized by having a lower temperature than the third zone 683. For instance, the heat pipe 662 may transfer heat from a hot zone including the controller 615 and the power regulation area 614 to a warm zone and/or a cool zone. For instance, the heat pipe may transfer heat from the hot zone including the controller 615 and the power regulation circuitry 613 to the cold zone including the memory device 630 (e.g., 630-1, 630-2, 630-3, . . . , 630-N), as illustrated in
As illustrated in
That is, in contrast to some previous approaches that may employ a single reservoir to cool all components (e.g., controller, power regulation circuitry and memory devices) in an apparatus, in the present disclosure each reservoir is associated with (cools) some but not all of the zones and components of the apparatus. Additionally, the thermal barrier 722 can be present to block the flow of heat between the different zones associated with the different liquid cooling reservoirs. As a result of the presence of the plurality of water cooling reservoirs and the thermal barrier 722, memory sub-system 770 performance can be improved in contrast to other approaches that do not employ a plurality of liquid cooling reservoirs and/or a thermal barrier therebetween. For instance, the memory sub-system 770 may realize less thermal throttling (e.g., longer period of operation in an absence of thermal throttling and/or improved performance (e.g., improved performance attributable to operation of temperature sensitive memory components at lower temperatures, etc.). The memory sub-system 770 may include a heatsink such as those described herein.
Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. The present disclosure can refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage systems.
The present disclosure also relates to an apparatus for performing the operations herein. This apparatus can be specially constructed for the intended purposes, or it can include a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMS, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, each coupled to a computer system bus.
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems can be used with programs in accordance with the teachings herein, or it can prove convenient to construct a more specialized apparatus to perform the method. The structure for a variety of these systems will appear as set forth in the description below. In addition, the present disclosure is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings of the disclosure as described herein.
In the foregoing specification, embodiments of the disclosure have been described with reference to specific example embodiments thereof. It will be evident that various modifications can be made thereto without departing from the broader spirit and scope of embodiments of the disclosure as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
This application claims the benefit of U.S. Provisional Application No. 63/513,258, filed on Jul. 12, 2023, the contents of which are incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
63513258 | Jul 2023 | US |