dp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of shally
>> verma
>> Sent: Friday, August 11, 2017 8:05 AM
>> To: Maxim Uvarov
>> Cc: Elo, Matias (Nokia - FI/Espoo) ; Petri Savolainen
>> ; lng-odp@lists.linaro.org
>> Subject: Re: [lng-odp] [EXT] Re: ODP1
Petri Savolainen
> ; lng-odp@lists.linaro.org
> Subject: Re: [lng-odp] [EXT] Re: ODP1.15 buffer alignment issue
>
> just to add for some implementation Buffer == data itself (without any
> metadata or headroom). So while you work on this, please get us
> clarity for such implementa
just to add for some implementation Buffer == data itself (without any
metadata or headroom). So while you work on this, please get us
clarity for such implementations as well.
On Fri, Aug 11, 2017 at 12:36 AM, Maxim Uvarov wrote:
> On 08/10/17 21:41, Liron Himi wrote:
>> Hi,
>>
>> I think it is
On 08/10/17 21:41, Liron Himi wrote:
> Hi,
>
> I think it is more than just naming replacement.
> The odp-pool API state that the alignment is for buffer alignment and not for
> data. So it seems like a bug, right?
>
> Here is a snipped from the API:
> /** Minimum buffer al
Hi,
I think it is more than just naming replacement.
The odp-pool API state that the alignment is for buffer alignment and not for
data. So it seems like a bug, right?
Here is a snipped from the API:
/** Minimum buffer alignment in bytes. Valid values are
