I was trying api-next from linaro/odp as of today and am seeing this
error. Am I missing anything here?
I simply use
./bootstrap
./configure
./make
make[2]: Entering directory
`/home/shrutika/zip/zip-linux/83xx/odp/odp/example/ipfragreass'
CC odp_ipfragreass-odp_ipfragreass.o
CC o
On Tue, Aug 29, 2017 at 10:41 PM, Dmitry Eremin-Solenikov
wrote:
> On 29/08/17 19:18, shally verma wrote:
>> Alongside a question of retrieving results for synchronous operations,
>> have one more questions - in crypto, I dont see separate output packet
>> data range. So, d
On Tue, Aug 29, 2017 at 6:06 PM, shally verma
wrote:
> On Tue, Aug 29, 2017 at 5:02 PM, Savolainen, Petri (Nokia - FI/Espoo)
> wrote:
>>
>>
>>> -Original Message-
>>> From: shally verma [mailto:shallyvermacav...@gmail.com]
>>> Sent: Tuesd
>
> From: Bill Fischofer [mailto:bill.fischo...@linaro.org]
> Sent: 03 August 2017 17:54
> To: shally verma
> Cc: Dmitry Eremin-Solenikov ; Challa,
> Mahipal ; lng-odp-forward
> ; Narayana, Prasad Athreya
> ; Verma, Shally
> ; Attunuru, Vamsi
> Subject: Re:
On Tue, Aug 29, 2017 at 5:02 PM, Savolainen, Petri (Nokia - FI/Espoo)
wrote:
>
>
>> -Original Message-----
>> From: shally verma [mailto:shallyvermacav...@gmail.com]
>> Sent: Tuesday, August 29, 2017 10:26 AM
>> To: Narayana Prasad Athreya
>> Cc:
Hi
In order to align to crypto, I was looking to latest spec regarding
Sub-event types here :
https://github.com/Linaro/odp/blob/api-next/include/odp/api/spec/event.h ,
where I cannot see reference to any sub-event type for crypto.
So could anyone confirm if crypto will be supporting only one e
one explain what is the use-case of #1 and why the use-case cannot
> be met with proposed API?
>
> PRasad
>
> On Tuesday 08 August 2017 10:21 PM, shally verma wrote:
>
> Petri/Berry
>
> As per discussion in today's call, this is what I summarize :
>
> T
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
Just a Resend.
On Tue, Aug 8, 2017 at 10:21 PM, shally verma
wrote:
> Petri/Berry
>
> As per discussion in today's call, this is what I summarize :
>
> Two new requirements added:
>
> 1. Support compression / decompression of multiple ranges with in one
> single
t: Friday, August 04, 2017 4:00 PM
>> To: lng-odp@lists.linaro.org
>> Subject: [lng-odp] [PATCH API-NEXT v8 1/1] comp: compression spec
>>
>> From: Shally Verma
>>
>> Signed-off-by: Shally Verma
>> Signed-off-by: Mahipal Challa Cc
>> prasada
On Wed, Aug 2, 2017 at 10:04 PM, shally verma
wrote:
> On Wed, Aug 2, 2017 at 6:03 PM, Dmitry Eremin-Solenikov
> wrote:
>> On 2 August 2017 at 15:18, shally verma wrote:
>>> On Wed, Aug 2, 2017 at 4:37 PM, Maxim Uvarov
>>> wrote:
>>>>
>>
On Wed, Aug 2, 2017 at 6:03 PM, Dmitry Eremin-Solenikov
wrote:
> On 2 August 2017 at 15:18, shally verma wrote:
>> On Wed, Aug 2, 2017 at 4:37 PM, Maxim Uvarov wrote:
>>>
>>>
>>> On 2 August 2017 at 14:05, Dmitry Eremin-Solenikov
>>> wrote:
&g
On Wed, Aug 2, 2017 at 4:37 PM, Maxim Uvarov wrote:
>
>
> On 2 August 2017 at 14:05, Dmitry Eremin-Solenikov
> wrote:
>>
>> On 02/08/17 13:56, shally verma wrote:
>> > On Wed, Aug 2, 2017 at 4:15 PM, Maxim Uvarov
>> > wrote:
>> >>
>> &
On Wed, Aug 2, 2017 at 4:15 PM, Maxim Uvarov wrote:
>
>
> On 2 August 2017 at 13:35, shally verma wrote:
>>
>> Hi
>>
>> Based on discussion in yesterday's odp public call, I was trying to
>> exercise github pull request feature for patch submission. Bu
Hi
Based on discussion in yesterday's odp public call, I was trying to
exercise github pull request feature for patch submission. But running
into some doubts.
-Should I create a pull request from a main odp.git repository like as
explained here
https://help.github.com/articles/creating-a-pull-r
utomatically if you use a GitHub pull request, but must be done
>> manually if you submit the patch via e-mail.
>>
>> Thanks.
>>
>> On Tue, Aug 1, 2017 at 2:38 AM, Vamsi Attunuru
>> wrote:
>>
>>> Signed-off-by: Vamsi Attunuru
>>> Signed
On Tue, Jul 25, 2017 at 5:02 PM, Bill Fischofer
wrote:
>
>
> On Mon, Jul 24, 2017 at 7:26 AM, shally verma
> wrote:
>>
>> On Mon, Jul 24, 2017 at 5:44 PM, Bill Fischofer
>> wrote:
>> > I should also point out that the pool min_seg_len does not mean tha
On Mon, Jul 24, 2017 at 5:55 PM, Dmitry Eremin-Solenikov
wrote:
> On 24/07/17 15:12, shally verma wrote:
>> On Mon, Jul 24, 2017 at 5:27 PM, Dmitry Eremin-Solenikov
>> wrote:
>>> On 24/07/17 14:11, shally verma wrote:
>>>> On Tue, Jul 11, 2017 at 7:30 P
>>
>> If pool_capa.max_seg_len < pool_param.pkt.len then that's an indication
>> that such packets will be segmented in this implementation. The
>> odp_packet_num_seg() API will tell you how many segments are contained in a
>> given odp_packet_t and this is th
On Mon, Jul 24, 2017 at 5:27 PM, Dmitry Eremin-Solenikov
wrote:
> On 24/07/17 14:11, shally verma wrote:
>> On Tue, Jul 11, 2017 at 7:30 PM, Github ODP bot wrote:
>>> From: Dmitry Eremin-Solenikov
>
>>> @@ -311,16 +315,15 @@ typedef struct odp_crypto_session_param
Resending.
On Mon, Jul 24, 2017 at 5:01 PM, shally verma
wrote:
> Have a question regarding packet pool creation and params. As it says in
> pool.h
>
> len = minimum length of pakcet
> seg_len = minimum length of 1st segment to hold packet data bytes
>
> Since it says minim
Have a question regarding packet pool creation and params. As it says in pool.h
len = minimum length of pakcet
seg_len = minimum length of 1st segment to hold packet data bytes
Since it says minimum, so actual segment size used to hold packet data
size may be more than this.
So if I want to crea
On Tue, Jul 11, 2017 at 7:30 PM, Github ODP bot wrote:
> From: Dmitry Eremin-Solenikov
>
> Input and output of crypto operations are packets. API is more flexible
> for application and API pipelining when output is packet with additional
> metadata. Application or API pipeline stages which do not
On Fri, Jul 14, 2017 at 6:06 PM, Bill Fischofer
wrote:
>
>
> On Fri, Jul 14, 2017 at 6:55 AM, shally verma
> wrote:
>>
>> On Thu, Jul 13, 2017 at 2:17 PM, Savolainen, Petri (Nokia - FI/Espoo)
>> wrote:
>> >
>> >
>> >> -Original
On Thu, Jul 13, 2017 at 2:17 PM, Savolainen, Petri (Nokia - FI/Espoo)
wrote:
>
>
>> -Original Message-----
>> From: shally verma [mailto:shallyvermacav...@gmail.com]
>> Sent: Thursday, July 13, 2017 11:43 AM
>> To: Savolainen, Petri (Nokia - FI/Espoo)
>>
On Thu, Jul 13, 2017 at 2:05 PM, Savolainen, Petri (Nokia - FI/Espoo)
wrote:
>
>
>> -Original Message-
>> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of
>> shally verma
>> Sent: Wednesday, July 12, 2017 3:36 PM
>> To: lng-odp-f
On Wed, Jul 12, 2017 at 10:59 PM, Bill Fischofer
wrote:
> On Wed, Jul 12, 2017 at 11:16 AM, shally verma
> wrote:
>> On Wed, Jul 12, 2017 at 8:50 PM, Bill Fischofer
>> wrote:
>>> On Wed, Jul 12, 2017 at 7:35 AM, shally verma
>>> wrote:
>>>> I hav
Ok. That clarifies my doubt. Only concern was we shouldn't end up
misusing directive.
Thanks for inputs.
Shally
On Wed, Jul 12, 2017 at 11:16 PM, Bill Fischofer
wrote:
> On Wed, Jul 12, 2017 at 10:33 AM, shally verma
> wrote:
>> On Wed, Jul 12, 2017 at 8:37 PM, Bill Fi
On Wed, Jul 12, 2017 at 8:50 PM, Bill Fischofer
wrote:
> On Wed, Jul 12, 2017 at 7:35 AM, shally verma
> wrote:
>> I have a question on odp_pktin_recv(odp_pktin_queue_t, odp_packet_t [], int).
>>
>> Once app receives packets associated to the queue, what happens to
>
enario?
>Also, do you envision this to be a temporary or permanent restriction?
Right now, I added this as temporary fix. But my question is in
general for any unsupported feature how an corresponding API should
deal with unused params.
Thanks
Shally
>
> On Wed, Jul 12, 2017 at 7:47
Hi
If any implementation does not support specific mode of operation ,
say , it only support sync but not async then is it legal to mark
async API params as ODP_UNUSED? As in such case API may simply return
with failure code, thus references to params is not actually exercised
which results in to
I have a question on odp_pktin_recv(odp_pktin_queue_t, odp_packet_t [], int).
Once app receives packets associated to the queue, what happens to
packets buffers passed to application? Does implementation always
assume that packets will be freed by caller and re-allocates fresh
packets to queue?
I
On Thu, Jun 29, 2017 at 4:18 AM, Dmitry Eremin-Solenikov
wrote:
> Input and output of crypto operations are packets. API is more flexible
> for application and API pipelining when output is packet with additional
> metadata. Application or API pipeline stages which do not care about
> crypto resul
I have question on definition of this macro ODP_PKTIO_MACADDR_MAXSIZE
. In pktio,h it is mentioned as " Minimum size of output buffer for
odp_pktio_mac_addr()" where as Macro name is MAXSIZE.
In linux-generic implementation this value is set to 16.
So how to interpret it? Does it mean user need
On Tue, Jun 27, 2017 at 2:51 PM, Savolainen, Petri (Nokia - FI/Espoo)
wrote:
>> > diff --git a/platform/linux-generic/include/odp/api/plat/event_types.h
>> b/platform/linux-generic/include/odp/api/plat/event_types.h
>> > index 0f51783..adf2c31 100644
>> > --- a/platform/linux-generic/include/odp/a
Ping. Reminder to review.
Thanks
Shally
On Tue, Jun 20, 2017 at 5:05 PM, Shally Verma
wrote:
> API patch to enable compression/decompression support in ODP
>
> Changes from RFC v3:
> Added separate function for compression and decompression.
> Added separate event ODP_E
On Thu, Jun 22, 2017 at 3:03 AM, Honnappa Nagarahalli
wrote:
> Why is it Hard? It is a matter of documenting/advertising which
> versions we are using in CI and making that as a minimum standard. If
> someone has a different compiler they can always submit the patches
> for their compilers.
>
I se
-by: Shally Verma
Signed-off-by: Mahipal Challa
---
include/odp/api/spec/comp.h| 810 +
include/odp/api/spec/event.h | 3 +-
include/odp/arch/arm32-linux/odp/api/abi/comp.h| 7 +
include/odp/arch/arm64-linux/odp/api/abi
Shally Verma (1):
comp: compression API
Changes from RFC v3:
Add separate function for compresion/decompression
Add separate events ODP_EVENT_COMP_COMPL for compression and
ODP_EVENT_DECOMP_COMPL decompression completion notification.
include/odp/api/spec/comp.h
On Tue, Jun 20, 2017 at 3:12 PM, Savolainen, Petri (Nokia - FI/Espoo)
wrote:
>
>
>> -Original Message-----
>> From: shally verma [mailto:shallyvermacav...@gmail.com]
>> Sent: Tuesday, June 20, 2017 8:55 AM
>> To: Bill Fischofer
>> Cc: Savolainen, Petri (No
On Fri, Jun 16, 2017 at 7:15 PM, Bill Fischofer
wrote:
> On Fri, Jun 16, 2017 at 8:33 AM, shally verma
> wrote:
>> On Fri, Jun 16, 2017 at 6:42 PM, Bill Fischofer
>> wrote:
>>> On Fri, Jun 16, 2017 at 8:04 AM, Savolainen, Petri (Nokia - FI/Espoo)
>>> wrote:
On Fri, Jun 16, 2017 at 6:42 PM, Bill Fischofer
wrote:
> On Fri, Jun 16, 2017 at 8:04 AM, Savolainen, Petri (Nokia - FI/Espoo)
> wrote:
>>> > diff --git a/include/odp/api/spec/event.h b/include/odp/api/spec/event.h
>>> > index f22efce5..2ad3ce84 100644
>>> > --- a/include/odp/api/spec/event.h
>>>
Does it mean that going further there would be certain limitation on
gcc version to be used? I just tried to compile next branch and
./configure throws an error
./configure: line 22786: syntax error near unexpected token
`-Wimplicit-fallthrough=0,'
./configure: line 22786: `AX_CHECK_COMPILE_FLAG(-
Do we have any more comments on same?
Petri
Could you get time to review feedback?
Can we consider v3 as accepted?
Thanks
Shally
On Thu, Jun 1, 2017 at 10:05 PM, shally verma
wrote:
> Re-sending with updated comments.
>
> Regards
> Shally
>
> On Thu, Jun 1, 2017 at 7:58
Re-sending with updated comments.
Regards
Shally
On Thu, Jun 1, 2017 at 7:58 PM, Verma, Shally
wrote:
> Regards
> Shally
>
> -Original Message-
> From: Savolainen, Petri (Nokia - FI/Espoo) [mailto:petri.savolainen@
> nokia.com]
> Sent: 01 June 2017 18:20
> To
Reminder.
Could we please have acceptance criteria on same.
Thanks
Shally
On Mon, May 22, 2017 at 12:24 PM, Shally Verma
wrote:
> Signed-off-by: Shally Verma
> Signed-off-by: Mahipal Challa
> ---
> include/odp/api/spec/comp.h | 740 ++
> +
Signed-off-by: Shally Verma
Signed-off-by: Mahipal Challa
---
include/odp/api/spec/comp.h | 740
1 file changed, 740 insertions(+)
diff --git a/include/odp/api/spec/comp.h b/include/odp/api/spec/comp.h
new file mode 100644
index 000..6c13ad4
reference odp_packet_data_range_t for accessing packet buffer
Shally Verma (1):
comp: compression interface
include/odp/api/spec/comp.h | 740
1 file changed, 740 insertions(+)
create mode 100644 include/odp/api/spec/comp.h
--
1.9.1
An API set to add compression/decompression support in ODP
interface.
Signed-off-by: Shally Verma
Signed-off-by: Mahipal Challa
---
include/odp/api/spec/comp.h | 748
1 file changed, 748 insertions(+)
diff --git a/include/odp/api/spec/comp.h b
capability struct
Shally Verma (1):
odp compression interface api set
include/odp/api/spec/comp.h | 748
1 file changed, 748 insertions(+)
create mode 100644 include/odp/api/spec/comp.h
--
1.9.1
50 matches
Mail list logo
