一段注释的翻译

/*

* Pay for annotated transport delays.

*

* The header delay marks the point in time, when the packet first is seen

* by the transactor. This is the point in time when the transactor needs

* to send the BEGIN_REQ to the SystemC world.

*

* NOTE: We drop the payload delay here. Normally, the receiver would be

* responsible for handling the payload delay. In this case, however,

* the receiver is a SystemC module and has no notion of the cpu model

* transport protocol and we cannot simply forward the

* payload delay to the receiving module. Instead, we expect the

* receiving SystemC module to model the payload delay by deferring

* the END_REQ. This could lead to incorrect delays, if the XBar

* payload delay is longer than the time the receiver needs to accept

* the request (time between BEGIN_REQ and END_REQ).

*

* TODO: We could detect the case described above by remembering the

* payload delay and comparing it to the time between BEGIN_REQ and

* END_REQ. Then, a warning should be printed.

*/

/*
*支付注明运输延误的费用。
*
*报头延迟标记了首次看到数据包的时间点
*由交易人。这是交易者需要的时间点
*将BEGIN_REQ发送到SystemC世界。
*
*注意：我们在此处删除有效载荷延迟。通常，接收器将是
*负责处理有效载荷延迟。然而在这种情况下，
*接收器是一个SystemC模块，没有CPU模型的概念
*传输协议，我们不能简单地转发
*有效载荷延迟到接收模块。相反，我们期待
*接收SystemC模块，通过延迟对有效载荷延迟进行建模
*END_REQ。这可能会导致错误的延迟，如果XBar
*有效载荷延迟长于接收器需要接受的时间
*请求（BEGIN_REQ和END_REQ之间的时间）。
*
*TODO：我们可以通过记住
*有效载荷延迟，并将其与BEGIN_REQ和END_REQ之间的时间进行比较。然后，应打印警告。
*/