On 16/04/15 17:11, Taras Kondratiuk wrote:
On 04/16/2015 06:00 PM, Zoltan Kiss wrote:
Hi,
I've noticed that a buffer allocated from a ODP_POOL_BUFFER type of pool
doesn't have any means to store how much of the data there is actually
used. You can see how big is the reserved area and at what address it
starts, but no way to maintain this information. Packet buffers support
that by odp_packet_(seg_)len and pushing/pulling tail and head. I know
raw buffers are supposed to stay simple, but isn't this a little bit too
simple?
There is no notion of 'used' space in odp_buffer_t. It is a simple
memory block. All space is 'used'. I don't think there is a need for
something more complex.
What use-case do you have in mind?
Nothing special, just started to think because the DPDK relative of raw
buffers (control buffers) have this notion.
Zoli
_______________________________________________
lng-odp mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/lng-odp
