Near memory protocol analyzer
By embedding a protocol analyzer in the memory controller to record packet tracking data between the host device and the memory, the problem of difficulty in monitoring and analyzing memory performance in the prior art is solved, and high-speed and accurate memory performance monitoring and analysis is achieved.
Patent Information
- Application Number
- CN202410304253.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-30
- Filing Date
- 2024-03-18
- Publication Date
- 2024-12-03
AI Technical Summary
Existing memory devices are difficult to efficiently monitor and record business activities between the host device and the memory, affecting the analysis of software program behavior and memory performance, and embedding of existing protocol analyzers in the host device will interfere with or slow down communication.
Embed a protocol analyzer in the memory controller to capture and record the packet tracking data between the host device and the memory array, and store it in the log area, and return it to the host device through the memory bus, achieving high-speed recording without affecting communication.
Provides detailed feedback on software program behavior and memory performance, reduces the need for expensive hardware and software tools, and improves the efficiency and accuracy of memory performance analysis.
Smart Images

Figure CN119065588A_ABST
Abstract
Description
[0001] Statement on government support
[0002] This invention was made with U.S. Government support under Contract No. 548143 awarded by PNNL. The U.S. Government has certain rights in this invention. Technical Field
[0003] Embodiments of the present disclosure relate generally to managed memory devices, and more particularly, to a memory device having an embedded protocol analyzer. Background Art
[0004] A memory device is a semiconductor circuit that provides electronic storage of data for a host system, such as a computer or other electronic device. A memory device may be volatile or nonvolatile. Volatile memory requires power to maintain data, and includes devices such as random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), or synchronous dynamic random access memory (SDRAM). Nonvolatile memory can retain stored data when not powered, and includes devices such as flash memory, read-only memory (ROM), electrically erasable programmable ROM (EEPROM), erasable programmable ROM (EPROM), resistance variable memory (such as phase change random access memory (PCRAM)), resistive random access memory (RRAM), and magnetoresistive random access memory (MRAM).
[0005] The host device typically includes a host processor, a first amount of main memory (e.g., typically volatile memory, such as DRAM) for supporting the host processor, and one or more memory devices (e.g., typically non-volatile memory, such as flash memory) that provide additional storage for retaining data in addition to or independently of the main memory.
[0006] The memory device may include a memory controller and one or more memory integrated circuit (IC) dies. The die may be configured as one or more memory arrays. The memory controller may include an interface circuit system configured to communicate with a host device (e.g., a host processor or interface circuit system) through a communication interface (e.g., a bidirectional parallel or serial interconnect bus). The memory controller may receive commands or operations associated with memory operations or instructions from the host, such as read or write operations to transfer data (e.g., user data and associated integrity data, such as error data or address data, etc.) between the memory device and the host device, erase operations to erase data from the memory device, perform drive management operations (e.g., data migration, obsolete item collection, block retirement), etc. Summary of the invention
[0007] In one aspect, the present disclosure provides a memory device comprising: one or more integrated circuit (IC) memory dies configured as a memory array; and a memory controller for controlling access to the memory array, the memory controller being configured to: receive memory requests from a host device; collect packet tracking data from the memory requests; include the packet tracking data in a log stored in a log area of the memory array; and return the log to the host device.
[0008] In another aspect, the present disclosure provides a method of operating a memory device, the method comprising: receiving, by a memory controller of the memory device, a memory request from a host device; collecting packet tracking data from the memory request, including the packet tracking data in a log stored in a memory array of the memory device; and returning the log to the host device.
[0009] In another aspect, the present disclosure provides a computer system comprising: at least one host device including a host processor; a memory bus and a host input / output (I / O) channel; and at least one memory device coupled to the at least one host device through the memory bus and the host I / O channel, wherein the memory device comprises: one or more integrated circuit (IC) memory dies configured as a memory array; and a memory controller for controlling access to the memory array, the memory controller being configured to: retain a log in the memory array according to log configuration information received from the at least one host device via the host I / O channel; receive a memory request from the at least one host device via the memory bus; store packet tracking data from the memory request in the log; and return the packet tracking data stored in the log to the host device. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] In the drawings, which are not necessarily drawn to scale, the same reference numerals may describe similar components in different views. The same reference numerals with different letter suffixes may represent different instances of similar components. The drawings generally illustrate the various embodiments discussed in this document by way of example and not by way of limitation.
[0011] Figure 1 is a block diagram of a computer system according to some examples described herein.
[0012] Figure 2 is a block diagram of a memory device according to some examples described herein.
[0013] Figure 3 is a flow chart of a method of operating a memory device according to some examples described herein.
[0014] Figure 4 is a block diagram of a memory controller of a memory device according to some examples described herein.
[0015] Figure 5 A block diagram illustrating an example machine according to some examples described herein. DETAILED DESCRIPTION
[0016] Software (e.g., programs), instructions, operating systems (OS), and other data are typically stored on storage systems and accessed by main memory for use by host processors. Main memory (e.g., RAM) is typically a memory device (e.g., volatile memory device) that is faster, more expensive, and of a different type than most memory devices (e.g., non-volatile memory devices, such as SSDs, etc.) of the storage system. In addition to main memory, the host device may also include different levels of volatile memory that is typically faster than the main memory, such as a group of static memory (e.g., cache, typically SRAM), which in a specific instance is configured to operate at a speed close to or exceeding the speed of the host processor but with lower density and higher cost. In other instances, different levels or amounts of main memory or static memory may be used depending on the desired host device performance and cost.
[0017] Programmers may wish to monitor and record the business on the interconnect bus between the host device and the main memory. Such monitoring provides programmers with information about the behavior of their programs and the memory performance when executing the programs.
[0018] Figure 1 1 is a block diagram of an example computer system 100 including two host devices 104 (e.g., host server processors) connected to two memory devices 114. To simplify the diagram, the example shows two host devices and two memory devices, but actual implementations may include many host devices 104 and memory devices 114. The host devices 104 are connected to the memory devices 114 via a memory switch 135 (e.g., Gen-Z, Peripheral Component Interconnect Express (PCIe), Compute Express Link (CXL), etc.). The memory devices 114 may include one or more memory integrated circuit (IC) dies or memory dies 130 and a memory controller 118. Data stored in the memory devices 114 may be accessed using a switching protocol to bring the data through the memory switch. In some examples, the memory devices 114 are directly connected to the host devices 104. In certain examples, the processing device is an in-memory processor.
[0019] Figure 2 Is suitable for use as Figure 1130-N). The memory device 114 includes a switch interface 123 to a memory switch 135. A host device communicates with the memory device via the memory switch 135 and the switch interface 123.
[0020] The memory controller 118 may receive instructions from the host device 104 and may communicate with the memory array to, for example, transfer data to (e.g., write) or transfer data from (e.g., read) or erase one or more of the memory cells, planes, sub-blocks, blocks, or pages of the memory array. For example, the memory controller 118 includes a processing circuit system 110, which may include one or more processors 115, which, when present, operate to execute instructions stored in the memory device 114 (e.g., stored in the memory 120). For the purposes of this example, the instructions will be discussed as firmware, but the instructions may also exist as software; and all or some portion of the described functionality may also be implemented in a circuit system including one or more components or integrated circuits. The processing circuit system 110 is configured to control access across the memory array and provide a translation layer between the host device 104 and the memory array. In addition, the memory controller 118 may include a memory die interface 125 to interface with the memory die on the memory bus 127. In some examples, the memory die interface 125 can be an Open NAND Flash Interface (ONFI).
[0021] return Figure 1 , the memory device 114 includes a protocol analyzer 140 embedded in the memory controller 118. The logic of the protocol analyzer 140 may be implemented in the processing circuitry 110 of the memory controller 118. The protocol analyzer 140 monitors and records the traffic between the host device 104 and the memory array. In contrast to the protocol analyzer 140 embedded in the memory device 114, including the protocol analyzer 140 in a separate device attached to the link between the host device 104 and the memory device 114 may interfere with or slow down the host-memory communication. Embedding the protocol analyzer 140 in the memory controller 118 allows the recording to be performed at a high speed.
[0022] The information captured (e.g., detected and stored) by the protocol analyzer 140 can be used by a programmer to determine the behavior of a software program and the performance of the memory when executing the program. The memory array is used as general memory for the program. A portion of the memory array is used to store log data collected by the protocol analyzer 140. The programmer can reserve or allocate a certain amount of the memory array for log data, and can configure the logic of the protocol analyzer 140 by sending a command with the starting address of the log and the size of the log to the memory controller 118.
[0023] Figure 3 is to operate the memory device (e.g. Figure 1 114 in the memory device to monitor and record the host device (e.g. Figure 1 Flow chart of a method 300 for performing transactions between a host device 104 in a memory device and a memory device.
[0024] At block 305, a memory controller (eg, Figure 1 The memory controller 118 of the host device receives a memory request from the host device. The memory request can be a memory read request, a memory write request, or another type of memory request.
[0025] At block 310, a protocol analyzer (eg, Figure 1 The protocol analyzer 140 in the memory analyzer 140 collects packet trace data from the memory request. In some examples, the packet trace data may include the command of the memory request (e.g., a read command or a write command) and the address of the memory request. If the memory request is a write request, the packet trace data may include the write data. If the memory request is a read request, the packet trace data may include the read data loaded from the memory. In some examples, the packet trace data may include the payload size of the write request or the read request. The packet trace data may also include an identifier (ID) of the host device sending the memory request. The packet trace data may include a timestamp of the memory request. The timestamp may be the current time in clock cycles or nanoseconds.
[0026] At block 315, the packet trace data is stored in a log in the memory array. Memory for the log may be reserved by sending a command to the memory controller containing a memory address for the starting address of the log and the size of the log in memory. This mapping provides direct load-store access to the program for the log data created by the program.
[0027] At block 320, the recorded packet trace data is returned to the host device. The packet trace data may be returned to the host device via a load command from the program. By default, a program may access its own log data. In some instances, the protocol analyzer includes a log status register for the log, and the protocol analyzer may use the log status register to indicate a log full status. In response to the log being full, the host device may read the status register and retrieve the packet trace data stored in the log. In some instances, the protocol analyzer sends an interrupt to the host device, and the host device reads the log data in response to the interrupt.
[0028] In some instances, the protocol analyzer may configure multiple logs in the memory array. This is useful for buffering log data. For example, if two logs are configured in the log area of the memory array, then when the first log becomes full, the protocol analyzer may switch to storing the packet trace data in the second log. When the first log becomes full, the log data from the first log may be sent to the host device. One or more status registers may be used to indicate the log status of each log configured by the protocol analyzer. In some instances, an interrupt to the host device may indicate which log is full, or the host device may track which log is currently in use and has a full status.
[0029] Figure 4 yes Figure 1 1 and 130. The block diagram shows a log area 442 of the memory and shows the logic of the protocol analyzer 140 in more detail. The log area 442 may include one log or more than one log. The interconnect link between the memory switch and the memory controller 118 includes a memory bus 444 (e.g., CXL) and a host input / output (I / O) channel 446. The memory bus is a data interface, and the memory controller 118 may receive memory requests via the memory bus. The memory requests may be stored in one or more queues 448. The packet tracking data may include a queue identifier that identifies which queue received the memory request. The host I / O channel 446 may include a configuration interface 450 that is accessed by the host device 104 using memory mapped I / O. The host I / O channel 446 is used for control and configuration information. The host I / O channel 446 may be used to send an interrupt to the host device 104, or the host I / O channel 446 may be used to read the log status register.
[0030] Configuration interface 450 may be used to configure the logic of protocol analyzer 140, such as by sending commands via host I / O channel 446 by host device 104. Region table 452 provides log region boundaries and log region configurations for packet tracing preferences. Multiple packet tracing preferences or features may be optionally configured into protocol analyzer 140 by sending commands to memory controller 118 to set fields of region table 452.
[0031] For example, a selective trace configuration may be programmed into the protocol analyzer 140. Collection of different packet trace data may be enabled for different address ranges of the log area 442. This allows different packet trace data to be collected for memory requests to different address ranges. A command filter option may be enabled to collect packet trace data for only a subset of memory requests. In some examples, command filters may be enabled and disabled to optionally collect packet trace data only for a subset of host devices 104 and only for certain types of operations per address range.
[0032] Another example of a selective tracing configuration is a record-only mode. In the record-only mode, the protocol analyzer 140 disables normal reading of data for memory read requests and disables normal writing of data for memory write requests for all address ranges or only for certain address ranges specified by the programmer. For disabled memory read and write requests, packet trace data is still collected and recorded.
[0033] The record-only mode reduces the need for shared main memory bandwidth for logging and read / write data storage by preventing normal reading and writing to designated memory areas for disabled data, and memory requests are dedicated to providing only packet trace data. This allows logging at real-time bandwidth or near real-time bandwidth. Write data in memory write requests can be ignored, and memory read requests can be responded to without accessing the memory die 130. The protocol analyzer 140 can optionally return useful status information with the read request response, such as how full the log is currently. The record-only mode can also provide immediate feedback on memory requests by returning specified performance or event counters, such as one or more of a row buffer hit indicator, bandwidth utilization, memory request latency, a heat map counter value for an address or address range, and device health status. The record-only mode is also useful for logging access to data objects for which there is no control dependency, such as neural network weights.
[0034] Table 1 shows an example of a region table 452. The fields listed are examples only, and additional fields may be included in the region table 452. In some examples, a different region table 452 is used for each configured log region, and in some examples, one region table is used for all log regions. The region table 452 may be looked up by the protocol analyzer control logic 454 after each memory request to determine what protocol analyzer action and configuration should be taken.
[0035] Table 1
[0036]
[0037]
[0038] The region table 452 may include a record mode field. The record mode field may be used to set the recording performed by the protocol analyzer control logic 454 to one of four or more different states. The first state is an off state, in which the recording of packet trace data is not performed. The second state is a command-only state, in which the protocol analyzer control logic 454 only records the command type (e.g., read, write, etc.) and the memory address of the memory request. The third state is a data-only state, in which only the write data or read data of the memory request is recorded. In a variant, the address is recorded together with the data. The fourth state is a command+data state, in which the command type, address, and data are recorded. The record mode field may include additional enable bits for enabling additional states. For example, the record mode field may include bits for optionally enabling the recording of other command packet metadata (e.g., the priority of the packet, the source identifier of the packet, etc.).
[0039] The region table 452 may include a data enable field. The data enable field may have three states: on, off, and off and read metadata. In the on state, the memory location is written and read with a memory request as in normal circumstances, and packet tracking data is recorded for the memory request in addition to the memory data. The on state may be the default state of the data enable field. In the on state, the protocol analyzer control logic 454 enables the main data path 456 to the memory and the protocol analyzer data path 458 to the memory.
[0040] In the off state, normal data writes are disabled for memory write requests, and no read data is returned for memory read requests. This is a log-only mode in which packet trace data is collected for memory requests, but no data is written or returned, although a log status (e.g., a full status) may be returned. In the off state, the protocol analyzer control logic 454 disables the main data path 456 to memory and enables the protocol analyzer data path 458 to memory. By preventing normal reads and writes to special log areas when data enable is off, a large amount of bandwidth to the memory die 130 can be saved and dedicated to logging writes when executing programs.
[0041] In the closed and read metadata state, normal data writes are disabled for memory write requests, and normal read data is not returned for memory read requests. However, a configurable read response is returned that may contain information useful to the programmer (read metadata). For example, the read response may include the current position in the log, which may be used by a program running on the host device 104. The read response may also include performance counters (e.g., indicating the current bandwidth of the memory or the latency of the memory) and memory health information (e.g., error counts).
[0042] The region table 452 may also include log configuration information, such as the log start address in the memory and the size of the log retained in the memory. The region table 452 may also include the start address and size of more than one log. For example, in a dual log buffering method, the region table 452 may include the start addresses of two logs in the memory.
[0043] The region table 452 may include a filter specification field. The filter specification field includes a set of masks (e.g., bit-level masks) that are compared to various fields of the memory request packet. Only those packets that have fields that match the set of masks are sent to the protocol analyzer control logic 454 for recording. Some examples of masks include specific command types, specific requesting host device IDs, packets with specific priorities, and packet payload sizes. A match between the mask in the filter specification field and the fields of a received memory request packet sends the packet to the protocol analyzer control logic 454 for recording.
[0044] The region table 452 may include a field for log field enable bits. The log field enable bits are a set of bits that indicate which portion of a memory request packet is included in the packet tracking data stored in the log region of the memory array. Some of the log field enable bits specify the storage of information that may not be included in the packet. Some examples of information that may optionally be included in the stored packet tracking data include a timestamp (e.g., in clock cycles or nanoseconds) of the memory request packet received by the memory device 114, the command, address, payload size, source host ID, and packet priority of the packet.
[0045] Another packet tracing feature provided by the embedded protocol analyzer is marker embedding. In marker embedding, the host device 104 can write to a marker control register using a special address exposed by the protocol analyzer control logic 454. The write request inserts a marker event in the packet tracing data stored in the log. The marker event can be an arbitrary data value. In some instances, the marker event is the value of an auto-increment counter. In some instances, the marker event is specific data that the programmer wants to track (e.g., the virtual address of a load / store instruction).
[0046] A software program may write any data value as a tag value. If the software simultaneously writes log entries for function call context or other context, the software program code may be aligned with the packet trace data off-line. A compiler, binary instrumentation, or programmer may record tags by inserting non-temporal write instructions to a tag control register in a software program. A program or utility library code called by a program may simultaneously record information about the program state or function name as part of the tag value stored in the log.
[0047] Table 2 is an example of code for storing a marker event in a log. The code first calls a library function (get_trace_control_ptr) to obtain the address of the marker control register to which the marker value will be written. A non-temporal store instruction that does not cache the write data may then write to the address indicated by the pointer and write the marker value to the log. In Table 2, the non-temporal store instruction (storeNT) forms a marker by concatenating a process ID (PID), the code's own instruction pointer (IP) (e.g., a code pointer to the storeNT instruction), and an identifier (ID) (which may be random, sequentially set, or determined by another scheme). These parameters for the marker value may be used by any of the compiler, binary instrumentation, or programmer, and may be used through an operating system (OS) function call.
[0048] Table 2.
[0049]
[0050] As the program code runs, it writes a unique tag value to the log at the entry and exit of each function call. The end result is a log of normal program memory accesses interspersed with tag entries. It should be noted that in systems with cache memory, only loads and stores that miss in the cache are logged, while all tags are logged. In addition, any log entry can be reordered by an out-of-order processor or other reordering in the storage system. Table 3 shows an example of a log generated using binary instrumentation.
[0051] Table 3.
[0052]
[0053] Tags in the log can be used for alignment of program and memory operations. Portions of a program (e.g., function calls) are associated with or close in time to memory operations that occur during the execution of the function. This allows the programmer to see which parts of the program cause memory patterns (bandwidth, latency, access frequency, etc.) on areas of interest (e.g., objects). For tighter alignment, barrier instructions in binary instrumentation can be used to force reordering of instructions. By encoding the appropriate fields in the tag, the programmer can obtain all necessary information about function calls using only the recorded packet trace data. This is true when the user includes the current function pointer or instruction address as part of the tag value.
[0054] An alternative method of alignment is to record two logs simultaneously; one log is recorded in software (e.g., saved to a disk of the host device) and the other log is recorded by a protocol analyzer embedded in the memory controller 118. Whenever a write is made to a memory control register, the tag value is also recorded to a file in the software along with the name of the calling function. The tag and packet trace data are typically collected by hardware. After the packet trace data is captured in both logs, the log data is retrieved from the memory controller 118 and an alignment tool (e.g., a process executed on the host device 104) scans the two logs from beginning to end, searching for a window of tag values that substantially match in the two logs (e.g., 90% of the tags in the window match). This provides an approximate alignment of the temporally related locations of function calls with the locations where the tags are stored.
[0055] Alignment using markers embedded in the log allows programmers and system designers to obtain detailed feedback about program behavior and memory performance. This helps programmers and system designers optimize the configuration of software and hardware.
[0056] The systems, devices, and methods described herein provide a protocol analyzer embedded in memory to monitor and record traffic on an interconnect bus, such as between a host processor and memory (e.g., CXL or Gen-Z protocol links), between a host processor and a storage device, or a network device. The recording can be done at high speed so as not to interfere with or slow down communications. Embedding the protocol analyzer 140 in the memory device 114 reduces the cost of high-speed protocol analysis and capture compared to other protocol monitoring methods. It also eliminates the need for expensive hardware and software tools for trace-level performance analysis and software optimization by customers (software) and hardware designers.
[0057] Figure 5 A block diagram illustrating an example machine 500 on which any one or more of the techniques (e.g., methodologies) described herein may be performed. As described herein, an example may include or be operated by logic or a number of components or mechanisms in the machine 500. A circuit system (e.g., a processing circuit system) is a collection of circuits including hardware (e.g., simple circuits, gates, logic, etc.) implemented in a tangible entity of the machine 500. Over time, the circuit system members may be flexible. The circuit system includes members that can perform specific operations alone or in combination when operating. In an example, the hardware of the circuit system may be designed invariably to perform specific operations (e.g., hard-wired).
[0058] In an example, the hardware of the circuit system may include variably connected physical components (such as execution units, transistors, simple circuits, etc.) that include machine-readable media that are physically modified (such as magnetic, electrical, removable placement of constant mass particles, etc.) to encode instructions for specific operations. When the physical components are connected, the basic electrical properties of the hardware composition are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (such as an execution unit or a loading mechanism) to generate a member of the circuit system in hardware via a variable connection to perform a portion of a specific operation when operating. Therefore, in an example, when the device operates, the machine-readable media element is part of the circuit system or is communicatively coupled to other components of the circuit system. In an example, any of the physical components can be used in more than one member of more than one circuit system. For example, in operation, an execution unit can be used in a first circuit of a first circuit system at one point in time and reused by a second circuit in the first circuit system or by a third circuit in the second circuit system at a different time. The following are additional examples of these components with respect to machine 500.
[0059] In alternative embodiments, the machine 500 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 500 may operate as a server machine or a client machine or both in a server-client network environment. In an example, the machine 500 may act as a peer machine in a peer-to-peer (P2P) (or other distributed) network environment. The machine 500 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile phone, a network facility, a network router, a switch or a bridge, or any machine capable of (sequentially or otherwise) executing instructions for actions specified by the machine. In addition, although only a single machine is described, the term "machine" should also be deemed to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods discussed herein (e.g., cloud computing, software as a service (SaaS), other computer cluster configurations).
[0060] The machine (e.g., computer system) 500 may include a hardware processor 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 504, a static memory (e.g., memory or storage for firmware, microcode, basic input output (BIOS), unified extensible firmware interface (UEFI), etc.) 506, and a mass storage device 508 (e.g., a hard drive, a tape drive, a flash storage device, or other block device), some or all of which may communicate with each other via an interconnection link (e.g., a bus) 530. One or both of the main memory and the static memory may include one or more SSD storage devices, PCI-SIG type storage devices, or SNIA type storage devices. The machine 500 may further include a display unit 510, an alphanumeric input device 512 (e.g., a keyboard), and a user interface (UI) navigation device 514 (e.g., a mouse). In an example, the display unit 510, the input device 512, and the UI navigation device 514 may be a touch screen display. The machine 500 may further include a storage system (e.g., a drive unit) 508, a signal generating device 518 (e.g., a speaker), a network interface device 520, and one or more sensors 516, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. The machine 500 may include an output controller 528, such as a serial (e.g., universal serial bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection for communicating with or controlling one or more peripheral devices (e.g., a printer, a card reader, etc.).
[0061] The processor 502, main memory 504, static memory 506, and mass storage 508 may be or include a machine-readable medium 522 on which is stored one or more sets of data structures or instructions 524 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 524 may also reside, completely or at least partially, within any register of the processor 502, main memory 504, static memory 506, or mass storage 508 during execution thereof by the machine 500. In an example, one or any combination of the hardware processor 502, main memory 504, static memory 506, or mass storage 508 may constitute the machine-readable medium 522. Although the machine-readable medium 522 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database and / or associated caches and servers) configured to store one or more instructions 524.
[0062] The term "machine-readable medium" may include any medium capable of storing, encoding, or carrying instructions executed by the machine 500 and causing the machine 500 to perform any one or more of the techniques of the present disclosure, or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memory, optical media, magnetic media, and signals (e.g., radio frequency signals, other photon-based signals, sound signals, etc.). In an example, a non-transitory machine-readable medium includes a machine-readable medium having a plurality of particles with a constant (e.g., stationary) mass, and is therefore a composition of matter. Thus, a non-transitory machine-readable medium is a machine-readable medium that does not include a transient propagating signal. Specific examples of non-transitory machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
[0063] In an example, the information stored or otherwise provided on the machine-readable medium 522 may represent instructions 524, such as the instructions 524 themselves or a format from which the instructions 524 may be derived. Such a format from which the instructions 524 may be derived may include source code, encoded instructions (e.g., in compressed or encrypted form), packaged instructions (e.g., divided into multiple packets), or the like. The information representing the instructions 524 in the machine-readable medium 522 may be processed by the processing circuit system into instructions to implement any of the operations discussed herein. For example, deriving the instructions 524 from the information (e.g., processing by the processing circuit system) may include: compiling (e.g., from source code, object code, etc.), interpreting, loading, organizing (e.g., dynamically or statically linking), encoding, decoding, encrypting, not encrypting, packaging, unpacking, or otherwise manipulating the information into instructions 524.
[0064] In an example, the export of instructions 524 may include assembling, compiling, or interpreting (e.g., by processing circuitry) information to create instructions 524 from some intermediate or pre-processed format provided by machine-readable medium 522. When the information is provided in multiple parts, the information may be combined, unpacked, and modified to create instructions 524. For example, the information may be in multiple compressed source code packages (or object code, or binary executable code, etc.) on one or several remote servers. The source code packages may be encrypted when transmitted over the network, and decrypted, decompressed, assembled (e.g., linked) as necessary, and compiled or interpreted at the local machine (e.g., compiled or interpreted into a library, a stand-alone executable file, etc.) and executed by the local machine.
[0065] The instructions 524 may further be transmitted or received over a communication network 526 using a transmission medium via a network interface device 520 utilizing any of a number of transmission protocols, such as frame relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc. Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network such as the Internet, a mobile telephone network such as a cellular network, a plain old telephone (POTS) network, and a wireless data network such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards (known as ), IEEE 802.16 series of standards (called ), IEEE 802.15.4 family of standards), peer-to-peer (P2P) networks, and the like. In an example, the network interface device 520 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 526. In an example, the network interface device 520 may include multiple antennas to communicate wirelessly using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. The term "transmission media" should be taken to include any intangible media capable of storing, encoding, or carrying instructions executed by the machine 500, and includes digital or analog communication signals or other intangible media that facilitate the communication of such software. Transmission media is machine-readable media.
[0066] The processing device 502 may represent one or more general purpose processing devices, such as a microprocessor, a central processing unit, or the like. More specifically, the processing device may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or multiple processors implementing a combination of instruction sets. The processing device 502 may also be one or more special purpose processing devices, such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, or the like. The processing device 502 may be configured to execute instructions 524 for performing the operations and steps discussed herein. The computer system 500 may further include a network interface device 520 for communicating over a network 526.
[0067] The storage system 508 may include a machine-readable storage medium (also referred to as a computer-readable medium) on which is stored one or more sets of instructions 524 or software embodying any one or more of the methodologies or functions described herein. The instructions 524 may also reside, completely or at least partially, within the main memory 504 or within the processing device 502 during execution thereof by the computer system 500, the main memory 504 and the processing device 502 also constituting machine-readable storage media.
[0068] The term "machine-readable storage medium" should be understood to include a single medium or multiple media storing one or more sets of instructions or any medium capable of storing or encoding a set of instructions executed by a machine and causing the machine to perform any one or more of the methods of the present disclosure. Thus, the term "machine-readable storage medium" should be considered to include, but not be limited to, solid-state memory, optical media, and magnetic media. In an example, a massed machine-readable medium includes a machine-readable medium having a plurality of particles with a constant (e.g., stationary) mass. Thus, a massed machine-readable medium is not a transient propagating signal. Specific examples of massed machine-readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
[0069] The machine 500 may further include a display unit, an alphanumeric input device (e.g., a keyboard), and a user interface (UI) navigation device (e.g., a mouse). In an example, one or more of the display unit, the input device, and the UI navigation device may be a touch screen display. The machine is a signal generating device (e.g., a speaker) or one or more sensors, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or one or more other sensors. The machine 500 may include an output controller, such as a serial (e.g., universal serial bus (USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., printers, card readers, etc.).
[0070] Instructions 524 (e.g., software, programs, operating system (OS), etc.) or other data stored on storage system 508 may be accessed by main memory 504 for use by processing device 502. Main memory 504 (e.g., DRAM) is typically fast but volatile, and is therefore a different type of storage than storage system 508 (e.g., SSD), which is suitable for long-term storage (including in a "powered down" condition). Instructions 524 or data used by a user or machine 500 are typically loaded into main memory 504 for use by processing device 502. When main memory 504 is full, virtual space from storage system 508 may be allocated to supplement main memory 504; however, because storage system 508 devices are typically slower than main memory 504, and write speeds are typically at least 2 times slower than read speeds, using virtual memory can significantly reduce the user experience due to storage system latency (compared to main memory 504, such as DRAM). In addition, using storage system 508 for virtual memory can significantly reduce the usable lifespan of storage system 508.
[0071] The instructions 524 may further be transmitted or received over a network 526 using a transmission medium via a network interface device 520 utilizing any of a number of transmission protocols, such as frame relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc. Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network such as the Internet, a mobile telephone network such as a cellular network, a plain old telephone (POTS) network, and a wireless data network such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards (known as ), IEEE 802.16 series of standards (called ), IEEE 802.15.4 family of standards), peer-to-peer (P2P) networks, etc.). In an example, the network interface device 508 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the network 520. In an example, the network interface device 508 may include multiple antennas to communicate wirelessly using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technology. The term "transmission media" should be taken to include any intangible medium capable of storing, encoding, or carrying instructions executed by the machine 500, and includes digital or analog communication signals or other intangible media that facilitate communication of such software.
[0072] The above detailed description includes references to the accompanying drawings that form a part of the detailed description. The drawings show, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are also referred to herein as "examples". Such examples may include elements other than the elements shown or described. However, the inventors also contemplate examples in which only those elements shown or described are provided. In addition, the inventors also contemplate examples (or one or more aspects thereof) using any combination or arrangement of those elements shown or described with respect to a specific example (or one or more aspects thereof) or with respect to other examples (or one or more aspects thereof) shown or described herein.
[0073] All publications, patents, and patent documents referenced in this document are incorporated herein by reference in their entirety, as if individually incorporated by reference. In the event of inconsistent usages between this document and the documents incorporated by reference, the usage in the incorporated references should be considered supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
[0074] In this document, the term "a or an" is used, as is common in patent documents, to include one or more than one, independent of any other examples or usages of "at least one" or "one or more". In this document, the term "or" is used to refer to a non-exclusive or, so that "A or B" includes "A but not B", "B but not A" and "A and B", unless otherwise indicated. In the appended claims, the terms "including" and "in which" are used as the common English equivalents of the corresponding terms "including" and "wherein". Moreover, in the appended claims, the terms "including" and "comprising" are open-ended, that is, a system, device, article or process containing elements other than those listed after this term in the claims is still considered to fall within the scope of the claims. In addition, in the appended claims, the terms "first", "second" and "third" etc. are used only as labels, and it is not desired to impose numerical requirements on their objects.
[0075] In various examples, the components, controllers, processors, units, engines, or tables described herein may include, among other things, physical circuitry or firmware stored on a physical device. As used herein, "processor" means any type of computing circuit, such as, but not limited to, a microprocessor, a microcontroller, a graphics processor, a digital signal processor (DSP), or any other type of processor or processing circuit (including a processor group or a multi-core device).
[0076] Various embodiments according to the present disclosure and described herein include memories utilizing vertical structures of memory cells (e.g., strings of NAND memory cells). As used herein, directional adjectives will be considered relative to the surface of the substrate on which the memory cells are formed (i.e., the vertical structures will be considered to extend away from the substrate surface, the bottom end of the vertical structures will be considered to be the end closest to the substrate surface and the top end of the vertical structures will be considered to be the end farthest from the substrate surface).
[0077] As used herein, operating a memory cell includes reading from, writing to, or erasing the memory cell. The operation of placing a memory cell in a desired state is referred to herein as "programming," and may include both writing to or erasing from the memory cell (i.e., the memory cell may be programmed to an erased state).
[0078] According to one or more embodiments of the present disclosure, a memory controller (e.g., a processor, a controller, firmware, etc.) located inside or outside a memory device is capable of determining (e.g., selecting, setting, adjusting, calculating, changing, clearing, communicating, adapting, deriving, defining, utilizing, modifying, applying, etc.) a certain number of wear cycles or wear states (e.g., recording wear cycles, counting operations of a memory device as they occur, tracking operations of the memory device from which they originate, evaluating memory device characteristics corresponding to wear states, etc.).
[0079] According to one or more embodiments of the present disclosure, a memory access device may be configured to provide wear cycle information to a memory device with each memory operation. A memory device control circuit system (e.g., control logic) may be programmed to compensate for memory device performance variations corresponding to the wear cycle information. The memory device may receive the wear cycle information and determine one or more operating parameters (e.g., values, characteristics) in response to the wear cycle information.
[0080] It should be understood that when an element is referred to as being "on," "connected to," or "coupled with" another element, it may be directly on, directly connected to, or directly coupled to the other element or there may be intervening elements. In contrast, when an element is referred to as being "directly on," "directly connected to," or "directly coupled to," there are no intervening elements or layers. If two elements are shown in a drawing as having a line connecting them, the two elements may be coupled or directly coupled unless otherwise indicated.
[0081] The method examples described herein may be at least partially machine or computer implemented. Some examples may include a computer-readable medium or machine-readable medium encoded with instructions operable to configure an electronic device to perform the methods described in the above examples. Implementations of such methods may include code, such as microcode, assembly language code, high-level language code, or the like. This code may include computer-readable instructions for performing various methods. The code may form part of a computer program product. In addition, the code may be tangibly stored on one or more volatile or non-volatile tangible computer-readable media, such as during execution or at other times. Examples of these tangible computer-readable media may include, but are not limited to: a hard disk, a removable disk, a removable optical disk (e.g., a compact disk and a digital video disk), a cassette tape, a memory card or stick, a random access memory (RAM), a read-only memory (ROM), and the like.
[0082] Example 1 includes subject matter, such as a memory device, comprising: one or more integrated circuit (IC) memory dies configured as a memory array; and a memory controller for controlling access to the memory array. The memory controller is configured to: receive memory requests from a host device; collect packet trace data from the memory requests; include the packet trace data in a log stored in a log area of the memory array; and return the log to the host device.
[0083] In Example 2, the subject matter of Example 1 optionally includes a memory controller configured to: receive a plurality of memory requests from the host device; compare the memory requests to one or more packet trace filters; capture packet trace data having properties specified in the one or more packet trace filters only from a subset of the plurality of memory requests and not capture packet trace data from memory requests that do not have the properties specified in the one or more packet trace filters; and store the captured packet trace data in the log.
[0084] In Example 3, the subject matter of Example 2 optionally includes a memory controller configured to: receive the one or more packet tracing filters from the host device; receive a configuration of a log area of the memory array for the log from the host device; and collect packet tracing data according to the one or more packet tracing filters and store the packet tracing data in the log area.
[0085] In Example 4, the subject matter of one or any combination of Examples 1 to 4 optionally includes a memory controller configured to: receive an indication of one or more fields of the memory request to include in the packet tracking data; and collect data from the indicated one or more fields of the memory request and store the data in the log as the packet tracking data.
[0086] In Example 5, the subject matter of one or any combination of Examples 1 to 4 optionally includes a memory controller configured to: collect the packet tracking data from the memory request; and when data disable is active in the memory controller, disable one or both of writing write data in the memory request to the memory array and returning read data for the memory request.
[0087] In Example 6, the subject matter of one or any combination of Examples 1 to 6 optionally includes a memory controller configured to: receive a memory read request with a data disable indication from the host device; record packet tracking data from the memory request in the log; disable inclusion of data in a response to the memory read request; and include read metadata in the response to the memory read request.
[0088] In Example 7, the subject matter of one or any combination of Examples 1-6 optionally includes a memory controller including a tag control register writable by the host device. The memory controller is configured to store a tag value in the log with the packet trace data according to the tag control register.
[0089] In Example 8, the subject matter of one or any combination of Examples 1 to 7 optionally includes a memory controller configured to: receive a configuration of a first log area of the memory array for the log and a second log area for the log from the host device; store the packet tracking data in the first log area of the log, and store the packet tracking data in the second log area of the log when the first log area is full; and return to the first log area when the first log area is full.
[0090] Example 9 includes subject matter, such as a method of operating a memory device, or may optionally be combined with one or any combination of Examples 1-8 to include such subject matter, comprising: receiving, by a memory controller of the memory device, a memory request from a host device; collecting packet tracking data from the memory request; including the packet tracking data in a log stored in a memory array of the memory device; and returning the log to the host device.
[0091] In Example 10, the subject matter of Example 9 optionally includes: receiving a plurality of memory requests from the host device; capturing packet trace data having properties specified in one or more packet trace filters only from a subset of the plurality of memory requests; and storing the captured packet trace data in the log.
[0092] In Example 11, the subject matter of Example 10 optionally includes: receiving the one or more packet tracing filters from the host device; receiving a log size and a log start address specifying a log area of the memory from the host device; capturing the packet tracing data of the subset of multiple memory requests according to the one or more packet tracing filters; and storing the packet tracing data in the log area of the memory array.
[0093] In Example 12, the subject matter of Example 10 optionally includes: receiving a plurality of memory requests from the host device; receiving one or more data logging field enables from the host device; and logging only enabled packet tracking data from the plurality of memory requests in the log.
[0094] In Example 13, the subject matter of one or any combination of Examples 9 to 12 optionally includes: receiving a data disable indication from the host device; recording packet tracking data from the memory request in the log; and in response to the data disable indication, disabling write data and disabling read data returned for the memory request.
[0095] In Example 14, the subject matter of one or any combination of Examples 9 to 13 optionally includes: receiving a memory read request with a data disable indication from the host device; recording packet tracking data from the memory request in the log for the memory read request; disabling read data returned for the memory read request; and returning read metadata to the host device in a response to the memory read request.
[0096] In Example 15, the subject matter of one or any combination of Examples 1-14 optionally includes: receiving a tag with the memory request; storing the tag in the log along with the packet tracking data for the memory request.
[0097] In Example 16, the subject matter of Example 15 optionally includes the host device writing a tag value to a tag control register of the memory controller to insert the tag value in the log.
[0098] In Example 17, the subject matter of one or any combination of Examples 9 to 16 optionally includes: storing the packet tracking data in a first log area of the log, and storing the packet tracking data in a second log area of the log when the first log area is full; and returning to the first log area when the first log area is full.
[0099] Example 18 includes subject matter, such as a computer system, or can be optionally combined with one or any combination of Examples 1-17 to include such subject matter, comprising: at least one host device including a host processor; a memory bus and a host input / output (I / O) channel; and at least one memory device coupled to the at least one host device via the memory bus and the host I / O channel. The memory device includes: one or more integrated circuit (IC) memory dies configured as a memory array; and a memory controller for controlling access to the memory array. The memory controller is configured to: retain a log in the memory array according to log configuration information received from the at least one host device via the host I / O channel; receive a memory request from the at least one host device via the memory bus; store packet tracking data from the memory request in the log; and return the packet tracking data stored in the log to the host device.
[0100] In Example 19, the subject matter of Example 18 optionally includes log configuration information received from the host device, including a log memory start address and a log memory size and one or more data field enables. The memory controller is configured to: capture only packet trace data having properties specified in one or more packet trace filters from a subset of the plurality of memory requests and only capture packet trace data enabled by the one or more data field enables; and store the captured packet trace data in the log.
[0101] In Example 20, the subject matter of one or both of Examples 18 and 19 optionally includes a memory controller including a log status register readable via the host I / O channel, and the memory controller is configured to set the log status register to a log full state of the log full packet tracking data.
[0102] Example 21 is at least one machine-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement any of Examples 1-20.
[0103] Example 22 is an apparatus comprising means for implementing any of Examples 1-20.
[0104] Example 23 is a system for implementing any of Examples 1-20.
[0105] Example 24 is a method for implementing any of Examples 1-20.
[0106] The above description is intended to be illustrative rather than restrictive. For example, the above examples (or one or more aspects thereof) may be used in combination with each other. After reviewing the above description, other embodiments may be used by a person of ordinary skill in the art, for example. An abstract is provided to comply with 37C.FR§1.72(b) to allow the reader to quickly determine the nature of the technical disclosure. The abstract is submitted with the understanding that it is not intended to explain or limit the scope or meaning of the claims. Moreover, in the above specific embodiments, various features may be grouped together to simplify the present invention. This should not be interpreted as wishing that the disclosed features not claimed are essential to any claim. Specifically, the subject matter of the present invention may be less than all the features of a specific disclosed embodiment. Therefore, the attached claims are hereby incorporated into the specific embodiments, wherein each claim itself is a separate embodiment, and it is expected that such embodiments can be combined with each other in various combinations or arrangements. The scope of the present invention should be determined with reference to the attached claims together with the full range of equivalents authorized by such claims.
Claims
1. A memory device, comprising: one or more integrated circuit (IC) memory dies configured as a memory array; and a memory controller for controlling access to the memory array, the memory controller being configured to: receiving a memory request from a host device; requesting collection of packet trace data from said memory; including the packet trace data in a log stored in a log area of the memory array; and The log is returned to the host device.
2. The memory device of claim 1 , wherein the memory controller is configured to: receiving a plurality of memory requests from the host device; comparing the memory request to one or more packet trace filters; capturing packet trace data having properties specified in the one or more packet trace filters from only a subset of the plurality of memory requests and not capturing packet trace data from memory requests not having the properties specified in the one or more packet trace filters; and The captured packet trace data is stored in the log.
3. The memory device of claim 2, wherein the memory controller is configured to: receiving the one or more packet trace filters from the host device; receiving from the host device a configuration of a log area of the memory array for the log; and Packet trace data is collected according to the one or more packet trace filters and stored in the log area.
4. The memory device of claim 1 , wherein the memory controller is configured to: receiving an indication of one or more fields of the memory request for inclusion in the packet trace data; and Data is collected from the indicated one or more fields of the memory request and stored in the log as the packet trace data.
5. The memory device of claim 1 , wherein the memory controller is configured to: requesting collection of the packet trace data from the memory; and When data disabling is active in the memory controller, one or both of writing write data in the memory request to the memory array and returning read data of the memory request are disabled.
6. The memory device of claim 1, wherein the memory controller is configured to: receiving a memory read request with a data disable indication from the host device; recording packet trace data from the memory request in the log; disabling inclusion of data in a response to said memory read request; and Read metadata is included in the response to the memory read request.
7. The memory device of claim 1, wherein the memory controller includes a tag control register writable by the host device, and wherein the memory controller is configured to store a tag value with the packet tracking data in the log according to the tag control register.
8. The memory device of claim 1, wherein the memory controller is configured to: receiving, from the host device, configuration of a first log area of the memory array for the log and a second log area for the log; storing the packet tracking data in a first log area of the log, and storing the packet tracking data in a second log area of the log when the first log area is full; and Wherein the returning the log to the host device includes returning the first log area when the first log area is full.
9. A method of operating a memory device, the method comprising: receiving, by a memory controller of the memory device, a memory request from a host device; requesting collection of packet trace data from said memory, including the packet trace data in a log stored in a memory array of the memory device; and The log is returned to the host device.
10. The method according to claim 9, comprising: receiving a plurality of memory requests from the host device; capturing, from only a subset of the plurality of memory requests, packet trace data having properties specified in one or more packet trace filters; and The captured packet trace data is stored in the log.
11. The method according to claim 10, comprising: receiving the one or more packet trace filters from the host device; receiving from the host device a log size and a log start address specifying a log area of the memory; and The packet trace data for the subset of a plurality of memory requests is captured according to the one or more packet trace filters and the packet trace data is stored in the log area of the memory array.
12. The method according to claim 10, comprising: receiving a plurality of memory requests from the host device; receiving one or more data record field enables from the host device; and Wherein said capturing the packet trace data comprises recording only enabled packet trace data from the plurality of memory requests in the log.
13. The method according to claim 9, comprising: receiving a data disable indication from the host device; recording packet trace data from the memory request in the log; and In response to the data disable indication, write data is disabled and read data returned for the memory request is disabled.
14. The method according to claim 9, comprising: receiving a memory read request with a data disable indication from the host device; recording, in the log, packet trace data from the memory request for the memory read request; disabling returning read data of the memory read request; and Read metadata is returned to the host device in a response to the memory read request.
15. The method of claim 9, wherein the receiving the memory request from the host device comprises: receiving a tag with the memory request; and The tag is stored in the log along with the packet trace data for the memory request.
16. The method of claim 15, wherein the receiving the tag comprises the host device writing a tag value to a tag control register of the memory controller to insert the tag value in the log.
17. The method according to claim 9, wherein storing the packet tracking data in the log comprises storing the packet tracking data in a first log area of the log, and storing the packet tracking data in a second log area of the log when the first log area is full; and Wherein the returning the log to the host device includes returning the first log area when the first log area is full.
18. A computer system comprising: at least one host device comprising a host processor; Memory bus and host input / output I / O channels; and at least one memory device coupled to the at least one host device through the memory bus and a host I / O channel, wherein the memory device comprises: one or more integrated circuit (IC) memory dies configured as a memory array; and a memory controller for controlling access to the memory array, the memory controller being configured to: retaining a log in the memory array according to log configuration information received from the at least one host device via the host I / O channel; receiving a memory request from the at least one host device via the memory bus; storing packet tracking data from the memory request in the log; and The packet trace data stored in the log is returned to the host device.
19. The computer system of claim 18, wherein the log configuration information received from the host device comprises: Log memory start address and log memory size; one or more packet tracking filters; One or more data fields are enabled; and wherein the memory controller is configured to: capturing only packet trace data having properties specified in the one or more packet trace filters from a subset of the plurality of memory requests and only packet trace data enabled by the one or more data field enables; and The captured packet trace data is stored in the log.
20. The computer system of claim 18, wherein the memory controller comprises: a log status register, which can be read via the host I / O channel, and Wherein the memory controller is configured to set the log status register to a log full state of the log full of packet tracking data.
Citation Information
Cited By
Storage system, data storage method, equipment, storage medium and program product
CN120196290A
