Skip to content

Conversation

@JannePeltonen
Copy link
Collaborator

Current API regarding dynamic packet references is not easy to efficiently support in some ODP implementations with HW accelerated packet output due to the need to update reference counts after TX completion and based on that conditionally free packet buffers. odp_packet_ref() has been implemented only as a full packet copy in all ODP implementation.

Redefine the semantics of odp_packet_ref() and the packets involved in packet data sharing in a way that hopefully makes it simpler to support packet data sharing with restrictions in packet output and with per-packet reference counting instead of per-segment reference counting. The new semantics also enable use cases that were not previously possible.

Specify better the rules regarding packet data layout manipulation operations, allowing private packet data also in the tail of the packets that reference other packets. Pull and truncate operations may involve shared packet data, in which case they just remove that data from the packet, not affecting the packet owning the data. All extend and truncate operations always produce non-shared packet data.

Change odp_packet_has_ref() to indicate whether a packet is referenced by another packet, not whether the packet shares data with another packet. In partivular, odp_packet_ref() returns a packet that shares data with the given packet but is not itself referenced by other packets. Specify that packet data and layout of packets referenced by other packets can not be modified at all.

Introduce pktio capability bits to indicate whether a pktio supports sending packets with shared data without using the dont_free flag. Sending with the dont_free flag is supported with all types of packets.

@odpbuild odpbuild changed the title api: packet: redefine packet data sharing [PATCH v1] api: packet: redefine packet data sharing Nov 11, 2025
@MatiasElo MatiasElo added this to the v1.49.0 milestone Nov 19, 2025
* Packets returned by this function can be used normally in ODP API functions
* unless otherwise noted. There are restrictions in packet output.
*
* Referenced packets can be used in ODP API functions that treat packet data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should use one word to refer. Either base packet or referenced packet.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed in v2 so that we talk about referenced packets, not base packets.

* of a static reference it also shares metadata. Packet data and data layout
* of packet that have references must be treated as read only.
*
* Packets created through odp_packet_ref() or odp_packet_ref_hdr() share data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

odp_packet_ref_hdr() --> odp_packet_ref_pkt()

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in v2

@odpbuild odpbuild changed the title [PATCH v1] api: packet: redefine packet data sharing [PATCH v2] api: packet: redefine packet data sharing Dec 2, 2025
@JannePeltonen
Copy link
Collaborator Author

v2: Many text clarifications and typo fixes. Removed base packet from terminology. Made the packet I/O capabilities more granular. Added reference related text in odp_packet_concat() specification. Added a new function to test whether a packet is a referencing packet. Mentioned that the functions that create referencing packets and static references can be called simultaneously in multiple threads for the same packet.

@odpbuild odpbuild changed the title [PATCH v2] api: packet: redefine packet data sharing [PATCH v3] api: packet: redefine packet data sharing Dec 9, 2025
@JannePeltonen
Copy link
Collaborator Author

v3: Specified that sending shared packets to TM must obey the restrictions of the egress pktio (but currently TM does not support the dont_free flag, which maybe needs to change).

@odpbuild odpbuild changed the title [PATCH v3] api: packet: redefine packet data sharing [PATCH v4] api: packet: redefine packet data sharing Dec 10, 2025
@JannePeltonen
Copy link
Collaborator Author

JannePeltonen commented Dec 10, 2025

v4:

  • Renamed odp_pktout_shared_packet_capability_t to odp_pktout_packet_ref_capability_t and rewrote the description for better clarity.
  • Renamed odp_pktio_capability_t::shared_pkt_consume to odp_pktio_capability_t::packet_ref
  • Added text to odp_packet_free() to describe handling of packet references
  • Removed the restriction that the ODP_PACKET_FREE_CTRL_DONT_FREE may not be set in packets with multiple references.
  • Added TM capability bits that tell whether different types of packet references may be enqueued to TM. Since TM capabilities are separate for different egresses or TM systems, the capability to handle packet references can depend on the underlying pktio. The don't_free packet option continues to not have an effect in odp_tm_enqueue().
  • fixed a couple of typos

@JannePeltonen JannePeltonen marked this pull request as ready for review December 12, 2025 12:05
Comment on lines 550 to 553
* Packets that share data with other packets may be sent without the
* dont_free option only if the relevant packet_ref capability is set
* (see odp_pktout_packet_ref_capability_t).
*
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just use the same text as in odp_pktout_event_queue() and odp_pktout_send() spec?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done in v5

*
* Packets that participate in packet data sharing (see odp_packet_ref()
* and odp_packet_ref_static()) may not get freed back to the packet pool
* immediately when this function is called:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since reference to a packet is a special case, only minimal documentation of it should be here and majority under e.g. odp_packet_ref().

E.g. here we could just say: "In case of packet references, the referenced packet(s) is freed back to the packet pool only after there are no more references to it."

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shortened and reworded in v5.

I avoided saying that the packet won't be freed until references to it disappear so that the text cannot be interpreted to mean that everything gets postponed until that point and that the packet could still be used (and be in a not-freed state) until that.

@odpbuild odpbuild changed the title [PATCH v4] api: packet: redefine packet data sharing [PATCH v5] api: packet: redefine packet data sharing Dec 23, 2025
@JannePeltonen
Copy link
Collaborator Author

v5: Updated based on review comments. Text clarifications only, no semantic changes.

*
* The packet passed to this function must not reference another packet or
* be a static reference (see odp_packet_ref_static()). It can already be
* a referenced packet.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Function documentation would be cleared for the (first time) reader, if this limitation is stated in the beginning. I'd move this just after the first paragraph (definition of referenced/referencing) and change:
"... must not reference another packet..." -> "...must not be a referencing packet or a static reference..."

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved and changed in v6

* reference. Must be a unique reference.
* @param hdr Handle of the header packet to be prefixed
*
* @return New reference the reference packet
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something wrong in our current return value documentation. This and odp_packet_ref() return value could be documented as "Handle of the newly created referencing packet".

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in v6

@MatiasElo MatiasElo removed this from the v1.49.0 milestone Dec 29, 2025
@JannePeltonen
Copy link
Collaborator Author

v6: cosmetic changes based on review comments, rebased

Current API regarding dynamic packet references is not easy to
efficiently support in some ODP implementations with HW accelerated
packet output due to the need to update reference counts after TX
completion and based on that conditionally free packet buffers.
odp_packet_ref() has been implemented only as a full packet copy in
all ODP implementations.

Redefine the semantics of odp_packet_ref() and the packets involved
in packet data sharing in a way that hopefully makes it simpler to
support packet data sharing with restrictions in packet output and
with per-packet reference counting instead of per-segment reference
counting. The new semantics also enable use cases that were not
previously possible.

Specify better the rules regarding packet data layout manipulation
operations, allowing private packet data also in the tail of the
packets that reference other packets. Pull and truncate operations may
involve shared packet data, in which case they just remove that data
from the packet, not affecting the packet owning the data. All extend
and truncate operations always produce non-shared packet data.

Change odp_packet_has_ref() to indicate whether a packet is referenced
by another packet, not whether the packet shares data with another
packet. In particular, odp_packet_ref() returns a packet that shares
data with the given packet but is not itself referenced by other
packets. Specify that packet data and layout of packets referenced by
other packets cannot be modified at all.

Add new odp_packet_is_referencing() to test whether a packet
references another packet.

Introduce pktio capability bits to indicate whether a pktio supports
sending packets with shared data without using the dont_free flag.
Sending with the dont_free flag is supported with all types of packets.

Signed-off-by: Janne Peltonen <janne.peltonen@nokia.com>
@odpbuild odpbuild changed the title [PATCH v5] api: packet: redefine packet data sharing [PATCH v6] api: packet: redefine packet data sharing Dec 31, 2025
@JannePeltonen JannePeltonen changed the title [PATCH v6] api: packet: redefine packet data sharing [PATCH v6] api: packet: redefine packet data sharing with packet references Dec 31, 2025
*
* Packets that reference or are referenced by other packets may be sent
* using this function only if the pktout to be used has the relevant
* capability. See odp_pktio_capability_t::packet_ref. XXX dontfree
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"XXX dontfree" some leftover?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants