Constraints

Coding Constraints and Implementation Requirements

To clearly define technical boundaries and responsibilities regarding the interface implementations described in this section, the following statements are hereby issued:

• Parameter verification responsibility

  DPUs are highly sensitive to performance. To minimize performance loss, the internal implementation of the programming framework does not perform validity checks on input parameters (including but not limited to data types, value ranges, and logical correlations). The caller is solely responsible for ensuring that all passed parameters strictly adhere to interface constraints and technical specifications to prevent security vulnerabilities, such as out-of-bounds memory access or data corruption caused by invalid parameters.

• Unverified interfaces
  • hdr_packet_delete_from_head
  • hdr_packet_insert_from_head
  • hdr_packet_modify
  • hdr_packet_calc_checksum_incr
  • hdr_packet_calc_inserted_checksum_incr
  • hdr_packet_calc_checksum
  • hdr_packet_calc_inserted_checksum

    For details about the interface specifications, see Table 2.

• Consequence bearing

  The caller shall assume full responsibility for the following issues arising from invalid parameters passed to the Hydra interfaces:

  • NIC functional anomalies and service crashes
  • Stability issues, including but not limited to memory leaks and resource contention