Agilex™ 7 F-Series and I-Series FPGA Memory Subsystem IP User Guide

Download PDF
ID 789389
Date 7/15/2024
Public
Document Table of Contents
Document Table of Contents x
1. About the Agilex™ 7 F-Series and I-Series FPGA Memory Subsystem IP 2. Introduction to Memory Subsystem IP 3. Memory Subsystem IP Architecture and Feature Description 4. Memory Subsystem Features 5. Memory Subsystem Interfaces and Signals 6. Memory Subsystem User Operations 7. Memory Subsystem Register Descriptions 8. Parameterizing the Memory Subsystem IP 9. Simulating a Design Example 10. Document Revision History for Agilex™ 7 F-Series and I-Series FPGA Memory Subsystem IP User Guide
1. About the Agilex™ 7 F-Series and I-Series FPGA Memory Subsystem IP x
1.1. Release Information
2. Introduction to Memory Subsystem IP x
2.1. Memory Subsystem Features 2.2. Getting Started with the Memory Subsystem IP 2.3. Memory Subsystem Resource Utilization
3. Memory Subsystem IP Architecture and Feature Description x
3.1. Memory-Specific Adaptor 3.2. Memory Subsystem Lookup Core IPs
3.1. Memory-Specific Adaptor x
3.1.1. Memory Subsystem Functional Description
3.1.1. Memory Subsystem Functional Description x
3.1.1.1. Write Data Replication 3.1.1.2. Bank Spreading 3.1.1.3. Memory Subsystem IP Scheduler 3.1.1.4. Memory Subsystem Auto-Precharge
3.2. Memory Subsystem Lookup Core IPs x
3.2.1. Memory Subsystem BCAM 3.2.2. Memory Subsystem TCAM 3.2.3. Memory Subsystem Multi-Bin Lookup (MBL)
3.2.1. Memory Subsystem BCAM x
3.2.1.1. Memory Subsystem BCAM Operations
3.2.2. Memory Subsystem TCAM x
3.2.2.1. Memory Subsystem TCAM Core Table 3.2.2.2. Memory Subsystem TCAM Operations
3.2.3. Memory Subsystem Multi-Bin Lookup (MBL) x
3.2.3.1. Memory Subsystem Multi-Bin Lookup (MBL) Functional Description 3.2.3.2. Pointers 3.2.3.3. Memory Subsystem MBL Operations Flush Key Insertion Key Lookup Modify Result Using Key Key Deletion Get Handle Lookup Using Handle Modify Result Using Handle Key Deletion Using Handle Insert Key if Not Present, Modify Result if Present 3.2.3.4. Row Collisions 3.2.3.5. Signature Collisions 3.2.3.6. Optimization Features
4. Memory Subsystem Features x
4.1. Memory-Specific Adaptor 4.2. External Memory Interface 4.3. Lookup IPs
4.2. External Memory Interface x
4.2.1. External Memory Interfaces IP Parameters Tab
4.3. Lookup IPs x
4.3.1. TCAM 4.3.2. BCAM 4.3.3. MBL
5. Memory Subsystem Interfaces and Signals x
5.1. AXI Memory Mapped (AXI-MM) Interface 5.2. AXI-Lite Interface 5.3. Lookup IPs 5.4. Request/Acknowledge and Reset Signals 5.5. Clock Signals
5.3. Lookup IPs x
5.3.1. TCAM AXI-ST Request Interface 5.3.2. TCAM AXI-ST Response Interface 5.3.3. TCAM AXI-Lite Interface 5.3.4. BCAM AXI-ST Request Interface 5.3.5. BCAM AXI-ST Response Interface 5.3.6. BCAM AXI-Lite Interface 5.3.7. MBL AXI-ST Request Interface 5.3.8. MBL AXI-ST Response Interface 5.3.9. MBL AXI-Lite Interface
6. Memory Subsystem User Operations x
6.1. Memory Specific Adaptor 6.2. Performing TCAM Operations 6.3. Performing BCAM Operations 6.4. Performing MBL Operations
6.2. Performing TCAM Operations x
6.2.1. TCAM Flush Operations 6.2.2. TCAM Insert Operations 6.2.3. TCAM Delete by Entry ID Operations 6.2.4. TCAM Delete by Key Operations 6.2.5. TCAM Lookup Operations through the AXI-Lite Interface 6.2.6. TCAM Lookup Operations through the AXI-ST Interface
6.3. Performing BCAM Operations x
6.3.1. BCAM Flush Operations 6.3.2. BCAM Insert Operations 6.3.3. BCAM Modify Operations 6.3.4. BCAM Delete Operations 6.3.5. BCAM Lookup Operations through the AXI-Lite Interface 6.3.6. BCAM Lookup Operations through the AXI ST Interface
6.4. Performing MBL Operations x
6.4.1. MBL Flush Operation 6.4.2. MBL Insert Key Operation 6.4.3. MBL Delete Key Operation 6.4.4. MBL Lookup Operation Using Key 6.4.5. MBL Modify Operation 6.4.6. MBL Modify Result Using Handle Operation 6.4.7. MBL Delete Key Using Handle Operation 6.4.8. MBL Lookup Using Handle Operation 6.4.9. MBL Insert Key if Not Present or Modify Result if Present Operation 6.4.10. MBL Get Handle Operation
7. Memory Subsystem Register Descriptions x
7.1. Device Feature List 7.2. Memory Base Sub-System Global CSR 7.3. BCAM Registers 7.4. TCAM Registers 7.5. MBL Registers
7.1. Device Feature List x
7.1.1. Device Feature Header
7.2. Memory Base Sub-System Global CSR x
7.2.1. Offset 0x0000 Version 7.2.2. Offset 0x0004 Feature List 7.2.3. Offset 0x0010 Memory Interfaces 0-7 7.2.4. Offset 0x0014 Memory Interfaces 8-15 7.2.5. Offset 0x0018 Memory Interfaces 16-23 7.2.6. Offset 0x001C Memory Interfaces 24-31 7.2.7. Offset 0x0020 Scratch Pad 7.2.8. Offset 0x0030 Control Policy (Lower DWORD) 7.2.9. Offset 0x0034 Control Policy (Upper DWORD) 7.2.10. Offset 0x0038 Read Access Control Policy (Lower DWORD) 7.2.11. Offset 0x003C Read Access Control Policy (Upper DWORD) 7.2.12. Offset 0x0040 Write Access Control Policy (Lower DWORD) 7.2.13. Offset 0x0044 Write Access Control Policy (Upper DWORD) 7.2.14. Offset 0x0050 Memory Status Bitmask 0 7.2.15. Offset 0x0054 Memory Status Bitmask 1 7.2.16. Offset 0x0058 Memory Ready Status 0 7.2.17. Offset 0x005C Memory Ready Status 1 7.2.18. Offset 0x0060 Memory Error Status 0 7.2.19. Offset 0x0064 Memory Error Status 1
7.3. BCAM Registers x
7.3.1. Device Feature Header (DFH)-Specific Registers 7.3.2. General BCAM Registers
7.3.1. Device Feature Header (DFH)-Specific Registers x
7.3.1.1. Field Names and Values
7.3.2. General BCAM Registers x
7.3.2.1. Version 7.3.2.2. Feature List 7.3.2.3. Interface Attribute Parameters 7.3.2.4. Interface Attribute Parameters 1 7.3.2.5. Scratch Pad 7.3.2.6. General Control (GEN_CTRL) 7.3.2.7. Management Control (MGMT_CTRL) 7.3.2.8. Hash function_0 seed 7.3.2.9. Hash function_1 seed 7.3.2.10. Hash function_2 seed 7.3.2.11. Warning 0 (WARNING_0) 7.3.2.12. Fatal Error (FATAL_ERROR_0) 7.3.2.13. Monitor 0 (MON_) 7.3.2.14. Total Entries (TOTAL_ENTRIES) 7.3.2.15. Max. Rehouse Iterations (Max_Rehouse_Iterations) 7.3.2.16. Statistics Control (STATS_CTRL) 7.3.2.17. Active Table Entries (TABLE_ENTRIES) 7.3.2.18. Key_N 7.3.2.19. Result_N
7.4. TCAM Registers x
7.4.1. Device Feature Header (DFH)-Specific Registers 7.4.2. General TCAM Registers
7.4.1. Device Feature Header (DFH)-Specific Registers x
7.4.1.1. Field Names and Values
7.4.2. General TCAM Registers x
7.4.2.1. Version 7.4.2.2. Feature List 7.4.2.3. Interface Attribute Parameters 7.4.2.4. Scratch 7.4.2.5. Gen_Ctrl 7.4.2.6. Mgmt_Ctrl 7.4.2.7. Entry 7.4.2.8. Warning_0 7.4.2.9. Fatal_Error_0 7.4.2.10. Mon_0 7.4.2.11. Key_N 7.4.2.12. Result_N 7.4.2.13. Match_N 7.4.2.14. Mask_N
7.5. MBL Registers x
7.5.1. MBL DFH 7.5.2. General MBL Registers 7.5.3. Version 7.5.4. Mbl_scratch 7.5.5. Mbl_gen_ctrl 7.5.6. Mbl_mgmt_ctrl 7.5.7. Mbl_key_handle 7.5.8. Mbl_nxt_handle_req 7.5.9. Mbl_nxt_handle 7.5.10. Mbl_warning_0 7.5.11. Mbl_fatal_0 7.5.12. Mbl_mon_0 7.5.13. Mbl_total_entries 7.5.14. Mbl_total_rehashes 7.5.15. Mbl_max_used_bins 7.5.16. Mbl_stats_ctrl 7.5.17. Mbl_stats_result 7.5.18. Mbl_max_lkup_latency 7.5.19. Mbl_max_rehash_index 7.5.20. Mbl_key 7.5.21. Mbl_res
8. Parameterizing the Memory Subsystem IP x
8.1. Launching the Memory Subsystem IP 8.2. Parameterization Flow
8.2. Parameterization Flow x
8.2.1. Defining the Number of Memory Interfaces, Type, and Location 8.2.2. Selecting the Required Application Interfaces 8.2.3. Mapping Application to Memory Interfaces (Data Flow) 8.2.4. Generating IPs within the Memory Subsystem 8.2.5. Parameterizing Required EMIF, CAM, and MSA IPs
8.2.5. Parameterizing Required EMIF, CAM, and MSA IPs x
8.2.5.1. Parameterizing the External Memory Interface (EMIF) IP 8.2.5.2. Parameterizing the Memory-Specific Adapter 8.2.5.3. Parameterizing the Content-Addressable Memory (CAM) IP 8.2.5.4. Parameterizing the External Memory Interfaces Calibration IP 8.2.5.5. Saving the IPs Within the Memory Subsystem 8.2.5.6. Propagation of Changes Across IPs within the Memory Subsystem IP
9. Simulating a Design Example x
9.1. Generating a Design Example 9.2. Generated Directory Structure for the Design Example 9.3. Steps for Simulation 9.4. Generating Traffic with the Test Engine IP
1. About the Agilex™ 7 F-Series and I-Series FPGA Memory Subsystem IP
2. Introduction to Memory Subsystem IP
3. Memory Subsystem IP Architecture and Feature Description
4. Memory Subsystem Features
5. Memory Subsystem Interfaces and Signals
6. Memory Subsystem User Operations
7. Memory Subsystem Register Descriptions
8. Parameterizing the Memory Subsystem IP
9. Simulating a Design Example
10. Document Revision History for Agilex™ 7 F-Series and I-Series FPGA Memory Subsystem IP User Guide

3.2.3.3. Memory Subsystem MBL Operations

The multi-bin lookup (MBL) can perform ten different operations:
  1. Flush
  2. Key insertion
  3. Key lookup
  4. Modify result
  5. Key deletion
  6. Get handle
  7. Lookup using handle
  8. Modify result using handle
  9. Delete key using handle
  10. Insert key if not present, modify result if present

The following sections provide high-level descriptions of each MBL operation. Refer to the Performing MBL Operations section for detailed instructions on issuing MBL commands through the AXI Lite interface, and for waveform examples.

Flush

You must always issue a flush operation at the beginning of the traffic. The flush operation writes zeros to all locations of the hash table and reinitializes the free pointers list.

Key Insertion

The system performs the following sequence when a management system requests a key to be inserted:

  1. Key lookup is performed, as described below. The Lookup Core returns a match/no match result, and information needed in the insertion process (all bins from the row and HASH2 vector).
  2. All signatures in the selected row are compared with the signature of the candidate key:
    1. If there is no matching signature, then the signature is inserted to the first available bin in the row. If there are no free bins in the row, then the key cannot be inserted.
    2. If there is a matching signature already in the row, the signature rehashing is performed:
      1. All keys corresponding to this row are read from the key table.
      2. All signatures are re-calculated using the HASH2 polynomial that you can set as a parameter. All signatures are compared with each other to check if there are collisions. The first polynomial with no collisions is selected as the polynomial for this row.
  3. If the new key can be inserted, a free pointer to the key memory is obtained from a free pointers list.
    Note: When you have enabled SEMI_AUTO pointer management mode, the pointer must be provided by the software, based on MBL_GET_HANDLE command run prior to the insert.
  4. The key is written to the key memory, at the location indicated by the pointer.
  5. The hash table is written with the updated row.

Key Lookup

Key lookup can be requested from the control path. The sequence of operations is as follows:

  1. The key is hashed in HASH1 to produce a row number.
    Note: It is possible that different keys after going through HASH1 produce the same row number, this is referred to as row collision.
  2. The system uses the row number to read the corresponding row from the hash table.
  3. The key is hashed in HASH2 to generate a signatures.
  4. The system compares the signature with a signature in each active bin in the row.
  5. If the system detects a signature match, the pointer from the matching bin is used to read a key and result from the key memory.
  6. The system compares the key read from the memory to the key being looked up; if a match is detected, the result is sent to output as a valid lookup result.

Modify Result Using Key

  1. Key lookup sequence 1-5 is performed.
  2. The system compares the key read from the memory to the key being looked up; if a match is detected, the result is modified.

Key Deletion

When a management system requests a key to be deleted, the following sequence is performed in hardware:

  1. Key lookup sequence 1-6 is performed.
  2. If the key is found, then the corresponding bin is marked as free.
  3. If the bin is located in the middle of other used bins then the bin at the highest index is moved to fill the gap left after the bin corresponding to the deleted entry.
  4. The pointer from the deleted entry is returned to the free pointers list, if the hardware-based pointer management is enabled.

Get Handle

When the Semi-automatic pointer management option is enabled, you can request a number of free handles. Refer to Optimization Features and MBL Get Handle Operation for more information.

Lookup Using Handle

  1. The handle is used to access the indicated address.
  2. Key and result are read from the key table.
  3. The key and result is sent to output as a valid lookup result.

Modify Result Using Handle

  1. The handle is used to access the indicated address.
  2. The result is modified.

Key Deletion Using Handle

  1. The handle is used to read a key and result from the key table.
  2. If the key is found in hash table, then the corresponding bin is marked as free.
  3. If the bin is located in the middle of other used bins then the bin at the highest index is moved to fill the gap left after the bin corresponding to the deleted entry.
  4. The pointer from the deleted entry is returned to the free pointers list.

Insert Key if Not Present, Modify Result if Present

  1. Key lookup sequence 1-6 is performed.
  2. If a match is detected, modify operation is executed.
  3. If no match is detected, key insertion operation is performed.
Level Two Title