CAID
  • NEW!
    NEW!  Connect Ideas Across Notes
    Save time and share insights. With Paragraph Citation, you can quote others’ work with source info built in. If someone cites your note, you’ll see a card showing where it’s used—bringing notes closer together.
    Got it
        • Sharing URL Link copied
        • /edit
        • View mode
          • Edit mode
          • View mode
          • Book mode
          • Slide mode
          Edit mode View mode Book mode Slide mode
        • Customize slides
        • Note Permission
        • Read
          • Owners
          • Signed-in users
          • Everyone
          Owners Signed-in users Everyone
        • Write
          • Owners
          • Signed-in users
          • Everyone
          Owners Signed-in users Everyone
        • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invite by email
        Invitee

        This note has no invitees

      • Publish Note

        Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

        Your note will be visible on your profile and discoverable by anyone.
        Your note is now live.
        This note is visible on your profile and discoverable online.
        Everyone on the web can find and read all notes of this public team.

        Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

        Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

        Explore these features while you wait
        Complete general settings
        Bookmark and like published notes
        Write a few more notes
        Complete general settings
        Write a few more notes
        See published notes
        Unpublish note
        Please check the box to agree to the Community Guidelines.
        View profile
      • Commenting
        Permission
        Disabled Forbidden Owners Signed-in users Everyone
      • Enable
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Suggest edit
        Permission
        Disabled Forbidden Owners Signed-in users Everyone
      • Enable
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
      • Emoji Reply
      • Enable
      • Versions and GitHub Sync
      • Note settings
      • Note Insights New
      • Engagement control
      • Make a copy
      • Transfer ownership
      • Delete this note
      • Insert from template
      • Import from
        • Dropbox
        • Google Drive
        • Gist
        • Clipboard
      • Export to
        • Dropbox
        • Google Drive
        • Gist
      • Download
        • Markdown
        • HTML
        • Raw HTML
    Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
    Menu
    Options
    Engagement control Make a copy Transfer ownership Delete this note
    Import from
    Dropbox Google Drive Gist Clipboard
    Export to
    Dropbox Google Drive Gist
    Download
    Markdown HTML Raw HTML
    Back
    Sharing URL Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Customize slides
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    3
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # [Study] Memory System -- DRAM study note ###### tags: `research-GraphRC` ![](https://i.imgur.com/un1PQmo.png) > by Jacob, Bruce Wang, David T. Ng, Spencer W. Rodriguez, Samuel [TOC] ## DRAM limitation ### Speed - DRAM designers have increased the **data rate at the DRAM’s I/O pins** without having also to increase the speed of the DRAM’s core - DDR improves speed relative to single data rate (SDR) by moving to a **2n prefetch architecture**—one in which twice the number of bits are fetched from the DRAM core ### Cost concern - DRAM design will be far more concerned about pin count than transistor count - Pin cost is becoming a major concern ### Power and Heat Dissipation - Previous-era DIMMs exhibited power dissipation on the order of **1W**. Current **FB-DIMMs dissipate nearly ten times** that ## DRAM access latency :::spoiler Breaking down access delay ![](https://i.imgur.com/tQqyA3W.png) ::: ### Timing parameter - Capture from Chapter 11, page 428 | Parameter | Description | | --------- | ----------- | | tAL | Added Latency to column accesses, used in DDRx SDRAM devices for posted CAS commands. | | tBURST | Data burst duration. The time period that data burst occupies on the data bus. Typically 4 or 8 beats of data. In DDR SDRAM, 4 beats of data occupy 2 full clock cycles. | | tCAS | Column Access Strobe latency. The time interval between column access command and the start of data return by the DRAM device(s). Also known as tCL. | | tCCD | Column-to-Column Delay. The minimum column command timing, determined by internal burst (prefetch) length. Multiple internal bursts are used to form longer burst for column reads. tCCD is 2 beats (1 cycle) for DDR SDRAM, and 4 beats (2 cycles) for DDR2 SDRAM | | tCMD | Command transport duration. The time period that a command occupies on the command bus as it is transported from the DRAM controller to the DRAM devices. | | tCWD | Column Write Delay. The time interval between issuance of the column-write command and placement of data on the data bus by the DRAM controller. | | tFAW | Four (row) bank Activation Window. A rolling time-frame in which a maximum of four-bank activation can be engaged. Limits peak current profi le in DDR2 and DDR3 devices with more than 4 banks. | | tOST | ODT Switching Time. The time interval to switching ODT control from rank to rank. | | tRAS | Row Access Strobe. The time interval between row access command and data restoration in a DRAM array. A DRAM bank cannot be precharged until at least tRAS time after the previous bank activation. | | tRC | Row Cycle. The time interval between accesses to different rows in a bank. tRC = tRAS + tRP. | | tRCD | Row to Column command Delay. The time interval between row access and data ready at sense amplifiers. | | tRFC | Refresh Cycle time. The time interval between Refresh and Activation commands. | | tRP | Row Precharge. The time interval that it takes for a DRAM array to be precharged for another row access. | | tRRD | Row activation to Row activation Delay. The minimum time interval between two row activa- tion commands to the same DRAM device. Limits peak current profiile. | | tRTP | Read to Precharge. The time interval between a read and a precharge command. | | tRTRS | Rank-to-rank switching time. Used in DDR and DDR2 SDRAM memory systems; not used in SDRAM or Direct RDRAM memory systems. One full cycle in DDR SDRAM. | | tWR | Write Recovery time. The minimum time interval between the end of a write data burst and the start of a precharge command. Allows sense amplifi ers to restore data to cells. | | tWTR | Write To Read delay time. The minimum time interval between the end of a write data burst and the start of a column-read command. Allows I/O gating to overdrive sense amplifi ers before read command starts. | #### Row-Read Command - The purpose of a row access command is to move data from the cells in the DRAM arrays to the sense amplifiers and then restore the data back into the cells in the DRAM arrays as part of the same command. - **tRCD**: The time it takes for the row access command to move data from the DRAM cell arrays to the sense amplifiers is known as the Row-Column (Command) Delay. - **tRAS**: The time it takes for a row access command to discharge and restore data from the row of DRAM cells is known as the Row Access Strobe latency or tRAS. - ![](https://i.imgur.com/a396DHr.png) #### Column-Read Command - A column-read command moves data from the array of sense amplifiers of a given bank of DRAM arrays through the data bus back to the memory controller. - **tCAS**: Column Access Strobe Latency (tCAS, or tCL) is the time it takes for the DRAM device to place the requested data onto the data bus after issuance of the column-read command. - **tCCD, tBURST**: The internal burst length of the DRAM device is labelled as tCCD in Figure 11.4, and the duration of the data burst on the data bus for a single column-read command is labelled as tBURST. - ![](https://i.imgur.com/MYlviju.png) #### Column-Write Command - A column-write command moves data from the memory controller to the sense amplifiers of the targeted bank. - **tCWD**: The column-write delay specifies the timing between assertion of the column-write command on the command bus and the placement of the write data onto the data bus by the memory controller. - **tWR**: The write recovery time, tWR, is the time it takes for the write data to propagate into the DRAM arrays - **tWTR**: The write-to-read time, tWTR, accounts for the time that the I/O gating resources are released by the write command - ![](https://i.imgur.com/N4yiRIE.png) #### Precharge Command - The precharge command completes the row access sequence as it resets the sense amplifi ers and the bitlines and prepares them for another row access command to the same array of DRAM cells. - **tRP**: Time after the assertion of the precharge command, the bitlines and sense amplifiers of the selected bank are properly precharged, and a subsequent row access command can be sent to the just-precharged bank of DRAM cells. - **tRC**: = tRP + tRAS. The minimum amount of time that a DRAM device needs to bring data from the DRAM cell arrays into the sense amplifi ers, restore the data to the DRAM cells, and precharge the bitlines to the reference voltage level for another row access command. - tRC is also commonly referred to as the random row-cycle time of a DRAM device. - ![](https://i.imgur.com/F6H4v9j.png) #### Refresh Command - ![](https://i.imgur.com/74JBjwh.png) ## Timing ### Read cycle ### Write cycle ### ## Overall architecture - ![](https://i.imgur.com/hpKTR2D.png) - Memory Controller - Channel - Rank - Chip (Device) - Bank - Subarray (Array) - Mat (Tile) - Row, Column - Cell ## DRAM Channel :::info - A channel is the **collection of all banks** that share **a common physical link** (command, address, data buses) to the processor. - Each system controller has a single **DRAM memory controller (DMC)**, and each DRAM memory controller controls a single **channel** of memory. While banks from the same channel experience contention at the physical link, **banks from different channels** can be accessed **completely independently** of each other. ::: - ![](https://i.imgur.com/OXUiSsN.png) - In modern DRAM memory systems, commodity DRAM memory modules are standardized with **64-bit-wide data busses**, and the 64-bit data bus width of the memory module matches the data bus width of the typical personal computer system controller. - Commodity **error correcting** memory systems are standardized with a **72-bit-wide data bus**. - Modern memory systems with o**ne DRAM memory controller and multiple physical channels** of DRAM devices are typically designed with the **physical channels operating in lockstep** with respect to each other. - Figure explanation - Typical system controller: The system controller controls a **single 64-bit-wide channel**. - Intel i875P system controller: The system controller connects to a single channel of DRAM with a **128-bit-wide data bus**. The system controller requires matching pairs of 64-bit wide memory modules to operate with the 128-bit-wide data bus. The paired-memory module configuration of the i875P is often referred to as a **dual channel** configuration. - ![](https://i.imgur.com/70EDPLX.png) - The use of independent DRAM memory controllers can lead to higher sustainable bandwidth characteristics. As a result, newer system controllers are often designed with **multiple memory controllers** despite the additional die cost. ## DRAM Rank :::info - **Rank** is now used to denote a set of DRAM devices that operate in lockstep to respond to a given command in a memory system. - Banks in different ranks are fully decoupled with respect to their device-level electrical operation and, consequently, offer **better bank-level parallelism than banks in the same rank.** - A DRAM rank typically consists of **eight DRAM chips**, each of which has **eight banks**. Since the chips operate in lockstep, **the rank has only eight independent banks**, each of which is the set of the ith bank across all chips. ::: - ![](https://i.imgur.com/PqbZ0SB.png) ## DRAM Device (Chip) - ![](https://i.imgur.com/hHBo3Tl.png) - This DRAM cell consists of **1024 columns**, and **each column is 16 bits wide**. That is, the **16-bit-wide column is the basic addressable unit of memory in this device**, and each column access that follows the row access would read or write 16 bits of data from the same row of DRAM - ![](https://i.imgur.com/9yMAhNF.png) - In a given generation, a DRAM device may be configured with different data bus widths for use in different applications. The 64 Meg x4 device consists of **4 bits of data per column**, **2048 columns of data per row**, and **8192 rows per bank**, and there are **4 banks in the device**. Alternatively, a 256-Mbit SDRAM device with a 16-bit-wide data bus will have 16 bits of data per column, 512 columns per row, and 8192 rows per bank; there are 4 banks in the 16 Mbit, x16 device. :::info Recap: What is the red 8 in the upper left corner ? The number of subarry ? or the number of - Figure from last week ![](https://i.imgur.com/lWF4hF3.jpg) - Updated figure ![](https://i.imgur.com/5bpbQb3.jpg) - **Conclusion:** - Given SALP, we have **subarry ID** field in memory address. We can select a specific **slice** from bank **volume** - Without SALP, we DON'T have **subarry ID** field in memory address. We automatically retrieve a **cube** of bits from bank **volume** (i.e. 8 bits for x8 DRAM, 4 bits for x4 DRAM) ::: ## DRAM Bank :::info - **Bank** is only used to denote a set of independent memory arrays inside a DRAM device. - **Banks** are the smallest memory structures that can be accessed in parallel with respect to each other. This is referred to as **bank-level parallelism**. - This is NOT true for RC-NVM bank ::: - DRAM device with **4 banks** of DRAM arrays internally. - ![](https://i.imgur.com/XWRepUY.png) - Modern DRAM devices contain **multiple banks** so that multiple, independent accesses to different DRAM arrays can **occur in parallel**. In this design, each **bank of memory is an independent** array that can be in different phases of a row access cycle. - Multiple banks within a given DRAM device can be **activated independently from each other** -- subject to the **power constraints** of the DRAM device that may specify how closely such activations can occur in a given period of time. ## DRAM Subarray (Array) ![](https://i.imgur.com/CIm3JbM.png) - A **x4 DRAM** (pronounced “by four”) indicates that the DRAM has at least four memory arrays and that a **column width is 4 bits** (each column read or write transmits 4 bits of data). In a x4 DRAM part, four arrays each read 1 data bit in unison, and the part **sends out 4 bits** of data each time the memory controller makes a **column read request**. - ![](https://i.imgur.com/N5iURcm.png) - Due to their large parasitic capacitance, long bitlines have two disadvantages. - First, they make it difficult for a DRAM cell to cause the necessary perturbation required for reliable sensing. - Second, a sense-amplifier takes longer to drive a long bitline to a target voltage-level, thereby increasing the latency of activation and precharging. - ![](https://i.imgur.com/g83kIJX.png) - All tiles in the horizontal direction – a **“row of tiles” – share the same set of global wordlines**. Therefore, these tiles are activated and precharged in lockstep. We abstract such a “row of tiles” as a single entity that we refer to as a **subarray**. More specifically, a subarray is a collection of cells that **share a local row-buffer** (all sense-amplifiers in the horizontal direction) and a **subarray row-decoder**. ## DRAM Row :::info - **Row** is simply a group of storage cells that are **activated in parallel** in response to a row activation command. ::: - DRAM **devices** can be connected in parallel to form **a rank of memory**. The effect of DRAM devices connected as ranks of DRAM devices that **operate in lockstep** is that a row activation command will activate the **same addressed row in ALL DRAM devices** in a given rank of memory. - From the perspective of the memory controller, the **size of a row** is simply the **size of a row in a given DRAM device** multiplied by the number of DRAM devices in a given rank. ![](https://i.imgur.com/ppUHmkE.png) ## DRAM Column :::info - **Column** of data is the smallest addressable unit of memory. ::: - ![](https://i.imgur.com/H9ZWnti.png) - **The size of a column of data is the same as the width of the data bus.** :::info - A **beat** is simply a data transition on the data bus. ::: - In SDRAM memory systems, there is **one data transition per clock cycle**, so **one beat of data is transferred per clock cycle**. - In DDRx SDRAM memory systems, **two data transfers can occur in each clock cycle**, so **two beats of data are transferred in a single clock cycle**. - In DDRx SDRAM memory systems, **each column access command fetches multiple columns of data depending on the programmed burst length**. - For example, in a DDR2 DRAM device, each memory read command returns a minimum of 4 columns of data. ## DRAM Cell design - Currently, DRAM device manufacturers such as Micron, Samsung, Elpida, Hynix, and the majority of the DRAM manufacturing industry use the stacked capacitor structure, while Qimonda, Nanya, and several other smaller DRAM manufacturers use the trench capacitor structure ### Trench capacitor design - ![](https://i.imgur.com/7BM1MJ0.png) ### Stacked capacitor design - ![](https://i.imgur.com/9whfKNU.png) - ![](https://i.imgur.com/bJcz6fR.png)

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully