Near-Memory Telemetry Logging With Time-Synchronized Event Alignment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory systems lack the ability to efficiently monitor and log memory-side internal metadata and telemetry data without crossing the interface between host devices and memory modules, limiting the insight into memory performance and behavior.
Innovation Solution
Implementing near-memory time-synchronized telemetry logging within memory devices, which includes a filter/logger and internal RAM to record telemetry data without crossing the interface, using triggering commands and unique identifiers to align data with code execution, enabling precise logging and offline/online analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If telemetry data is logged by crossing the interface between host devices and memory modules, then data can be captured, but the logging process adds interface overhead and reduces measurement precision
Solution Approach 1:
The patent divides the logging function into two segments: a filter/logger component that captures and pre-processes telemetry data within the memory device, and a separate host system component that retrieves and analyzes the logged data. This segmentation allows precise local capture without requiring continuous host-device interface communication for every data point.
Solution Approach 2:
The filter/logger acts as an intermediary component embedded within the memory device that intercepts and logs telemetry data locally before it crosses the interface. This intermediary captures data at the source, eliminating the need for the host system to request every data point through the interface, thus reducing interface overhead while maintaining measurement precision.
2Loss of information
If detailed memory-side telemetry data is monitored, then insight into memory performance is improved, but device complexity increases
Solution Approach 1:
The filter/logger component is designed with multi-functionality, serving both as a telemetry data capturer and a pre-processor that can filter and organize data before logging. This universal component handles multiple tasks (capture, filter, log, and even preliminary analysis) within the memory device, reducing the need for additional complex infrastructure on both the device and host sides.
Solution Approach 2:
The memory device performs self-service by including the filter/logger functionality directly within its architecture. The device autonomously captures, filters, and logs its own telemetry data without requiring external monitoring infrastructure, thereby gaining detailed performance insight while minimizing the addition of external complex systems.
3Ease of operation
If telemetry data is logged without time synchronization, then logging is simpler, but the ability to map events with code execution is reduced
Solution Approach 1:
The filter/logger incorporates a programmable timer that performs preliminary time-synchronization actions before data is logged. This timer pre-establishes accurate time stamps and synchronization markers in the logged data, ensuring that event timing information is captured with high precision before the data leaves the memory device, thus maintaining both simplicity and accuracy.
Solution Approach 2:
The patent replaces complex post-processing mechanical or software-based time-synchronization mechanisms with a hardware-based programmable timer integrated into the filter/logger. This substitution provides accurate time synchronization directly at the source through hardware timing circuits, eliminating the need for complex software-based synchronization protocols while maintaining event alignment accuracy.
Data Source
AI summary
A memory controller of a memory device can receive an insertion notification related to near-memory telemetry data, and can collect the near-memory telemetry data based on the insertion notification. The near-memory telemetry data can be included in a log stored in a memory array of the memory device, and the logged near-memory telemetry data can be sent to a host device, in some examples.