c - "tearing"在部分程序注释中的使用

Question

当我读一些C程序的时候，我发现了一些评论，比如“撕裂事件”“包含撕裂信息数据的结构”“撕裂分析”。这让我这个母语不是英语的人感到困惑理解“撕裂”一词的含义。那么怎么理解呢？

`typedef struct tagRmsTearingServiceInfo
{
    UINT32  nvmLastPhysErrAddr;     ///< NVM physical address of last defective sector
    UINT8   nvmErrorCnt;            ///< NVM error counter for Map RAM-Init
    UINT8   nvmUnrecErrorCnt;       ///< NVM unrecoverable error counter
    UINT8   analysisData[10];       ///< 10 bytes for IFX internal use for tearing analysis
} RMS_TEARING_SERVICE_INFO;
/** Volatile FL Mailbox Area declarations */
typedef struct tagVolatileFlMailboxArea
{
    UINT16                      version;
    UINT16                      mailboxStatus;
    UINT16                      mailboxUpdateInfo;
    UINT8                       rfu_000[2];
    UINT32 volatile             interfaceActivationInfo;
    PIFX_MAILBOX_PAGE2          ifxMailboxPage2Addr;
    RMS_TEARING_SERVICE_INFO    rmsTearingServiceInfo;
    UINT8                       rfu_010[76];
    UINT32                      flStartMode;
    UINT8                       secFLTMDownloadKey[16];
} VOLATILE_FL_MAILBOX_AREA;`

Answer 1

撕裂是一个特定领域的术语。 nemequ 已经提到了最常见的领域，与 GPU 硬件和编程相关。

在您的情况下，基于评论关键字 NVM、IFX 等。我怀疑撕裂是指中断的 NVM 操作。参见例如TLE987xQX BF BootROM User Manual

它在段落中隐式定义:

reduce the risk of data loss in case of interrupted NVM operations (tearing events)

在这里:

a NVM program or erase operation interrupted by any reset or power loss (tearing events).

另见 5.4.4.2 Tearing-safe Programming来自同一本手册。

In TLE987xQX, the mapping mechanism of the non-linearly mapped sector is used like a log-structured file system. When a page is programmed in this sector, the old values are not physically overwritten, but a different physical page (spare page) in the same sector is programmed. If the programming fails, the old values are still present in the sector and user can decide, by means of a specific input parameter of the user programming routine (refer to Table 5-17), whether the old values or the new failing values should be physically kept in the sector. When an erase or write procedure is interrupted by a power down, this is identified during the reconstruction of the MapRAM content after the next reset. In this case, the service algorithm routine is automatically started and repairs the NVM state exploiting the fact that either the old or the new data (or both) are fully valid