The present disclosure relates generally to semiconductor memory and methods, and more particularly, to apparatuses and methods for in-memory data switching networks.
Memory devices are typically provided as internal, semiconductor, integrated circuits in computers or other electronic systems. There are many different types of memory including volatile and non-volatile memory. Volatile memory can require power to maintain its data (e.g., host data, error data, etc.) and includes random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), synchronous dynamic random access memory (SDRAM), and thyristor random access memory (TRAM), among others. Non-volatile memory can provide persistent data by retaining stored data when not powered and can include NAND flash memory, NOR flash memory, and resistance variable memory such as phase change random access memory (PCRAM), resistive random access memory (RRAM), and magnetoresistive random access memory (MRAM), such as spin torque transfer random access memory (STT RAM), among others.
Electronic systems often include a number of processing resources (e.g., one or more processors), which may retrieve and execute instructions and store the results of the executed instructions to a suitable location. A processor can comprise a number of functional units such as arithmetic logic unit (ALU) circuitry, floating point unit (FPU) circuitry, and a combinatorial logic block, for example, which can be used to execute instructions by performing an operation on data (e.g., one or more operands). As used herein, an operation can be, for example, a Boolean operation, such as AND, OR, NOT, NOT, NAND, NOR, and XOR, and/or other operations (e.g., invert, shift, arithmetic, statistics, among many other possible operations). For example, functional unit circuitry may be used to perform the arithmetic operations, such as addition, subtraction, multiplication, and division on operands, via a number of operations.
A number of components in an electronic system may be involved in providing instructions to the functional unit circuitry for execution. The instructions may be executed, for instance, by a processing resource such as a controller and/or host processor. Data (e.g., the operands on which the instructions will be executed) may be stored in a memory array that is accessible by the functional unit circuitry. The instructions and/or data may be retrieved from the memory array and sequenced and/or buffered before the functional unit circuitry begins to execute instructions on the data. Furthermore, as different types of operations may be performed in one or multiple clock cycles through the functional unit circuitry, intermediate results of the instructions and/or data may also be sequenced and/or buffered. A sequence to complete an operation in one or more clock cycles may be referred to as an operation cycle. Time consumed to complete an operation cycle costs in terms of processing and computing performance and power consumption, of a computing apparatus and/or system.
In many instances, the processing resources (e.g., processor and associated functional unit circuitry) may be external to the memory array, and data is accessed via a bus between the processing resources and the memory array to execute a set of instructions. Processing performance may be improved in a processing-in-memory (PIM) device, in which a processing and/or logic resource may be implemented internally and/or near to a memory (e.g., directly on a same chip as the memory array). A processing-in-memory (PIM) device may save time by reducing and eliminating external communications and may also conserve power.
The present disclosure includes apparatuses and methods for in-memory data switching networks. In at least one embodiment, an apparatus includes an array of memory cells and sensing circuitry selectably coupled to the array of memory cells. An input/output (I/O) line is shared as a data path for in-memory data switching associated with the array. An in-memory data switching network is selectably coupled to the respective shared I/O line. For example, the sensing circuitry may be selectably coupled to columns of memory cells and the shared I/O lines and the memory data switching network may also be selectably coupled to the shared I/O lines. A controller is configured to couple to the in-memory data switching network and direct enablement of a switch protocol.
An in-memory data switching network, as described herein, is intended to mean circuitry (e.g., in a fixed configuration and/or as selected from a plurality of alternative programmable configurations) used to restructure and/or reorganize (e.g., to swizzle) data values in order to switch a position of at least one data value (e.g., all data values) in a sequence (e.g., plurality) of data values. To swizzle data values from their previous positions in the sequence as described herein may provide a number of advantages. Performance of various operations may rely on and/or may be improved by swizzing the data values relative to their original sequence. Such operations may, for example, include fast Fourier transforms, scatter gather functions, sorting functions, switching endianness (e.g., most significant bit to least significant bit) of data in the sequence, to pack bytes into vectors (e.g., packing vectors for imaging), to shift and/or to move bytes and/or bits in the sequence from one position to another position, among other possible operations in which data switching may be useful.
Ordinal numbers such as first and second are used herein to assist in correlating and/or distinguishing between similar and/or selectably coupled components (e.g., subarrays of memory cells and associated sensing circuitry, data values and associated compute components, subrows of memory cells and associated compute components, logic stripes and associated compute components, connection circuitry and associated compute components and/or logic stripes, etc.). The ordinal numbers are not used to indicate a particular ordering and/or relationship between the components, unless the context clearly dictates otherwise (e.g., by using terms such as adjacent, etc.).
A shared I/O line (e.g., as shown at 155 and described in connection with
As used herein, a “shared I/O line” is intended to a mean an I/O line that is local to the array in a data path that has a pitch which is a function of a pitch of the array of memory cells. The shared I/O may be located on a bank (e.g., as shown at 121 and described in connection with
As used herein, data movement is an inclusive term that includes, for instance, copying, transferring, and/or transporting data values from a source location to a destination location. Data may, for example, be moved from a sense amplifier of sensing circuitry of a subarray to a compute component in a logic stripe in a data path of a shared I/O line local to the array. Copying the data values may indicate that the data values stored (cached) in the sense amplifiers are copied and moved to a compute component in a logic stripe in the data path of the shared I/O line local to the array and that the original data values stored in the subrow of the row may remain unchanged. Transferring the data values may indicate that the data values stored (cached) in the sense amplifiers are copied and moved to a compute component in a logic stripe in the data path of the shared I/O line local to the array and that at least one of the original data values stored in the subrow of the row may be changed (e.g., by being erased and/or by a subsequent write operation, as described herein). Transporting the data values may be used to indicate the process by which the copied and/or transferred data values are moved (e.g., by the data values being placed on the shared I/O line from the source location and transported to the destination location).
As described in more detail below, the embodiments may allow a host system to allocate a number of locations (e.g., arrays, subarrays and/or portions of subarrays, such as row and subrows thereof) in one or more DRAM banks to hold (e.g., store) and/or process data. A host system and a controller may perform the address resolution on an entire block of program instructions (e.g., PIM command instructions) and data and direct (e.g., control) allocation, storage, and/or movement (e.g., flow) of data and commands into allocated locations (e.g., subarrays and portions of subarrays) within a destination (e.g., target) bank. Writing and/or reading data and/or executing commands in the DRAM array (e.g., movement of data values for performing operations by a logic stripe, as described herein) may utilize a normal DRAM read/write path to the DRAM device. As the reader will appreciate, while a DRAM-style memory array for a PIM device is discussed with regard to examples of in data path compute operations presented herein, embodiments are not limited to a PIM DRAM implementation.
The memory devices described herein may use a number of controllers for a bank of subarrays, controllers for individual subarrays, and/or controllers for latch components (e.g., each controller being a sequencer, a state machine, a microcontroller, a sub-processor, ALU circuitry, or some other type of controller) to execute a set of instructions to perform an operation on data (e.g., one or more operands). As used herein, an operation may be, for example, a Boolean logical operation, such as AND, OR, NOT, NOT, NAND, NOR, and XOR, and/or other operations (e.g., invert, shift, arithmetic, statistics, among many other possible operations). For example, functional unit circuitry may be used to perform the arithmetic operations, such as addition, subtraction, multiplication, and division on operands, via a number of logical operations.
In the following detailed description of the present disclosure, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration how one or more embodiments of the disclosure may be practiced. These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice the embodiments of this disclosure, and it is to be understood that other embodiments may be utilized and that process, electrical, and structural changes may be made without departing from the scope of the present disclosure.
As used herein, designators such as “X”, “Y”, “Z”, “N”, “M”, etc., particularly with respect to reference numerals in the drawings, indicate that a number of the particular feature so designated may be included. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting. As used herein, the singular forms “a”, “an”, and “the” can include both singular and plural referents, unless the context clearly dictates otherwise. In addition, “a number of”, “at least one”, and “one or more” (e.g., a number of memory arrays) can refer to one or more memory arrays, whereas a “plurality of” is intended to refer to more than one of such things. Furthermore, the words “can” and “may” are used throughout this application in a permissive sense (i.e., having the potential to and/or being able to in at least some embodiments described herein), not in a mandatory sense (i.e., must). The term “include,” and derivations thereof, means “including, but not limited to”. The terms “couple”, “coupled”, and “coupling” mean to be directly or indirectly connected physically or for access to and movement (transmission) of commands and/or data, as appropriate to the context. The terms “data” and “data values” are used interchangeably herein and can have the same meaning, as appropriate to the context.
The figures herein follow a numbering convention in which the first digit or digits correspond to the figure number and the remaining digits identify an element or component in the figure. Similar elements or components between different figures may be identified by the use of similar digits. For example, 108 may reference element “08” in
As used herein, in some embodiments, additional “latches” may be intended to mean additional functionalities (e.g., amplifiers, memory cells, select logic) that sense, couple, store, and/or move (e.g., read, store, cache) data values of memory cells in an array and that are distinct from latches (e.g., as shown at 706 and described in connection with
System 100 in
For clarity, the system 100 has been simplified to focus on features with particular relevance to the present disclosure. The memory array 130 may be a DRAM array, SRAM array, STT RAM array, PCRAM array, TRAM array, RRAM array, NAND flash array, and/or NOR flash array, among other types of arrays. The array 130 may include memory cells arranged in rows coupled by access lines (which may be referred to herein as word lines or select lines) and columns coupled by sense lines (which may be referred to herein as data lines or digit lines). Although a single array 130 is shown in
The memory device 120 may include address circuitry 142 to latch address signals provided over a data bus 156 (e.g., an I/O bus connected to the host 110) by I/O circuitry 144 (e.g., provided to external ALU circuitry and/or to DRAM DQs via local I/O lines and global I/O lines). As used herein, DRAM DQs may enable input of data to and/or output of data from a bank (e.g., from and/or to the controller 140 and/or host 110) via a bus (e.g., data bus 156). During a write operation, a voltage (high=1, low=0) may be applied to a DQ (e.g., a pin). This voltage may be translated into an appropriate signal and stored by a selected memory cell. During a read operation, a data value read from a selected memory cell may appear at the DQ once access is complete and the output is enabled (e.g., by the output enable signal being low). At other times, DQs may be in a high impedance state, such that the DQs do not source or sink current and do not present a signal to the system. This also may reduce DQ contention when two or more devices (e.g., banks) share a combined data bus, as described herein. Such DQs are separate and distinct from the plurality of shared I/O lines 155 (in
Status and exception information may be provided from the controller 140 of the memory device 120 to a channel controller 143, for example, through an out-of-band (OOB) bus 157 (e.g., high-speed interface (HSI)), which in turn may be provided from the channel controller 143 to the host 110. The channel controller 143 may include a logic component to allocate a plurality of locations (e.g., controllers for subarrays) in the arrays of each respective bank to store bank commands, application instructions (e.g., for sequences of operations), and arguments (PIM commands) for various banks associated with operations for each of a plurality of memory devices 120. The channel controller 143 may dispatch commands (e.g., PIM commands) to the plurality of memory devices 120 to store those program instructions within a given bank 121 (e.g., banks 121 and 121-1 of
Address signals are received through address circuitry 142 and decoded by a row decoder 146 and a column decoder 152 to access the memory array 130. Data may be sensed (read) from memory array 130 by sensing voltage and/or current changes on sense lines (digit lines) using a number of sense amplifiers, as described herein, of the sensing circuitry 150. A sense amplifier may read and latch a page (e.g., a row) of data from the memory array 130. Additional compute circuitry, as described herein, may be coupled to the sensing circuitry 150 and may be used in combination with the sense amplifiers to sense, store (e.g., cache and/or buffer), perform compute functions (e.g., operations), and/or move data. The I/O circuitry 144 may be used for bi-directional data communication with host 110 over the data bus 156 (e.g., a 64 bit wide data bus). The write circuitry 148 may be used to write data to the memory array 130.
Controller 140 (e.g., bank control logic, sequencer and timing circuitry shown in
Examples of the sensing circuitry 150 are described further below (e.g., in
In some embodiments, the sensing circuitry 150 may be used to perform operations using data stored by memory array 130 as inputs and participate in movement of the data for copy, transfer, transport, writing, logic, and/or storage operations to a different location in the memory array 130 and/or in logic stripes 109 without transferring the data via a sense line address access (e.g., without firing a column decode signal). As such, in some embodiments, various compute functions may be performed using, and within, sensing circuitry 150 rather than (or in association with) being performed by processing resources external to the sensing circuitry 150 (e.g., by a processor associated with host 110 and/or other processing circuitry, such as ALU circuitry, located on device 120, such as on controller 140 or elsewhere). However, in addition, embodiments described herein may perform in data path compute functions and/or operations on data values moved to a plurality of compute components 431-1, . . . , 431-Z and/or logic stripes 109-0, . . . , 109-N−1 in a compute unit from the rows of the array. As an example, according to some embodiments, compute operations may be controlled in the compute unit at speeds of 2 ns without having to move the data values back into the rows, as compared to an example time required to fire the rows in the array of 60 ns.
In various previous approaches, data associated with an operand, for instance, would be read from memory via sensing circuitry and provided to external ALU circuitry via I/O lines (e.g., via local I/O lines and/or global I/O lines). The external ALU circuitry could include a number of registers and would perform compute functions using the operands, and the result would be transferred back to the array via the I/O circuitry 144.
In contrast, embodiments herein perform compute functions on data values, moved to a plurality of compute components 431-1, . . . , 431-Z and/or logic stripes 109-0, . . . , 109-N−1 via a plurality of shared I/O lines 155 from the rows and/or subrows of the array, in a compute unit in a data path local to the array. Additionally, sensing circuitry 150 may be configured to perform operations on data stored by memory array 130 and store the result back to the memory array 130 without enabling an I/O line (e.g., a local I/O line) coupled to the sensing circuitry 150. However, once loaded, compute operations may be controlled in the compute unit much faster (e.g., at speeds of 2 ns) without having to move the data values back into the rows and/or subrows, as compared to an example time required to fire the rows in the array (e.g., 60 ns). The sensing circuitry 150 may be formed on pitch with the memory cells of the array. The plurality of compute components 431-1, . . . , 431-Z and/or logic stripes 109-0, . . . , 109-N−1, associated with the data path of the plurality of shared I/O lines 155, may have a pitch equal to that of the data path and that is a function of a pitch of digit lines to the array of memory cells
For example, the sensing circuitry 150 described herein may be formed on a same pitch as a pair of complementary sense lines (e.g., digit lines). As an example, a pair of complementary memory cells may have a cell size with a 6F2 pitch (e.g., 3F×2F), where F is a feature size. If the pitch of a pair of complementary sense lines for the complementary memory cells is 3F, then the sensing circuitry being on pitch indicates the sensing circuitry (e.g., a sense amplifier and/or a corresponding compute component per respective pair of complementary sense lines) is formed to fit within the 3F pitch of the complementary sense lines. Likewise, the compute components 431-1, . . . , 431-Z of the logic stripes 109-0, . . . , 109-N−1, associated with the data path of the plurality of shared I/O lines 155, have a pitch that is a function of the 3F pitch of the complementary sense lines. For example, the compute components 431-1, . . . , 431-Z of logic stripes 109-0, . . . , 109-N−1 may have a pitch that is an integer multiple of the 3F pitch of digit lines to the array of memory cells, which also may correspond to a pitch of the plurality of shared I/O lines 155.
By contrast, the circuitry of the processing resource(s) (e.g., a compute engine, such as an ALU) of various prior systems may not conform to pitch rules associated with a memory array. For example, the memory cells of a memory array may have a 4F2 or 6F2 cell size. As such, the devices (e.g., logic gates) associated with ALU circuitry of previous systems may not be capable of being formed on pitch with the memory cells (e.g., on a same pitch as the sense lines), which may affect chip size and/or memory density, for example. In the context of some computing systems and subsystems (e.g., a central processing unit (CPU)), data may be processed in a location that is not on pitch and/or on chip with memory (e.g., memory cells in the array), as described herein. For example, the data may be processed by a processing resource associated with a host, for instance, rather than on pitch with the memory.
As such, in a number of embodiments, circuitry external to array 130 and sensing circuitry 150 is not needed to perform compute functions as the sensing circuitry 150 may perform the appropriate operations to perform such compute functions or may perform such operations in a data path of a plurality of shared I/O lines local to the array without the use of an external processing resource. Therefore, the sensing circuitry 150 and/or the plurality of compute components 431-1, . . . , 431-Z and/or logic stripes 109-0, . . . , 109-N−1 in a compute unit in a data path of the plurality of shared I/O lines 155 may be used to complement or to replace, at least to some extent, such an external processing resource (or at least the bandwidth consumption of such an external processing resource). In some embodiments, the sensing circuitry 150 and/or the plurality of compute components 431-1, . . . , 431-Z and/or logic stripes 109-0, . . . , 109-N−1 in a compute unit in a data path of the plurality of shared I/O lines 155 may be used to perform operations (e.g., to execute instructions) in addition to operations performed by an external processing resource (e.g., host 110). For instance, host 110 and/or sensing circuitry 150 may be limited to performing only certain operations and/or a certain number of operations.
Operations described herein may include operations associated with a PIM capable device. PIM capable device operations may use bit vector based operations. As used herein, the term “bit vector” is intended to mean a number of bits on a bit vector memory device (e.g., a PIM device) stored physically contiguously or non-contiguously in a row of an array of memory cells. Thus, as used herein a “bit vector operation” is intended to mean an operation that is performed on a bit vector that is a contiguous or non-contiguous portion of virtual address space (e.g., used by a PIM device). For example, a row of virtual address space in the PIM device may have a bit length of 16K bits (e.g., corresponding to 16K complementary pairs of memory cells in a DRAM configuration). Sensing circuitry 150, as described herein, for such a 16K bit row may include a corresponding 16K sense amplifiers 206 and/or processing elements (e.g., compute components 231) formed on pitch with the sense lines selectably coupled to corresponding memory cells in the 16 bit row. A compute component in the sensing circuitry and/or logic stripe of the PIM device may operate as a one bit processing element (PE) on a single bit of the bit vector of the row or subrow of memory cells sensed by the sensing circuitry 150 (e.g., sensed by and/or stored by a sense amplifier, as described herein). Similarly, the plurality of compute components 431-1, . . . , 431-Z of logic stripes 109-0, . . . , 109-N−1 in a compute unit in a data path of the plurality of shared I/O lines 155 may each operate as a one bit PE on a single bit of the bit vector of the row and/or subrow of memory cells sensed in an array.
Enabling an I/O line may include enabling (e.g., turning on, activating) a transistor having a gate coupled to a decode signal (e.g., a column decode signal) and a source/drain coupled to the I/O line. However, embodiments are not limited to not enabling an I/O line. For instance, in a number of embodiments, the sensing circuitry (e.g., 150) may be used to perform operations without enabling column decode lines of the array.
However, the plurality of shared I/O lines 155 may be enabled in order to load data values to the plurality of compute components 431-1, . . . , 431-Z and/or logic stripes 109-0, . . . , 109-N−1 in a compute unit in a data path of the plurality of shared I/O lines 155 where compute operations may be controlled much faster. For example, in the plurality of compute components 431-1, . . . , 431-Z and/or logic stripes 109-0, . . . , 109-N−1 in the compute unit, the compute operation may be performed at speeds of 2 ns. This enhancement of speed may be attributed to not having to move the data values back into the rows and/or subrows with the associated time used in firing the rows in the array (e.g., 60 ns).
Alternatively or in addition, the plurality of shared I/O lines 155 may be enabled in order to load data values to an in-memory data switching network 172. Various embodiments of the data switching network are described herein. In some embodiments, the data switching network (e.g., as shown at 372 and described in association with
Each column 122 is configured to be coupled to sensing circuitry 150, as described in connection with
Each of the of the subarrays 125-0, 125-1, . . . , 125-N−1 may include a plurality of rows 119 shown vertically as Y (e.g., each subarray may include 512 rows in an example DRAM bank). In some embodiments, the number of rows in one or more of the subarrays (e.g., all of the subarrays) may be substantially equal (e.g., all having 128, 256, 512 rows, among other possibilities). For example, each subarray of the plurality of subarrays may include a number of memory cells in a column that is substantially equal to a number of memory cells in a column of an adjacent subarray (e.g., all having 128, 256, 512 memory cells, among other possibilities) and/or a sense line of each subarray may have a length that is substantially equal to a length of a sense line of the column of the adjacent subarray (e.g., all subarrays in the array). Embodiments are not limited to the example horizontal and vertical orientation of columns and rows described herein or the example numbers thereof.
As shown in
The short and long digit line subarrays are respectively separated by amplification regions configured to be coupled to a data path (e.g., the shared I/O line described herein). As such, the short digit line subarrays 125-0 and 125-1 and the long digit line subarrays 126-0, . . . , 126-N−1 may each have amplification regions 124-0, 124-1, . . . , 124-N−1 that correspond to sensing component stripe 0, sensing component stripe 1, . . . , and sensing component stripe N−1, respectively.
Each column 122 may be configured to be coupled to sensing circuitry 150, as described in connection with
In some embodiments, a compute component may be coupled to each sense amplifier within the sensing circuitry 150 in each respective sensing component stripe coupled to a short digit line subarray (e.g., in sensing component stripes 124-0 and 124-1 coupled respectively to the short digit line subarrays 125-0 and 125-1). However, embodiments are not so limited. For example, in some embodiments, there may not be a 1:1 correlation between the number of sense amplifiers and compute components (e.g., there may be more than one sense amplifier per compute component or more than one compute component per sense amplifier, which may vary between subarrays, partitions, banks, etc).
Each of the of the short digit line subarrays 125-0 and 125-1 may include a plurality of rows 119 shown vertically as Y (e.g., each subarray may include 512 rows in an example DRAM bank). Each of the of the long digit line subarrays 126-0, . . . , 126-N−1 may include a plurality of rows 118 shown vertically as Z (e.g., each subarray may include 1024 rows in an example DRAM bank). As such, in various embodiments, the number of rows in one or more of the subarrays (e.g., all of the subarrays) may vary from the number of rows in other subarrays. For example, a number of memory cells in a column of a subarray of the first subset (e.g., a short digit line subarray) may, in some embodiments, be at most half of a number of memory cells in a column of a subarray of the second subset (e.g., a long digit line subarray) and/or a digit line (sense line) of a subarray of the first subset may have a length that is at most half of a length of a digit line of the subarray of the second subset. Embodiments are not limited to the example horizontal and vertical orientation of columns and rows described herein or the example numbers thereof.
Implementations of PIM DRAM architecture may perform processing at the sense amplifier and compute component level (e.g., in a sensing component stripe). Implementations of PIM DRAM architecture may allow a finite number of memory cells to be connected to each sense amplifier (e.g., around 1K or 1024memory cells). A sensing component stripe may include from around 8K to around 16K sense amplifiers. For example, a sensing component stripe for a long digit line subarray may include 16K sense amplifiers and may be configured to couple to an array of 1K rows and around 16K columns with a memory cell at each intersection of the rows and columns so as to yield 1K (1024) memory cells per column. By comparison, a sensing component stripe for a short digit line subarray may include 16K sense amplifiers and compute components and may be configured to couple to an array of, for example, at most half of the 1K rows of the long digit line subarray so as to yield 512 memory cells per column. In some embodiments, the number of sense amplifiers and/or compute components in respective sensing component stripes (e.g., corresponding to a number of memory cells in a row) may vary between at least some of the short digit line subarrays in comparison to the long digit line subarrays.
The numbers of rows, columns, and memory cells per column and/or the ratio of the numbers of memory cells between columns in the long and short digit line subarrays just presented are provided by way of example and not by way of limitation. For example, the long digit line subarrays may have columns that each have a respective 1024 memory cells and the short digit line subarrays may have columns that each have either a respective 512, 256, or 128 memory cells, among other possible numbers that are less than 512. The long digit line subarrays may, in various embodiments, have less than or more than 1024 memory cells per column, with the number of memory cells per column in the short digit line subarrays configured as just described. Alternatively or in addition, cache subarrays may be formed with a digit line length less than, equal to, or greater than the digit line length of the long digit line subarrays (storage subarrays) such that the cache subarrays are not the short digit line subarrays just described. For example, the configuration of the digit lines and/or the memory cells of the cache subarrays may provide faster computation than the configuration of the storage subarrays (e.g., 2T2C instead of 1T1C, SRAM instead of DRAM, etc).
Accordingly, the number of rows of memory cells in a cache subarray and/or the corresponding number of memory cells per digit line may be less than, equal to, or greater than the number of rows of memory cells in a storage subarray and/or the corresponding number of memory cells per digit line of the storage subarrays. In some embodiments, a number of memory cells in a row of a long digit line subarray may differ from a number of memory cells in a row of a short digit line subarray. For example, a memory cell of a short digit line subarray configured as 2T2C may be approximately twice as wide as a memory cell of a long digit line subarray configured as 1T1C because the 2T2C memory cell has two transistors and two capacitors whereas the 1T1C memory cell has one transistor and one capacitor. In order to integrate widths of these two configurations of subarrays on a chip and/or bank architecture, the number of memory cells in the rows may be adjusted (e.g., such that a short digit line subarray may, for example, have around half as many memory cells as in a row of a long digit line subarray). A controller may have or be directed by instructions to accommodate movement of data values between these two configurations of subarrays.
In some embodiments, long digit line subarray 126-N−1 may be subarray 32 in 128 subarrays and may be a last subarray in a first direction in a first partition of four partitions of subarrays, as described herein. Isolation stripes (not shown) may include a number of isolation transistors configured to selectably (e.g., as directed by controller 140) connect and disconnect portions of a selected shared I/O line. Selectably enabling (e.g., activating and inactivating) the isolation transistors connects and disconnects movement between partitions via the shared I/O line of data values to and from the sense amplifiers and/or compute components (e.g., in sensing component stripes, as described herein).
As such, the plurality of subarrays 125-0 and 125-1 and 126-0, . . . , 126-N−1, the plurality of sensing component stripes 124-0, 124-1, . . . , 124-N−1, and the isolation stripe may be considered as a single partition 128. In some embodiments, however, depending upon the direction of the data movement, a single isolation stripe may be shared by two adjacent partitions.
As shown in
As shown in
As described herein, an I/O line 155 may be selectably shared by a plurality of partitions, subarrays, rows, particular columns of memory cells, and/or an in-memory data switching network via the sensing component stripe coupled to each of the subarrays. For example, the sense amplifier and/or compute component of each of a selectable subset of a number of columns (e.g., eight column subsets of a total number of columns) may be selectably coupled to each of the plurality of shared I/O lines for data values stored (cached) in the sensing component stripe to be moved (e.g., transferred, transported, and/or fed) to each of the plurality of shared I/O lines.
As shown schematically in
The shared I/O lines 155 may be utilized to increase a speed, rate, and efficiency of data movement in a PIM array (e.g., between subarrays and/or the in-memory data switching network). In at least one embodiment, using the shared I/O lines 155 provides an improved data path by providing at least a thousand bit width. In one embodiment, 2048 shared I/O lines are coupled to 16,384 columns to provide a 2048 bit width. The illustrated shared I/O lines 155 may be formed on pitch with the memory cells of the array.
In some embodiments, the controller 140 may be configured to provide instructions (control signals based on commands) and data to a plurality of locations of a particular bank 121 in the memory array 130, to the sensing component stripes 124-0, 124-1, . . . , 124-N−1 and/or to the in-memory data switching network 172 via the shared I/O lines 155 with control and data registers 151 and/or an instruction read path 161. For example, the control and data registers 151 and/or the instruction read path 161 may provide instructions to be executed using by the sense amplifiers and the compute components of the sensing circuity 150 in the sensing component stripes 124-0, 124-1, . . . , 124-N−1.
Implementations of PIM DRAM architecture may perform processing at the sense amplifier and compute component level. Implementations of PIM DRAM architecture may allow only a finite number of memory cells to be connected to each sense amplifier (e.g., around 512 memory cells). A sensing component stripe 124 may include from around 8,000 to around 16,000 sense amplifiers. For example, a sensing component stripe 124 may be configured to couple to an array of 512 rows and around 16,000 columns. A sensing component stripe may be used as a building block to construct the larger memory. In an array for a memory device, there may be 128 sensing component stripes, which corresponds to 128 subarrays, as described herein. Hence, 512 rows times 128 sensing component stripes would yield around 66,000 rows intersected by around 16,000 columns to form around a 1 gigabit DRAM.
As such, when processing at the sense amplifier level, there are only 512 rows of memory cells available to perform logic functions with each other and it may not be possible to easily perform logic functions on multiple rows where data is coupled to different sensing component stripes. To accomplish processing of data in different subarrays coupled to different sensing component stripes, all the data to be processed is moved into the same subarray in order to be coupled to the same sensing component stripe.
However, DRAM implementations have not been utilized to move data from one sensing component stripe to another sensing component stripe and/or from a memory array and/or sensing component stripe to an in-memory data switching network (e.g., a butterfly network by way of illustration and not by way of limitation). As mentioned, a sensing component stripe may contain as many as 16,000 sense amplifiers, which corresponds to around 16,000 columns or around 16,000 data values (e.g., bits) of data to be stored (e.g., cached) from each row. A DRAM DQ data bus (e.g., as shown at 156 in
In order to achieve data movement conducted with a high speed, rate, and efficiency from one sensing component stripe to another and/or to the data switching network 172 in PIM DRAM implementations, shared I/O lines 155 are described herein. For example, with 2048 shared I/O lines configured as a 2048 bit wide shared I/O line 155, movement of data from a full row, as just described, would take 8 cycles, a 32 times increase in the speed, rate, and efficiency of data movement. As such, compared other PIM DRAM implementations (e.g., relative to a 64 bit wide data path), utilization of the structures and processes described in the present disclosure saves time for data movement. In various embodiments, time may be saved, for example, by not having to read data out of one bank, bank section, and subarray thereof, storing the data, and then writing the data in another location and/or by reducing the number of cycles for data movement.
Accordingly, as shown and described, for example, in connection with
In some embodiments, the in-memory data switching network may be selectably coupled to a sense line (e.g., digit lines shown at 205 and 305 and described in connection with
As shown in
The plurality of subarrays shown at 125-0, 125-1, and 125-3 for short digit line subarrays and 126-0, 126-1, . . . , 126-N−1 for long digit line subarrays may each be coupled to and/or separated by sensing component stripes 124-0, 124-1, . . . , 124-N−1 that may include sensing circuitry 150 and logic circuitry (e.g., as shown at 713 and described in connection with
As shown schematically in
As described herein, an I/O line may be selectably shared by a plurality of partitions, subarrays, rows, particular columns of memory cells, and/or the data switching network 172 via the sensing component stripe coupled to each of the subarrays. For example, the sense amplifier and/or compute component of each of a selectable subset of a number of columns (e.g., eight column subsets of a total number of columns) may be selectably coupled to each of the plurality of shared I/O lines for data values stored (cached) in the sensing component stripe to be moved (e.g., transferred, transported, and/or fed) to each of the plurality of shared I/O lines.
In some embodiments, the controller 140 may be configured to direct by providing instructions (commands) and data to a plurality of locations of a particular bank 121 in the memory array 130 and to the sensing component stripes 124-0, 124-1, . . . , 124-N−1, via the shared I/O line 155 coupled to control and data registers 151. For example, the control and data registers 151 may relay the instructions to be executed by the sense amplifiers and/or the compute components of the sensing circuity 150 in the sensing component stripes 124-0, 124-1, . . . , 124-N−1.
However, the shared I/O line 155 and/or the connection circuitry 232 described herein may be configured (e.g., formed and/or enabled) to move a result of performance of a single operation or a sequential plurality of operations to a suitable location other than back to the first subset 125 and/or the second subset 126 of subarrays of memory array 130. For example, the result data value may, in various embodiments, be moved to an external register via the shared I/O line 155 and/or the connection circuitry 232. Embodiments of such external registers may include a number of bank registers (not shown) associated with (e.g., selectably coupled to) the controller 140 of the bank 121 of the memory device 120 and/or registers (not shown) associated with the host 110 (e.g., which may be accessed directly via data bus 156 by I/O circuitry 144 and/or indirectly via the controller 140 through the out-of-band bus 157). Moreover, data values for storage and/or processing, and/or commands for doing so, by a particular long digit line storage subarray and/or a particular short digit line cache subarray may be input. The input may be performed, for example, using a data transfer protocol such as DDR4, among others, from the host CPU directly via data bus 156 by I/O circuitry 144 and/or indirectly via the controller 140 through the control bus 154.
As described in connection with
Embodiments, however, are not so limited. For example, in various embodiments, there may be any number of short digit line subarrays 125 and any number of long digit line subarrays 126 in the bank section 123, which may be separated by isolation stripes into any number of partitions (e.g., as long as there is a combination of at least one short digit line subarray with at least one long digit line subarray in the various partitions). In various embodiments, the partitions may each include a same number or a different number of short and/or long digit line subarrays, sensing component stripes, etc., depending on the implementation.
Accordingly, as shown and described, for example, in connection with
The memory device 120 may include an in-memory data switching network (e.g., as shown at 172 and 372 and described in connection with
The memory device 120 may be configured to move a plurality of data values from the source location using a plurality of first sense amplifiers coupled to the respective plurality of shared I/O lines and move the plurality of data values to the destination location using a plurality of second sense amplifiers coupled to the plurality of shared I/O lines. The memory device 120 may, in some embodiments, be further configured to move a plurality of data values to the in-memory data switching network via the plurality of sense amplifiers selectably coupled to the respective plurality of shared I/O lines 155. The memory device 120 may, in some embodiments, be further configured to move a plurality of data values to the in-memory data switching network via a plurality of sense lines (e.g., digit lines shown at 205 and 305 and described in connection with
As described herein, the in-memory data switching network may include a plurality of levels each having a plurality of switch nodes. The plurality of levels of a data switching network 472 are shown at 409-0, . . . , 409-N−1 and described in connection with
In various embodiments, the number of switch nodes may be the same as the number of sense amplifiers coupled to the array or the number of switch nodes may be a multiple of or a fraction (e.g., an eighth, a sixteenth, etc.) of the number of sense amplifiers (e.g., via multiplexing with column select circuitry 358-1 and 358-2 shown in and described in connection with
The memory device 120 may, in various embodiments, include a plurality of subarrays (e.g., as shown at 125-0, 125-1, . . . , 125-N−1 and described in connection with
The memory device 120 may, in various embodiments, include a first subset (e.g., short digit line subarrays shown at 125-0 and 125-1 and described in connection with
The memory device 120 may, in various embodiments, include a sensing component stripe (e.g., as shown at 124-0, . . . , 124-N−1 and described in connection with
Each bank section, in some embodiments, may have a plurality of compute components 431-1, . . . , 431-Z and logic stripes 109-0, . . . , 109-N−1 in the compute unit 460 in a data path of the plurality of shared I/O lines 155 associated therewith. In various embodiments, the logic stripes also may include a plurality of switch nodes (e.g., as shown at 966 and described in connection with
As shown in the example embodiment of
The cells of the memory array 230 may be arranged in rows coupled by access (word) lines 204-X (Row X), 204-Y (Row Y), etc., and columns coupled by pairs of complementary sense lines (e.g., digit lines DIGIT(D) and DIGIT(D) shown in
Although rows and columns are illustrated as orthogonally oriented in a plane, embodiments are not so limited. For example, the rows and columns may be oriented relative to each other in any feasible three-dimensional configuration. For example, the rows and columns may be oriented at any angle relative to each other, may be oriented in a substantially horizontal plane or a substantially vertical plane, and/or may be oriented in a folded topology, among other possible three-dimensional configurations.
Memory cells may be coupled to different digit lines and word lines. For example, a first source/drain region of a transistor 202-1 may be coupled to digit line 205-1 (D), a second source/drain region of transistor 202-1 may be coupled to capacitor 203-1, and a gate of a transistor 202-1 may be coupled to word line 204-Y. A first source/drain region of a transistor 202-2 may be coupled to digit line 205-2 (D)_, a second source/drain region of transistor 202-2 may be coupled to capacitor 203-2, and a gate of a transistor 202-2 may be coupled to word line 204-X. A cell plate, as shown in
The memory array 230 is configured to couple to sensing circuitry 250 in accordance with a number of embodiments of the present disclosure. In this embodiment, the sensing circuitry 250 comprises a sense amplifier 206 and a compute component 231 corresponding to respective columns of memory cells (e.g., coupled to respective pairs of complementary digit lines). However, in some embodiments, the sensing circuitry 250 used for in data path compute operations performed by compute components of logic stripes may not include compute components in the sensing circuitry 250. The sense amplifier 206 may be coupled to the pair of complementary digit lines 205-1 and 205-2. If present, the compute component 231 may be coupled to the sense amplifier 206 via pass gates 207-1 and 207-2. The gates of the pass gates 207-1 and 207-2 may be coupled to operation selection logic 213.
The operation selection logic 213 may include pass gate logic for controlling pass gates that couple the pair of complementary digit lines un-transposed between the sense amplifier 206 and the compute component 231 and swap gate logic for controlling swap gates that couple the pair of complementary digit lines transposed between the sense amplifier 206 and the compute component 231. The operation selection logic 213 may also be coupled to the pair of complementary digit lines 205-1 and 205-2. The operation selection logic 213 may be configured to control continuity of pass gates 207-1 and 207-2 based on a selected operation.
The sense amplifier 206 may be operated to determine a data value (e.g., logic state) stored by a selected memory cell. The sense amplifier 206 may comprise a cross coupled latch, which may be referred to herein as a primary latch. In the example illustrated in
In operation, when a memory cell is being sensed (e.g., read), the voltage on one of the digit lines 205-1 (D) or 205-2 (D)_ will be slightly greater than the voltage on the other one of digit lines 205-1 (D) or 205-2 (D)_. An ACT signal and an RNL* signal may be driven low to enable (e.g., fire) the sense amplifier 206. The digit lines 205-1 (D) or 205-2 (D)_ having the lower voltage will turn on one of the PMOS transistor 229-1 or 229-2 to a greater extent than the other of PMOS transistor 229-1 or 229-2, thereby driving high the digit line 205-1 (D) or 205-2 (D)_ having the higher voltage to a greater extent than the other digit line 205-1 (D) or 205-2 (D)_ is driven high.
Similarly, the digit line 205-1 (D) or 205-2 (D)_ having the higher voltage will turn on one of the NMOS transistor 227-1 or 227-2 to a greater extent than the other of the NMOS transistor 227-1 or 227-2, thereby driving low the digit line 205-1 (D) or 205-2 (D)_ having the lower voltage to a greater extent than the other digit line 205-1 (D) or 205-2 (D)_ is driven low. As a result, after a short delay, the digit line 205-1 (D) or 205-2 (D)_ having the slightly greater voltage is driven to the voltage of the supply voltage VCC through a source transistor, and the other digit line 205-1 (D) or 205-2 (D)_ is driven to the voltage of the reference voltage (e.g., ground) through a sink transistor. Therefore, the cross coupled NMOS transistors 227-1 and 227-2 and PMOS transistors 229-1 and 229-2 serve as a sense amplifier pair, which amplify the differential voltage on the digit lines 205-1 (D) and 205-2 (D)_ and operate to latch a data value sensed from the selected memory cell.
Embodiments are not limited to the sense amplifier 206 configuration illustrated in
The sense amplifier 206 may, in conjunction with the compute component 231, be operated to perform various operations using data from an array as input. In a number of embodiments, the result of an operation may be stored back to the array without transferring the data via a digit line address access (e.g., without firing a column decode signal such that data is transferred to circuitry external from the array and sensing circuitry via local I/O lines). As such, a number of embodiments of the present disclosure may enable performing operations and compute functions associated therewith using less power than various previous approaches. Additionally, since a number of embodiments eliminate the need to transfer data across local and global I/O lines in order to perform compute functions (e.g., between memory and discrete processor), a number of embodiments may enable an increased (e.g., faster) processing capability as compared to previous approaches.
The sense amplifier 206 may further include equilibration circuitry 214, which may be configured to equilibrate the digit lines 205-1 (D) and 205-2 (D)_. In this example, the equilibration circuitry 214 comprises a transistor 224 coupled between digit lines 205-1 (D) and 205-2 (D)_. The equilibration circuitry 214 also comprises transistors 225-1 and 225-2 each having a first source/drain region coupled to an equilibration voltage (e.g., VDD/2), where VDD is a supply voltage associated with the array. A second source/drain region of transistor 225-1 may be coupled digit line 205-1 (D), and a second source/drain region of transistor 225-2 may be coupled digit line 205-2 (D)_. Gates of transistors 224, 225-1, and 225-2 may be coupled together, and to an equilibration (EQ) control signal line 226. As such, activating EQ enables the transistors 224, 225-1, and 225-2, which effectively shorts digit lines 205-1 (D) and 205-2 (D)_ together and to the equilibration voltage (e.g., VCC/2).
Although
As described further below, in a number of embodiments, the sensing circuitry 250 (e.g., sense amplifier 206 and compute component 231) may be operated to perform a selected operation and initially store the result in one of the sense amplifier 206 or the compute component 231 without transferring data from the sensing circuitry via a local or global I/O line (e.g., without performing a sense line address access via activation of a column decode signal, for instance).
However, in embodiments described herein, sensing circuitry 250 having sense amplifiers 206, which in some embodiments may also include compute components 231 as shown in
Performance of operations (e.g., Boolean logical operations involving data values) is fundamental and commonly used. Boolean logical operations are used in many higher level operations. Consequently, speed and/or power efficiencies that may be realized with improved operations, may translate into speed and/or power efficiencies of higher order functionalities.
As shown in
The logic stripes 409-0, . . . , 409-N−1 may correspond to the in-memory data switching network 472 described herein. The logic stripes (e.g., a subset or all of the logic stripes in compute unit 460) also may correspond to the levels (e.g., a shown at 967-0, 967-1, 967-N−1 and described in connection with
As described herein, a memory device (e.g., 120 in
Each bank section 123 may be associated with a plurality of logic stripes (e.g., 109-0, 109-1, . . . , 109-N−1 in
The memory device may include a logic stripe (e.g., 109 in
In some embodiments, a number of a plurality of logic stripes (e.g., 109-0, . . . , 109-N−1 in
In various embodiments, connection circuitry 232-1 may, for example, be coupled at 217-1 and connection circuitry 232-2 may be coupled at 217-1 to a primary latch 215 (e.g., sense amplifier 206 serving as a latch associated with a compute component 231 in a logic stripe) for movement of sensed, stored, and/or data values of a logic stripe on which an operation has been performed. The data values may be moved to a selected latch, compute component 231, and/or switch node 966 in another logic stripe, as described herein, directly (e.g., as a bit serial link) via the connection circuitry 232-1 and 232-2 (e.g., without movement via a shared I/O line).
Although
As the reader will appreciate, each shared I/O line 355 (
Data values present on the pair of complementary digit lines 305-1 and 305-2 may be loaded into the sense amplifier 306-0 as described in connection with
The sense amplifiers 306-0, 306-1, . . . , 306-7 in
The configurations of embodiments illustrated in
The circuitry illustrated in
Controller 140 may be coupled to column select circuitry 358 to control select lines (e.g., select line 0) to access data values stored by the sense amplifiers, compute components, and/or present on the pair of complementary digit lines (e.g., 305-1 and 305-2 when selection transistors 359-1 and 359-2 are activated via signals from select line 0). Activating the selection transistors 359-1 and 359-2 (e.g., as directed by the controller 140) enables coupling of sense amplifier 306-0, compute component 331-0, and/or complementary digit lines 305-1 and 305-2 of column 0 (322-0) to move data values on digit line 0 and digit line 0* to shared I/O line 355. For example, the moved data values may be data values from a particular row 319 stored (cached) in sense amplifier 306-0 and/or compute component 331-0. Data values from each of columns 0 through 7 may similarly be selected by controller 140 activating the appropriate selection transistors.
Moreover, enabling (e.g., activating) the selection transistors (e.g., selection transistors 359-1 and 359-2) may enable a particular sense amplifier and/or compute component (e.g., 306-0 and/or 331-0, respectively) and/or complementary digit lines 305-1 and 305-2 of column 0 (322-0) to be coupled with a shared I/O line 355 such that the data values may be moved to (e.g., placed on and/or transferred to) the shared I/O line 355. In some embodiments, one column at a time is selected (e.g., column 322-0) to be coupled to a particular shared I/O line 355 to move (e.g., copy, transfer, and/or transport) the stored data values. In the example configuration of
Ordinal numbers, as used herein, may not be used to indicate a particular ordering and/or relationship between the components. For example, movement of a first data value from a first subrow of a first row of a memory array via the shared I/O lines to a first compute component of a first logic stripe is intended to indicate that a particular data value from a particular subrow (which may be, but is not necessarily, the first subrow in a sequence of subrows) of a particular row may be moved to a particular compute component of a particular logic stripe (each of which may be, but is not necessarily, the first in a sequence of compute components and/or logic stripes). Similarly, movement of a second data value from a second subrow of the first row (which may be a next subrow adjacent the previously mentioned first subrow but may be, but is not necessarily, the second subrow in the sequence of subrows) is intended to indicate that a particular data value from the second subrow of the same row may be moved to a particular compute component of a different logic stripe. For example, referring to the second data value being moved to the second compute component of the second logic stripe is used to associate the second data value with a compute component and/or a logic stripe that is different than those previously referred to as the first of such components. As such, the second compute component may be, but is not necessarily, the first compute component in a sequence of compute components of the second logic stripe and/or the second logic stripe may be, but is not necessarily, the second logic stripe in a sequence of logic stripes.
Similarly, as described herein, a controller being configured to direct, in a first operation cycle, a first parallel movement (e.g., via the shared I/O lines) of a number of a plurality of data values of the first subrow to a corresponding number of a plurality of first compute components of the first logic stripe is intended to indicate that the controller may direct performance in a specific operation cycle (e.g., in a time frame of around 2 to 60 nanoseconds (ns)) of movement of a particular number corresponding to the plurality of data values of the first subrow to the same number of compute components of the first logic stripe. The controller being configured to direct, in a second operation cycle, a second parallel movement of a number of a plurality of data values of the second subrow to a corresponding number of a plurality of second compute components of the second logic stripe is intended to indicate that in the second operation cycle (which may be, but is not necessarily, the next, e.g., adjacent, 2-60 ns time frame) the controller may direct performance of movement of a particular number corresponding to the plurality of data values of the second subrow to the same number of compute components of the second logic stripe. The particular number of the plurality of data values of the second subrow and/or of the second compute components of the second logic stripe may be, but is not necessarily, the same number as that of the data values of the first subrow and/or of the first compute components of the first logic stripe.
As described herein, the plurality of shared I/O lines 455 may be selectably shared by a plurality of subarrays, bank sections, quadrants, rows, subrows, and/or particular columns of memory cells via select logic coupled to each array. For example, the sensing circuitry 150 and/or additional latches 170, including a sense amplifier and select logic for multiplexing each of a selectable number of subsets of a number of columns (e.g., 8, 16, etc., column subsets of a total number of columns) may be selectably coupled to each of the plurality of shared I/O lines 455 for data values to be moved to the plurality of compute components 431-1, . . . , 431-Z and/or logic stripes 409-0, . . . , 409-N−1 in a compute unit 460 in a data path of the plurality of shared I/O lines 455. In some embodiments, the plurality of compute components 431-1, . . . , 431-Z selectably coupled to each of the plurality of shared I/O lines 455 may correspond to the number of columns selectably coupled to the plurality of shared I/O lines (e.g., 1K, 2K, etc.).
The plurality of shared I/O lines 455 may selectably couple a first subrow of a row of the array via the sensing circuitry to a first compute component 431 and/or switch node 966 (e.g., a number of latches 970 and/or switches 963 of each switch node 966 as described in connection with
In some embodiments, the compute component and/or switch node may be in a logic stripe (e.g., as shown at 409-0, 409-1, . . . , 409-N−1 and described in connection with
In various embodiments, each of the plurality of compute components and/or switch nodes may be shifted to another one of the plurality of shared I/O lines of the data path. For example, the number of columns and/or memory cells (e.g., 16,384 columns and/or memory cells, among other possible configurations) of a row (e.g., as shown at 319 and described in connection with
The memory device 120 includes a controller (e.g., as shown at 140 and described in connection with
The present disclosure describes enablement of in data path compute operations (e.g., PIM operations, such as AND, OR, refresh, row copy, shift, add, multiply, etc.) and switch operations, as described herein, to be performed on data values stored by memory cells (e.g., when moved to a compute component and/or switch nodes, as described herein) substantially simultaneously with performance of, for example, read and/or write operations on data values from a same bank, a same subarray in the same bank, and/or a same row in the same subarray (e.g., in a DRAM array, among other types of memory arrays). For example, the movement operation may be performed on data values stored in a subrow of memory cells in a row of a subarray substantially simultaneously with performance of, for example, logical operations on the same data values previously moved to a compute component and/or switch node in the data path (e.g., to a selected logic stripe) as directed by a controller and/or a host, as described herein.
Accordingly, when a subrow is activated to be sensed in an array, a plurality of data values stored by memory cells of the subrow (e.g., data values for the entire subrow) may be moved (e.g., copied, transferred, and/or transported) to a corresponding plurality of compute components and/or switch nodes (e.g., that each form at least a portion of a logic stripe 409 in a compute unit, as shown at 460 and described in connection with
The present disclosure describes, in some embodiments, that when a row is sensed, the data values in the row (e.g., the data values from all 16,384 (16K) memory cells in the row) may be moved to be stored (e.g., cached) in a latch component (e.g., a sense amplifier) to be further moved on a shared I/O line to a logic stripe in a compute unit in the data path of the shared I/O that is local to the array. In some embodiments, 2048 (2K) shared I/O lines may be configured as a 2K bit wide shared I/O line. According to some embodiments, a number of cycles for moving the data from a first row in a source location to a second row in a destination location may be determined by dividing a number of columns in the array intersected by a row of memory cells in the array by the 2K bit width of the plurality of shared I/O lines. For example, an array (e.g., a bank, a bank section, or a subarray thereof) may have 16K columns, which may correspond to 16K data values in a row, which when divided by the 2K bit width of the plurality of shared I/O lines intersecting the row may yield eight cycles, each separate cycle being at substantially the same point in time (e.g., in parallel) for movement of each 2K bit fraction of the data in the row such that all 16K data bits in the row are moved after completion of the eight cycles. For example, only one of a plurality (e.g., a subset of eight, as shown in
In one example, 2K data values may be multiplexed at a time (e.g., in parallel) through 2K shared I/O lines from 2K sense amplifiers of the 16K columns (e.g., digit line pairs) by an eight way multiplexer to 2K compute components and/or switch nodes (e.g., to store and/or process a total of 2K bits) in each logic stripe (e.g., each logic stipe having 2K compute components and/or switch nodes) of a compute unit. In some embodiments, the compute unit may have eight logic stripes to store 2K data values per logic stripe, thereby being capable of storing 16K data values per compute unit that have been moved in eight cycles by the 2K shared I/O lines. In another example, 1K data values may be multiplexed at a time through 1K shared I/O lines from 1K sense amplifiers of the 16K columns by a sixteen way multiplexer to 1K compute components and/or switch nodes (e.g., to store and/or process a total of 1K bits) in a logic stripe (e.g., each logic stipe having 1K compute components) of a compute unit. In some embodiments, the compute unit (e.g., as shown at 460 and described in connection with
As such, the memory cells in the bank, the subarray, the row, and/or the subrow from which the data values were moved may be available to perform compute and/or switch operations on other data values stored therein (e.g., by having the original data values moved to a logic stripe in the compute unit in the data path of the shared I/O that is local to the array). In various embodiments, each logic stripe may include a number of a plurality of latches, corresponding to (e.g., the same as or an integer multiple of) the number of compute components and/or switch nodes, to store a plurality of data values moved from another bank, subarray, row, and/or subrow to enable performance of a number of operations (e.g., logical and/or switch operations) on the data values stored by the latches associated with the compute component and/or switch nodes.
Implementations of DRAM architecture for in data path compute operations may perform processing at the sense amplifier and compute component level (e.g., in a logic stripe) and/or switch operations at the latch and switch level. Implementations of the DRAM architecture for in data path compute and/or switch operations may allow only a finite number of memory cells to be connected to the compute components in a logic stripe in the data path of the shared I/O lines (e.g., 1K memory cells as given in one example above). An array may include from around 8K to around 16K columns (pairs of digit lines) and associated sense amplifiers. In some embodiments, for example as shown in
In some embodiments, a plurality of logic stripes as part of a compute unit may be associated with each quadrant. For example each logic stripe in a compute unit in the data path of the shared I/O lines may be associated with a subarray in each quadrant of a bank. Thus, in the above example, a compute unit in the data path of the shared I/O lines local to the array may have 128 logic stripes (4 quadrants, one logic stripe for each of 32 subarrays per quadrant). Embodiments, however, are not limited to this illustrative example. A bank of memory (e.g., of memory cells in a DRAM array) may, in some embodiments, include 64K rows by 16K columns of DRAM to provide around 1 gigabit of memory.
The present disclosure describes a compute component and/or switch node in a data path of a shared I/O line local to an array that may include a plurality of latches that function as sense amplifiers to store (cache) data values moved (e.g., copied, transferred, and/or transported) from sensing circuitry associated with the array. The compute components and/or switch nodes may be in a plurality of logic stripes in a compute unit in the data path of a plurality of shared I/O lines local to the array such that the plurality of logic stripes each includes a subset of a total number of compute components and/or switch nodes. The compute components 431-1, . . . , 431-Z and/or switch nodes 966-0, . . . , 966-M−1 of logic stripes 409-0, . . . , 409-N−1 (e.g., as shown and described in connection with
As such, the architecture for in data path compute operations may facilitate movement (e.g., copying, transferring, and/or transporting) of data values stored in a subrow of a row of an array to the compute components, switch nodes, and/or logic stripes in the data path of the plurality of shared I/O lines local to the array. Sensing circuitry 150 having sense amplifiers, which in some embodiments may also include compute components as shown in
The memory array architecture may provide a number of benefits in addition to those just described. Overall processing speed may be increased by, for example, enabling logical operations and/or switch operations to be performed on data stored by memory cells in parallel with performance of other operations (e.g., performance of DDR4 I/O operations). For example, the logical operations and/or switch operations may be performed in a compute unit having a plurality of compute components 431-1, . . . , 431-Z, switch nodes 966-0, . . . , 966-M−1, and/or logic stripes 409-0, . . . , 409-N−1 in the data path of the shared I/O lines 455 local to the array. By way of example and not by way of limitation, once data values are loaded to the plurality of compute components, switch nodes and/or logic stripes in the compute unit from the subrows of the array, compute operations may be controlled in the compute unit at speeds of 2 ns without having to move the data values back into the rows, as compared to an example time required to fire the rows in the array of 60 ns. In this manner, the compute components, switch nodes, and/or logic stripes (along with associated latches) may provide storage of the moved data values for performance of certain functions (e.g., AND, OR, NOR, XOR, add, subtract, multiply, divide, switch operations, etc.) while the original data values of a subrow may be saved back to a row, saved elsewhere, and/or written over. As discussed more in connection with
In the embodiment of
For example, a bit from a first sense amplifier and/or memory cell in a sequence of the first subrow 465-1 may be directed (e.g., by the controller 140) for storage by a first compute component 431-1 and/or a first switch node 966-0, or an associated latch, in the sequence of compute components in the first logic stripe 409-0. A bit from a second sense amplifier and/or memory cell in the sequence of the first subrow 465-1 may be directed for storage by a second compute component 431-2 and/or a second switch node 966-1, or an associated latch, in the sequence of compute components and/or switch nodes in the first logic stripe 409-0. Further, a bit from a first sense amplifier and/or memory cell in a sequence of the second subrow 465-2 may be directed for storage by a first compute component 431-1 and/or a first switch node 966-0, or an associated latch, in the sequence of compute components in the second logic stripe 409-1. A bit from a second sense amplifier and/or memory cell in the sequence of the second subrow 465-2 may be directed for storage by a second compute component and/or a second switch node, or an associated latch, in the sequence of compute components in the second logic stripe 409-1. Bits corresponding to each sense amplifier and/or memory cell in the sequence of subrows 465-2465-1, . . . , 465-16 per row may similarly be designated for storage by a corresponding compute component and/or switch node, or an associated latch, in the sequence in the sequence of logic stripes 409-0, . . . , 409-N−1 (e.g., data values from subrow 465-1 are moved to logic stripe 409-0, data values from subrow 465-2 are moved to logic stripe 409-1, etc.). Movement may be directed to a designated logic stripe via the shared I/O lines 455, which may provide a 1K bit wide data path to the compute unit 460.
In the example of
In some embodiments, the controller 140 (
In some embodiments, the shared I/O lines may be used to connect the 1K data values to a respective one of the plurality of compute components 431-1, . . . , 431-Z and/or switch nodes 966-0, . . . , 966-M−1 in a respective one of the plurality of logic stripes 409-0, . . . , 409-N−1. By way of example and not by way of limitation, 1K bits of the data values may be moved in parallel to a particular logic stripe associated with each subrow. In various embodiments, there may, for example, be a compute unit 460 associated with each of the 32 subarrays 425-1, . . . , 425-32 in each of 4 quadrants of a bank section 423 or compute units may be shared between various combinations of the subarrays, quadrants, and/or bank sections. Data values loaded to the plurality of compute components 431-1, . . . , 431-Z and/or switch nodes 966-0, . . . , 966-M−1 in the logic stripes 409-0, . . . , 409-N−1 of the compute unit 460 may be operated on according to microcode instructions from the controller 140 (
As described herein, for example, once the 1K data values of a first subrow 465-1 are moved (e.g., loaded) to a first logic stripe 409-0 of the compute unit 460, compute and/or switch operations may be initiated on such data values before and/or substantially simultaneously with data values from a second subrow 465-2 being moved to a second logic stripe 409-1 of the compute unit 460. Such operations performed in the logic stripe of the compute unit may be controlled much faster (e.g., at speeds of approximately 2 ns) according to microcode instructions executed by the controller 140 (
Accordingly, a memory device 120 may include, in various embodiments, a plurality of I/O lines shared as a data path for in data path compute operations associated with an array 130 of memory cells. The plurality of shared I/O lines may selectably couple a first subrow (e.g., 465-1) of a row of the array via the sensing circuitry (e.g., 350) to a first compute component (e.g., 431-1) and/or a first switch node (e.g., 966-0) in the data path to move a first data value from the first subrow to the first compute component and/or the first switch node. The plurality of shared I/O lines may selectably couple a second subrow (e.g., 465-2) of the respective row via the sensing circuitry to a second compute component and/or switch node (e.g., corresponding to the position of the first compute component and/or switch node in the first logic stripe) in the data path to move a second data value from the second subrow to the second compute component and/or switch node. For example, the first logic stripe (e.g., 409-0) may include the first compute component and/or the first switch node and a second logic stripe (e.g., 409-1) may include the second compute component and/or the second switch node. As described herein, an operation may be performed on the first data value from the first subrow using the first compute component substantially simultaneously with movement of the second data value from the second subrow to the second compute component.
In various embodiments, the data path may further include the first logic stripe (e.g., 409-0) that may include a number of a plurality of first compute components and/or first switch nodes that corresponds to a number of a plurality of memory cells (not shown) of the first subrow (e.g., 465-1) and the second logic stripe (e.g., 409-1) that may include a number of a plurality of second compute components and/or switch nodes that corresponds to a number of a plurality of memory cells of the second subrow (e.g., 465-2). A number of a plurality of logic stripes (e.g., 409-0, . . . , 424N) may correspond to a number of a plurality of subrows (e.g., 465-1, . . . , 465-16) of the respective row. A compute unit (e.g., 460) may include a plurality of logic stripes (e.g., 409-0, . . . , 424N) that may each include a plurality of compute components (e.g., 431-1, . . . , 431-Z) and/or switch nodes (e.g., 966-0, . . . , 966-M−1), where each of the plurality of compute components may be associated with (e.g., selectably coupled to) at least one of the plurality of shared I/O lines 455 local to the array. A number of the plurality of shared I/O lines may correspond to a number of a plurality of memory cells of a subrow of the respective row (e.g., an individual shared I/O line for every 8 or 16 memory cells and/or columns of the subrow or row, among other possible configurations). A logic stripe (e.g., 409-0) may include a number of a plurality of compute components and/or switch nodes that corresponds to the number of the plurality of memory cells of the subrow coupled to a respective logic stripe.
As shown in
The control logic 531-0, . . . , 531-7 in the example shown in
The control logic 531-0, . . . , 531-7 may decode microcode instructions into function calls (e.g., microcode function calls (uCODE)) implemented by the sequencers 532-0, . . . , 532-7.
As described in connection with
In various embodiments, the control logic 531-0, . . . , 531-7, sequencers 532-0, . . . , 532-7, and timing circuitry 533-0, . . . , 533-7 may operate to generate sequences of operation cycles for a DRAM array and/or direct the performance of operations (e.g., logical and/or switch operations) on the memory device 520 (e.g., on a bank 521-0, . . . , 521-7 including in a compute unit 460/660 in a data path of the shared I/O lines 455-0, . . . , 455-7). In the PIM capable device example, each sequence may be designed to perform operations, such as a Boolean logic operations AND, OR, XOR, etc., which together achieve a specific function. For example, the sequences of operations may repetitively perform a logical operation for a one (1) bit add in order to calculate a multiple bit sum. In another example, instructions for the sequences of operations may be executed to perform a number of switch operations, among various other types of operations. Each sequence of operations may be fed into a first in/first out (FIFO) buffer coupled to the timing circuitry 533-0, . . . , 533-7 to provide timing coordination with the sensing circuity 150, compute unit 460/660, and/or additional logic circuitry 713 associated with the array of memory cells 130 (e.g., DRAM arrays) shown in
In the example PIM capable memory device 520 shown in
In the embodiment of
The plurality of shared I/O lines 655 described herein may connect the array 130 (
At 604, a condition code from a wired OR logic configuration may provide a bit value result of a wired OR operation with the compute unit 660. At 611 bit values may provide a register address as a pointer to a second register source for compute component operation and/or switch node operation instructions. At 612, bit values may indicate a register index of a logic stripe 609-0, . . . , 609-N−1 of the compute unit 660 together with the register address pointer to a second register source for compute component operation and/or switch node operation instructions 611.
In some embodiments, there may be a plurality of latches 706 associated with a compute component 731 such that the latches may, in various embodiments, be selectably, directly, and/or indirectly coupled to the shared I/O line to load a data value to each of the latches, which may then be selectably used (e.g., as directed by a controller) by an associated compute component for performance of a plurality of logical operations (e.g., as determined by the number of latches squared). Hence, pass gates 707-1 and 707-2 may be used in various embodiments to directly and/or indirectly couple the latches 706, compute components 731, and/or logical operation select logic 713 to each other and/or indirectly connect the shared I/O line 755 to the latches 706, compute components 731, and/or logical operation select logic 713.
The latch 706 shown in
In the embodiment illustrated in
The compute unit 460/660 circuitry shown in
According to various embodiments, the operation selection logic 713 may include four logic selection transistors: logic selection transistor 762 coupled between the gates of the swap transistors 742 and a TF signal control line, logic selection transistor 752 coupled between the gates of the pass gates 707-1 and 707-2 and a TT signal control line, logic selection transistor 754 coupled between the gates of the pass gates 707-1 and 707-2 and a FT signal control line, and logic selection transistor 764 coupled between the gates of the swap transistors 742 and a FF signal control line. Gates of logic selection transistors 762 and 752 are coupled to the true sense line through isolation transistor 750-1 (having a gate coupled to an ISO signal control line). Gates of logic selection transistors 764 and 754 are coupled to the complementary sense line through isolation transistor 750-2 (also having a gate coupled to an ISO signal control line).
Data values present on the pair of complementary shared I/O lines 755-1 and 755-2 may be loaded into the compute component 731 via the pass gates 707-1 and 707-2. The compute component 731 may comprise a loadable shift register. When the pass gates 707-1 and 707-2 are OPEN, data values (“A”) on the pair of complementary shared I/O lines 755-1 and 755-2 are passed to the compute component 731 and thereby loaded into the loadable shift register. The data values on the pair of complementary shared I/O lines 755-1 and 755-2 may be the data value (“B”) stored by the sense amplifier 706 when the sense amplifier is fired. In this example, the logical operation selection logic signal, Pass, is high to OPEN the pass gates 707-1 and 707-2.
The ISO, TF, TT, FT, and FF control signals may operate to select a logical function to implement based on the data value (“B”) in the sense amplifier 706 and the data value (“A”) in the compute component 731. In particular, the ISO, TF, TT, FT, and FF control signals are configured to select the logical function to implement independent from the data value present on the pair of complementary shared I/O lines 755-1 and 755-2 (although the result of the implemented logical operation may be dependent on the data value present on the pair of complementary shared I/O lines 755-1 and 755-2. For example, the ISO, TF, TT, FT, and FF control signals select the logical operation to implement directly since the data value present on the pair of complementary shared I/O lines 755-1 and 755-2 is not passed through logic to operate the gates of the pass gates 707-1 and 707-2.
Additionally,
The logical operation selection logic 713 signal Pass may be activated (e.g., high) to OPEN the pass gates 707-1 and 707-2 (e.g., conducting) when the ISO control signal line is activated and either the TT control signal is activated (e.g., high) with data value on the true shared I/O line is “1” or the FT control signal is activated (e.g., high) with the data value on the complement shared I/O line is “1.”
The data value on the true shared I/O line being a “1” OPENs logic selection transistors 752 and 762. The data value on the complimentary shared I/O line being a “1” OPENs logic selection transistors 754 and 764. If the ISO control signal or either the respective TT/FT control signal or the data value on the corresponding shared I/O line (e.g., shared I/O line to which the gate of the particular logic selection transistor is coupled) is not high, then the pass gates 707-1 and 707-2 will not be OPENed by a particular logic selection transistor.
The logical operation selection logic signal Pass* may be activated (e.g., high) to OPEN the swap transistors 742 (e.g., conducting) when the ISO control signal line is activated and either the TF control signal is activated (e.g., high) with data value on the true shared I/O line is “1,” or the FF control signal is activated (e.g., high) with the data value on the complement shared I/O line is “1.” If either the respective control signal or the data value on the corresponding shared I/O line (e.g., shared I/O line to which the gate of the particular logic selection transistor is coupled) is not high, then the swap transistors 742 will not be OPENed by a particular logic selection transistor.
The Pass* control signal is not necessarily complementary to the Pass control signal. It is possible for the Pass and Pass* control signals to both be activated or both be deactivated at the same time. However, activation of both the Pass and Pass* control signals at the same time shorts the pair of complementary shared I/O lines together, which may be a disruptive configuration to be avoided.
The compute unit 460/660 circuitry illustrated in
Logic Table 8-1 illustrated in
Via selective control of the continuity of the pass gates 707-1 and 707-2 and the swap transistors 742, each of the three columns of the upper portion of Logic Table 8-1 may be combined with each of the three columns of the lower portion of Logic Table 8-1 to provide 3×3=9 different result combinations, corresponding to nine different logical operations, as indicated by the various connecting paths shown at 875. The nine different selectable logical operations that may be implemented by the compute unit 460/660 circuitry are summarized in Logic Table 8-2 illustrated in
The columns of Logic Table 8-2 illustrated in
Each of the levels 967-0, . . . , 977-N−1 is shown to include a plurality of switch nodes 966-0, . . . , 966-M−1. The number of the plurality of switch nodes 966-0, . . . , 966-M−1 may correspond to a number of memory cells in a row of an array (e.g., 4K, 8K, 16K, etc., memory cells as described in connection with
Data values moved to a switch node 966 may be stored by a number of latches 970 of the switch node and switch operations may be performed on the stored data values by the switch 963 of the switch node. In some embodiments, there may be a plurality of latches 970 associated with a switch 963 such that the latches may, in various embodiments, be selectably, directly, and/or indirectly coupled to the shared I/O line to load a data value to each of the latches, which may then be selectably used (e.g., as directed by a controller) by an associated switch for performance of a plurality of switch operations (e.g., as determined by the number of latches squared).
In some embodiments, each of the switch nodes in a level may be configured to perform a fixed switch operation. For example, each switch node 966-0, . . . , 966-M−1 in the first level 967-0 may be configured to switch (e.g., via connection circuitry 232 described herein) a received data value to a predetermined position in a second level 967-1 of a plurality (e.g., sequence) of levels 967-0, . . . , 967-N−1 configured to achieve the intended completed switch operation on data values by passage through the designated switch nodes in the sequence of levels. As shown in
In some embodiments, each of the switch nodes in a level may be configured to perform a plurality of movements (e.g., switches) of data values. A controller 140 (e.g., as described in connection with
In some embodiments, each switch node 966-0, . . . , 966-M−1 itself may be considered a programmable multiplexer. For example, an embodiment consistent with the data switching network 972-1 implemented as levels 967-0, . . . , 977-N−1 (e.g., in a two-dimensional topology, although not so limited) may have a network topology that consists of (k+1)2k switch nodes. The switch nodes may be arranged in k+1 ranks, each having n=2k switch nodes, where k represents the order of the network. In a data switching network where each level includes, for example, 256 (28) switch nodes (e.g., is 28 bits wide), the depth of the data switching network may be determined by: (8+1)28=2304 switch nodes that may be uniformly distributed in 9 levels (e.g., 2304÷256=9).
For example, each switch node 966-0, . . . , 966-M−1 in the first level 967-0 may be configured to switch a received data value to a plurality of positions in a second level 967-1 of the plurality (e.g., sequence) of levels 967-0, . . . , 967-N−1 depending on which instructions are sent from the switching component 171 to enable a particular switch protocol. Accordingly, passage of the data values through the designated switch nodes in the sequence of levels may be configured to achieve a plurality of switch operations (e.g., a different switch operation in each level) to achieve the intended completed switch operations (e.g., as determined by selection from a plurality of switch protocols).
A memory device 120 may include an array (e.g., bank section of the array shown at 423 including subarrays 425-1, . . . , 425-32 and described in connection with
The memory device 120 may further include a controller (e.g., as shown at 140 and described in connection with
In some embodiments, the first logic stripe (e.g., 409-0 in
The controller may be further configured to direct movement, via the shared I/O line, to the array of a data value (e.g., to a memory cell of a row in subarrays 425-1, . . . , 425-32 shown in and described in connection with
The controller may be further configured to selectably enable the first switch protocol from a plurality of switch protocols. The first switch protocol may be enabled by execution of instructions sent (e.g., via switching component 171 and instruction described in connection with
In various embodiments, the first logic stripe (e.g., 409-0 in
The embodiment illustrated in
In some embodiments, the controller 140 (e.g., the switching component 171 thereof) may direct that the switch nodes 966-0, . . . , 966-M−1 in each of levels 967-0, . . . , 966-M−1 (e.g., four levels) are configured (e.g., enabled, programmed, etc.) to perform a first portion 969-1 of a sequence of switch operations. Upon completion of the first portion 969-1 of the sequence, the resulting data values may be stored (e.g., in a corresponding number of latches 968-0, . . . , 968-M−1 coupled to the switch nodes in the last level 967-N−1).
The controller 140 may then direct that the switch nodes 966-0, . . . , 966-M−1 in each of levels 967-0, . . . , 966-M−1 (e.g., four levels) are reconfigured to perform a second portion 969-2 of the sequence of switch operations (e.g., in which the switch operations performed in at least one of the levels differ from the switch operations performed in the first portion 969-1 of the sequence). In some embodiments, the second portion 969-2 of the sequence may be performed by passage of the data values in an opposite direction through the levels compared to passage in the first portion 969-1. Upon completion of the second portion 969-2 of the sequence, the resulting data values may be stored (e.g., in a corresponding number of latches 968-0, . . . , 968-M−1 coupled to the switch nodes in the first level 967-0). In some embodiments, the second portion 969-2 of the sequence may be performed by passage of the data values in the same direction as the passage in the first portion 969-1 by, for example, looping the result data values from the last level 967-N−1 to the first level 967-0.
The number of portions (e.g., 969-1, 969-2, . . . , 969-M) of the sequence of switch operations performed as such is unlimited, which may continuously make the fraction of the sequence performed in each passage smaller. Passing the data values in a plurality of portions though the same levels as such to achieve the intended completed switch operation may reduce the area utilized on the chip for the levels of the in-memory data switch network and/or the cost thereof. In some embodiments, the portions 969 just described may correspond to partitions of an array (e.g., as shown at 128 and described in connection with
Hence, the memory device 120, as just described, may be configured to perform switch operations via the sensing circuitry, the shared I/O line, the connection circuitry, and/or the switch nodes positioned in the data path. The switch operations described herein thereby include operations that differ from operations performed by previous implementations of butterfly networks that are positioned outside the data path (e.g., butterfly networks that include hardware, firmware, and/or software components located at positions other than in the data path described herein).
Accordingly, embodiments described herein provide a method for operating a memory device for in-memory data switching networks that may be performed by execution of non-transitory instructions by a processing resource. As described herein, the method may include performing on a data value, by a first logic stripe (e.g., logic stripe 409-0 shown in and described in connection with
The method may further include completing performance of the second subset of the plurality of switch operations by sequentially moving the data value resulting from completion of performance of the first subset of the plurality of switch operations from the last logic stripe to the first logic stripe. The method may, in some embodiments, further include directing, by the controller, that the switch operation performed by the last logic stripe as the last switch operation of the first subset is different from the first switch operation of the second subset performed by the last logic stripe.
The method may further include storing, by a latch (e.g., as shown at 968-0, . . . , 968-M−1) coupled to a switch node of the last logic stripe (e.g., last level 967-N−1), a data value resulting from performance by the last logic stripe of the last switch operation of the first subset 969-1 and initiating, by the last logic stripe, performance of the first switch operation of the second subset 969-2 of the plurality of switch operations on the stored data value. The method may further include storing, by a latch (e.g., as shown at 968-0, . . . , 968-M−1) coupled to a switch node of the first logic stripe (e.g., first level 967-0), a data value resulting from performance by the first logic stripe of a last switch operation of the second subset 969-2 and moving, via the shared I/O line, the stored data value to the array (e.g., to a memory cell of a row in subarrays 425-1, . . . , 425-32 shown in and described in connection with
While example embodiments including various combinations and configurations of sensing circuitry, sense amplifiers, compute components, latches, logic stripes, shared I/O lines, column select circuitry, connection circuitry, multiplexers, in-memory data switching networks, levels thereof, switch nodes, switches, etc., have been illustrated and described herein, embodiments of the present disclosure are not limited to those combinations explicitly recited herein. Other combinations and configurations of the sensing circuitry, sense amplifiers, compute components, latches, logic stripes, shared I/O lines, column select circuitry, connection circuitry, multiplexers, in-memory data switching networks, levels thereof, switch nodes, switches, etc., disclosed herein are expressly included within the scope of this disclosure.
Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art will appreciate that an arrangement calculated to achieve the same results may be substituted for the specific embodiments shown. This disclosure is intended to cover adaptations or variations of one or more embodiments of the present disclosure. It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combination of the above embodiments, and other embodiments not specifically described herein will be apparent to those of skill in the art upon reviewing the above description. The scope of the one or more embodiments of the present disclosure includes other applications in which the above structures and processes are used. Therefore, the scope of one or more embodiments of the present disclosure should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.
In the foregoing Detailed Description, some features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the disclosed embodiments of the present disclosure have to use more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
This application is a Continuation of U.S. application Ser. No. 15/465,340, filed Mar. 21, 2017, the contents of which are included herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4380046 | Fung | Apr 1983 | A |
4435792 | Bechtolsheim | Mar 1984 | A |
4435793 | Ochii | Mar 1984 | A |
4727474 | Batcher | Feb 1988 | A |
4843264 | Galbraith | Jun 1989 | A |
4958378 | Bell | Sep 1990 | A |
4977542 | Matsuda et al. | Dec 1990 | A |
5023838 | Herbert | Jun 1991 | A |
5034636 | Reis et al. | Jul 1991 | A |
5201039 | Sakamura | Apr 1993 | A |
5210850 | Kelly et al. | May 1993 | A |
5233690 | Sherlock | Aug 1993 | A |
5253308 | Johnson | Oct 1993 | A |
5276643 | Hoffman et al. | Jan 1994 | A |
5325500 | Bell et al. | Jun 1994 | A |
5325519 | Long et al. | Jun 1994 | A |
5367488 | An | Nov 1994 | A |
5379257 | Matsumura et al. | Jan 1995 | A |
5386379 | Ali-Yahia et al. | Jan 1995 | A |
5398213 | Yeon et al. | Mar 1995 | A |
5420870 | Kim | May 1995 | A |
5440482 | Davis | Aug 1995 | A |
5446690 | Tanaka et al. | Aug 1995 | A |
5473576 | Matsui | Dec 1995 | A |
5481500 | Reohr et al. | Jan 1996 | A |
5485373 | Davis et al. | Jan 1996 | A |
5506811 | McLaury | Apr 1996 | A |
5606347 | Simpson | Feb 1997 | A |
5615404 | Knoll et al. | Mar 1997 | A |
5638128 | Hoogenboom | Jun 1997 | A |
5638317 | Tran | Jun 1997 | A |
5654936 | Cho | Aug 1997 | A |
5678021 | Pawate et al. | Oct 1997 | A |
5724291 | Matano | Mar 1998 | A |
5724366 | Furutani | Mar 1998 | A |
5751987 | Mahant-Shetti et al. | May 1998 | A |
5787458 | Miwa | Jul 1998 | A |
5854636 | Watanabe et al. | Dec 1998 | A |
5867429 | Chen et al. | Feb 1999 | A |
5870504 | Nemoto et al. | Feb 1999 | A |
5915084 | Wendell | Jun 1999 | A |
5935263 | Keeth et al. | Aug 1999 | A |
5986942 | Sugibayashi | Nov 1999 | A |
5991209 | Chow | Nov 1999 | A |
5991785 | Alidina et al. | Nov 1999 | A |
6005799 | Rao | Dec 1999 | A |
6009020 | Nagata | Dec 1999 | A |
6092186 | Betker et al. | Jul 2000 | A |
6122211 | Morgan et al. | Sep 2000 | A |
6125071 | Kohno et al. | Sep 2000 | A |
6134164 | Lattimore et al. | Oct 2000 | A |
6147514 | Shiratake | Nov 2000 | A |
6151244 | Fujino et al. | Nov 2000 | A |
6157578 | Brady | Dec 2000 | A |
6163862 | Adams et al. | Dec 2000 | A |
6166942 | Vo et al. | Dec 2000 | A |
6172918 | Hidaka | Jan 2001 | B1 |
6175514 | Henderson | Jan 2001 | B1 |
6181698 | Hariguchi | Jan 2001 | B1 |
6208544 | Beadle et al. | Mar 2001 | B1 |
6226215 | Yoon | May 2001 | B1 |
6243309 | Shin | Jun 2001 | B1 |
6269040 | Reohr et al. | Jul 2001 | B1 |
6301153 | Takeuchi et al. | Oct 2001 | B1 |
6301164 | Manning et al. | Oct 2001 | B1 |
6304477 | Naji | Oct 2001 | B1 |
6389507 | Sherman | May 2002 | B1 |
6418498 | Martwick | Jul 2002 | B1 |
6466499 | Blodgett | Oct 2002 | B1 |
6477174 | Dooley et al. | Nov 2002 | B1 |
6510098 | Taylor | Jan 2003 | B1 |
6563754 | Lien et al. | May 2003 | B1 |
6578058 | Nygaard | Jun 2003 | B1 |
6731542 | Le et al. | May 2004 | B1 |
6754746 | Leung et al. | Jun 2004 | B1 |
6768679 | Le et al. | Jul 2004 | B1 |
6807614 | Chung | Oct 2004 | B2 |
6816422 | Hamade et al. | Nov 2004 | B2 |
6819612 | Achter | Nov 2004 | B1 |
6894549 | Eliason | May 2005 | B2 |
6943579 | Hazanchuk et al. | Sep 2005 | B1 |
6948056 | Roth | Sep 2005 | B1 |
6950771 | Fan et al. | Sep 2005 | B1 |
6950898 | Merritt et al. | Sep 2005 | B2 |
6956770 | Khalid et al. | Oct 2005 | B2 |
6961272 | Schreck | Nov 2005 | B2 |
6965648 | Smith et al. | Nov 2005 | B1 |
6985394 | Kim | Jan 2006 | B2 |
6987693 | Cernea et al. | Jan 2006 | B2 |
7020017 | Chen et al. | Mar 2006 | B2 |
7028170 | Saulsbury | Apr 2006 | B2 |
7045834 | Tran et al. | May 2006 | B2 |
7054178 | Shiah et al. | May 2006 | B1 |
7061817 | Raad et al. | Jun 2006 | B2 |
7079407 | Dimitrelis | Jul 2006 | B1 |
7173857 | Kato et al. | Feb 2007 | B2 |
7187585 | Li et al. | Mar 2007 | B2 |
7196928 | Chen | Mar 2007 | B2 |
7260565 | Lee et al. | Aug 2007 | B2 |
7260672 | Garney | Aug 2007 | B2 |
7372715 | Han | May 2008 | B2 |
7400532 | Aritome | Jul 2008 | B2 |
7406494 | Magee | Jul 2008 | B2 |
7447720 | Beaumont | Nov 2008 | B2 |
7454451 | Beaumont | Nov 2008 | B2 |
7457181 | Lee et al. | Nov 2008 | B2 |
7535769 | Cernea | May 2009 | B2 |
7546438 | Chung | Jun 2009 | B2 |
7562198 | Noda et al. | Jul 2009 | B2 |
7574466 | Beaumont | Aug 2009 | B2 |
7602647 | Li et al. | Oct 2009 | B2 |
7663928 | Tsai et al. | Feb 2010 | B2 |
7685365 | Rajwar et al. | Mar 2010 | B2 |
7692466 | Ahmadi | Apr 2010 | B2 |
7752417 | Manczak et al. | Jul 2010 | B2 |
7791962 | Noda et al. | Sep 2010 | B2 |
7796453 | Riho et al. | Sep 2010 | B2 |
7805587 | Van Dyke et al. | Sep 2010 | B1 |
7808854 | Takase | Oct 2010 | B2 |
7827372 | Bink et al. | Nov 2010 | B2 |
7869273 | Lee et al. | Jan 2011 | B2 |
7898864 | Dong | Mar 2011 | B2 |
7924628 | Danon et al. | Apr 2011 | B2 |
7937535 | Ozer et al. | May 2011 | B2 |
7957206 | Bauser | Jun 2011 | B2 |
7979667 | Allen et al. | Jul 2011 | B2 |
7996749 | Ding et al. | Aug 2011 | B2 |
8042082 | Solomon | Oct 2011 | B2 |
8045391 | Mokhlesi | Oct 2011 | B2 |
8059438 | Chang et al. | Nov 2011 | B2 |
8095825 | Hirotsu et al. | Jan 2012 | B2 |
8117462 | Snapp et al. | Feb 2012 | B2 |
8164942 | Gebara et al. | Apr 2012 | B2 |
8208328 | Hong | Jun 2012 | B2 |
8213248 | Moon et al. | Jul 2012 | B2 |
8223568 | Seo | Jul 2012 | B2 |
8238173 | Akerib et al. | Aug 2012 | B2 |
8274841 | Shimano et al. | Sep 2012 | B2 |
8279683 | Klein | Oct 2012 | B2 |
8310884 | Iwai et al. | Nov 2012 | B2 |
8332367 | Bhattacherjee et al. | Dec 2012 | B2 |
8339824 | Cooke | Dec 2012 | B2 |
8339883 | Yu et al. | Dec 2012 | B2 |
8347154 | Bahali et al. | Jan 2013 | B2 |
8351292 | Matano | Jan 2013 | B2 |
8356144 | Hessel et al. | Jan 2013 | B2 |
8417921 | Gonion et al. | Apr 2013 | B2 |
8462532 | Argyres | Jun 2013 | B1 |
8484276 | Carlson et al. | Jul 2013 | B2 |
8495438 | Roine | Jul 2013 | B2 |
8503250 | Demone | Aug 2013 | B2 |
8526239 | Kim | Sep 2013 | B2 |
8533245 | Cheung | Sep 2013 | B1 |
8555037 | Gonion | Oct 2013 | B2 |
8599613 | Abiko et al. | Dec 2013 | B2 |
8605015 | Guttag et al. | Dec 2013 | B2 |
8625376 | Jung et al. | Jan 2014 | B2 |
8644101 | Jun et al. | Feb 2014 | B2 |
8650232 | Stortz et al. | Feb 2014 | B2 |
8769251 | Luc et al. | Jul 2014 | B2 |
8873272 | Lee | Oct 2014 | B2 |
8964496 | Manning | Feb 2015 | B2 |
8971124 | Manning | Mar 2015 | B1 |
9015390 | Klein | Apr 2015 | B2 |
9047193 | Lin et al. | Jun 2015 | B2 |
9165023 | Moskovich et al. | Oct 2015 | B2 |
20010007112 | Porterfield | Jul 2001 | A1 |
20010008492 | Higashiho | Jul 2001 | A1 |
20010010057 | Yamada | Jul 2001 | A1 |
20010028584 | Nakayama et al. | Oct 2001 | A1 |
20010043089 | Forbes et al. | Nov 2001 | A1 |
20010050870 | Koshikawa | Dec 2001 | A1 |
20020059355 | Peleg et al. | May 2002 | A1 |
20030167426 | Slobodnik | Sep 2003 | A1 |
20030222879 | Lin et al. | Dec 2003 | A1 |
20040073592 | Kim et al. | Apr 2004 | A1 |
20040073773 | Demjanenko | Apr 2004 | A1 |
20040085840 | Vali et al. | May 2004 | A1 |
20040095826 | Perner | May 2004 | A1 |
20040154002 | Ball et al. | Aug 2004 | A1 |
20040205289 | Srinivasan | Oct 2004 | A1 |
20040240251 | Nozawa et al. | Dec 2004 | A1 |
20050015557 | Wang et al. | Jan 2005 | A1 |
20050078514 | Scheuerlein et al. | Apr 2005 | A1 |
20050097417 | Agrawal et al. | May 2005 | A1 |
20050285862 | Noda et al. | Dec 2005 | A1 |
20060047937 | Selvaggi et al. | Mar 2006 | A1 |
20060069849 | Rudelic | Mar 2006 | A1 |
20060146623 | Mizuno et al. | Jul 2006 | A1 |
20060149804 | Luick et al. | Jul 2006 | A1 |
20060181917 | Kang et al. | Aug 2006 | A1 |
20060215432 | Wickeraad et al. | Sep 2006 | A1 |
20060225072 | Lari et al. | Oct 2006 | A1 |
20060291282 | Liu et al. | Dec 2006 | A1 |
20070002668 | Williams | Jan 2007 | A1 |
20070103986 | Chen | May 2007 | A1 |
20070171747 | Hunter et al. | Jul 2007 | A1 |
20070180006 | Gyoten et al. | Aug 2007 | A1 |
20070180184 | Sakashita et al. | Aug 2007 | A1 |
20070195602 | Fong et al. | Aug 2007 | A1 |
20070285131 | Sohn | Dec 2007 | A1 |
20070285979 | Turner | Dec 2007 | A1 |
20070291532 | Tsuji | Dec 2007 | A1 |
20080025073 | Arsovski | Jan 2008 | A1 |
20080037333 | Kim et al. | Feb 2008 | A1 |
20080052711 | Forin et al. | Feb 2008 | A1 |
20080101395 | Ballew | May 2008 | A1 |
20080137388 | Krishnan et al. | Jun 2008 | A1 |
20080165601 | Matick et al. | Jul 2008 | A1 |
20080178053 | Gorman et al. | Jul 2008 | A1 |
20080215937 | Dreibelbis et al. | Sep 2008 | A1 |
20090067218 | Graber | Mar 2009 | A1 |
20090154238 | Lee | Jun 2009 | A1 |
20090154273 | Borot et al. | Jun 2009 | A1 |
20090254697 | Akerib | Oct 2009 | A1 |
20100067296 | Li | Mar 2010 | A1 |
20100091582 | Vali et al. | Apr 2010 | A1 |
20100110748 | Best | May 2010 | A1 |
20100172190 | Lavi et al. | Jul 2010 | A1 |
20100210076 | Gruber et al. | Aug 2010 | A1 |
20100226183 | Kim | Sep 2010 | A1 |
20100308858 | Noda et al. | Dec 2010 | A1 |
20100332895 | Billing et al. | Dec 2010 | A1 |
20110051523 | Manabe et al. | Mar 2011 | A1 |
20110063919 | Chandrasekhar et al. | Mar 2011 | A1 |
20110093662 | Walker et al. | Apr 2011 | A1 |
20110103151 | Kim et al. | May 2011 | A1 |
20110119467 | Cadambi et al. | May 2011 | A1 |
20110122695 | Li et al. | May 2011 | A1 |
20110140741 | Zerbe et al. | Jun 2011 | A1 |
20110219260 | Nobunaga et al. | Sep 2011 | A1 |
20110267883 | Lee et al. | Nov 2011 | A1 |
20110317496 | Bunce et al. | Dec 2011 | A1 |
20120005397 | Lim et al. | Jan 2012 | A1 |
20120017039 | Margetts | Jan 2012 | A1 |
20120023281 | Kawasaki et al. | Jan 2012 | A1 |
20120120705 | Mitsubori et al. | May 2012 | A1 |
20120134216 | Singh | May 2012 | A1 |
20120134225 | Chow | May 2012 | A1 |
20120134226 | Chow | May 2012 | A1 |
20120140540 | Agam et al. | Jun 2012 | A1 |
20120182798 | Hosono et al. | Jul 2012 | A1 |
20120195146 | Jun et al. | Aug 2012 | A1 |
20120198310 | Tran et al. | Aug 2012 | A1 |
20120246380 | Akerib et al. | Sep 2012 | A1 |
20120265964 | Murata et al. | Oct 2012 | A1 |
20120281486 | Rao et al. | Nov 2012 | A1 |
20120303627 | Keeton et al. | Nov 2012 | A1 |
20130003467 | Klein | Jan 2013 | A1 |
20130061006 | Hein | Mar 2013 | A1 |
20130107623 | Kavalipurapu et al. | May 2013 | A1 |
20130117541 | Choquette et al. | May 2013 | A1 |
20130124783 | Yoon et al. | May 2013 | A1 |
20130132702 | Patel et al. | May 2013 | A1 |
20130138646 | Sirer et al. | May 2013 | A1 |
20130163362 | Kim | Jun 2013 | A1 |
20130173888 | Hansen et al. | Jul 2013 | A1 |
20130205114 | Badam et al. | Aug 2013 | A1 |
20130219112 | Okin et al. | Aug 2013 | A1 |
20130227361 | Bowers et al. | Aug 2013 | A1 |
20130283122 | Anholt et al. | Oct 2013 | A1 |
20130286705 | Grover et al. | Oct 2013 | A1 |
20130326154 | Haswell | Dec 2013 | A1 |
20130332707 | Gueron et al. | Dec 2013 | A1 |
20140185395 | Seo | Jul 2014 | A1 |
20140215185 | Danielsen | Jul 2014 | A1 |
20140250279 | Manning | Sep 2014 | A1 |
20140344934 | Jorgensen | Nov 2014 | A1 |
20150029798 | Manning | Jan 2015 | A1 |
20150042380 | Manning | Feb 2015 | A1 |
20150063052 | Manning | Mar 2015 | A1 |
20150078108 | Cowles et al. | Mar 2015 | A1 |
20150085589 | Lu et al. | Mar 2015 | A1 |
20150279466 | Manning | Mar 2015 | A1 |
20150120987 | Wheeler | Apr 2015 | A1 |
20150134713 | Wheeler | May 2015 | A1 |
20150270015 | Murphy et al. | Sep 2015 | A1 |
20150324290 | Leidel | Nov 2015 | A1 |
20150325272 | Murphy | Nov 2015 | A1 |
20150356009 | Wheeler et al. | Dec 2015 | A1 |
20150356022 | Leidel et al. | Dec 2015 | A1 |
20150357007 | Manning et al. | Dec 2015 | A1 |
20150357008 | Manning et al. | Dec 2015 | A1 |
20150357019 | Wheeler et al. | Dec 2015 | A1 |
20150357020 | Manning | Dec 2015 | A1 |
20150357021 | Hush | Dec 2015 | A1 |
20150357022 | Hush | Dec 2015 | A1 |
20150357023 | Hush | Dec 2015 | A1 |
20150357024 | Hush et al. | Dec 2015 | A1 |
20150357047 | Tiwari | Dec 2015 | A1 |
20160062672 | Wheeler | Mar 2016 | A1 |
20160062673 | Tiwari | Mar 2016 | A1 |
20160062692 | Finkbeiner et al. | Mar 2016 | A1 |
20160062733 | Tiwari | Mar 2016 | A1 |
20160063284 | Tiwari | Mar 2016 | A1 |
20160064045 | La Fratta | Mar 2016 | A1 |
20160064047 | Tiwari | Mar 2016 | A1 |
20160098208 | Willcock | Apr 2016 | A1 |
20160098209 | Leidel et al. | Apr 2016 | A1 |
20160110135 | Wheeler et al. | Apr 2016 | A1 |
20160125919 | Hush | May 2016 | A1 |
20160154596 | Willcock et al. | Jun 2016 | A1 |
20160155482 | La Fratta | Jun 2016 | A1 |
20160188250 | Wheeler | Jun 2016 | A1 |
20160196142 | Wheeler et al. | Jul 2016 | A1 |
20160196856 | Tiwari et al. | Jul 2016 | A1 |
20160225422 | Tiwari et al. | Aug 2016 | A1 |
20160266873 | Tiwari et al. | Sep 2016 | A1 |
20160266899 | Tiwari | Sep 2016 | A1 |
20160267951 | Tiwari | Sep 2016 | A1 |
20160292080 | Leidel et al. | Oct 2016 | A1 |
20160306584 | Zawodny et al. | Oct 2016 | A1 |
20160306614 | Leidel et al. | Oct 2016 | A1 |
20160365129 | Willcock | Dec 2016 | A1 |
20160371033 | La Fratta et al. | Dec 2016 | A1 |
20170052906 | Lea | Feb 2017 | A1 |
Number | Date | Country |
---|---|---|
102141905 | Aug 2011 | CN |
0214718 | Mar 1987 | EP |
2026209 | Feb 2009 | EP |
H0831168 | Feb 1996 | JP |
2009259193 | Mar 2015 | JP |
10-0211482 | Aug 1998 | KR |
10-2010-0134235 | Dec 2010 | KR |
10-2013-0049421 | May 2013 | KR |
2001065359 | Sep 2001 | WO |
2010079451 | Jul 2010 | WO |
2013062596 | May 2013 | WO |
2013081588 | Jun 2013 | WO |
2013095592 | Jun 2013 | WO |
2016144726 | Sep 2016 | WO |
Entry |
---|
Dybdahl, et al., “Destructive-Read in Embedded DRAM, Impact on Power Consumption,” Apr. 2006, (10 pgs.), vol. 2, Issue 2, Journal of Embedded Computing-Issues in embedded single-chip multicore architectures. |
Kogge, et al., “Processing in Memory: Chips to Petaflops,” May 23, 1997, (8 pgs.), retrieved from: http://www.cs.ucf.edu/courses/cda5106/summer02/papers/kogge97PIM.pdf. |
Draper, et al., “The Architecture of the DIVA Processing-in-Memory Chip,” Jun. 22-26, 2002, (12 pgs.), ICS '02, retrieved from: http://www.isi.edu/˜draper/papers/ics02.pdf. |
Adibi, et al., “Processing-in-Memory Technology for Knowledge Discovery Algorithms,” Jun. 25, 2006, (10 pgs.), Proceeding of the Second International Workshop on Data Management on New Hardware, retrieved from: http://www.cs.cmu.edu/˜damon2006/pdf/adibi06inmemory.pdf. |
U.S. Appl. No. 13/449,082, entitled, “Methods and Apparatus for Pattern Matching,” filed Apr. 17, 2012, (37 pgs.). |
U.S. Appl. No. 13/743,686, entitled, “Weighted Search and Compare in a Memory Device,” filed Jan. 17, 2013, (25 pgs.). |
U.S. Appl. No. 13/774,636, entitled, “Memory as a Programmable Logic Device,” filed Feb. 22, 2013, (30 pgs.). |
U.S. Appl. No. 13/774,553, entitled, “Neural Network in a Memory Device,” filed Feb. 22, 2013, (63 pgs.). |
U.S. Appl. No. 13/796,189, entitled, “Performing Complex Arithmetic Functions in a Memory Device,” filed Mar. 12, 2013, (23 pgs.). |
International Search Report and Written Opinion for PCT Application No. PCT/US2013/043702, dated Sep. 26, 2013, (11 pgs.). |
Pagiamtzis, et al., “Content-Addressable Memory (CAM) Circuits and Architectures: A Tutorial and Survey”, Mar. 2006, (16 pgs.), vol. 41, No. 3, IEEE Journal of Solid-State Circuits. |
Pagiamtzis, Kostas, “Content-Addressable Memory Introduction”, Jun. 25, 2007, (6 pgs.), retrieved from: http://www.pagiamlzis.com/cam/camintro. |
Debnath, Biplob, Bloomflash: Bloom Filter on Flash-Based Storage, 2011 31st Annual Conference on Distributed Computing Systems, Jun. 20-24, 2011, 10 pgs. |
Derby, et al., “A High-Performance Embedded DSP Core with Novel SIMD Features”, Apr. 6-10, 2003, (4 pgs), vol. 2, pp. 301-304, 2003 IEEE International Conference on Accoustics, Speech, and Signal Processing. |
“4.9.3 MINLOC and MAXLOC”, Jun. 12, 1995, (5pgs.), Message Passing Interface Forum 1.1, retrieved from http://www.mpi-forum.org/docs/mpi-1.1/mpi-11-html/node79.html. |
Stojmenovic, “Multiplicative Circulant Networks Topological Properties and Communication Algorithms”, (25 pgs.), Discrete Applied Mathematics 77 (1997) 281-305. |
Boyd et al., “On the General Applicability of Instruction-Set Randomization”, Jul.-Sep. 2010, (14 pgs.), vol. 7, Issue 3, IEEE Transactions on Dependable and Secure Computing. |
Elliot, et al., “Computational RAM: Implementing Processors in Memory”, Jan.-Mar. 1999, (10 pgs.), vol. 16, Issue 1, IEEE Design and Test of Computers Magazine. |
International Search Report and Written Opinion for related PCT Application No. PCT/US2018/021683, dated Jun. 18, 2018, 12 pages. |
Office Action for related Taiwan Patent Application No. 107109409, dated Mar. 6, 2019, 15 pages. |
Extended European Search Report for related EP Patent Application No. 18772619.5, dated Dec. 15, 2020, 9 pages. |
Notice of Preliminary Rejection for related Korea Patent Application No. 10-2019-7030425, dated Jun. 29, 2021, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20210073159 A1 | Mar 2021 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15465340 | Mar 2017 | US |
Child | 17099101 | US |