- Move packets from the event instead of copying them. This simplifies
event handling/freeing code, which now does not have to track, which
packets were copied from the event and which packets should be freed.
- Do not require to free the event before processing packets. This
allows one
From: Dmitry Eremin-Solenikov
Soft limit expiration isn't an error per se. It does not mean, that we
received invalid or unprocessed packet. They look more like flags,
noting that soft limit on this SA was expired.
Signed-off-by: Dmitry Eremin-Solenikov
---
/** Email created from pull request 2
From: Dmitry Eremin-Solenikov
For INLINE-destined SAs it is typical to have packets processed through
INLINE API. So, let's invert the inline_mode flag to mean that the
packet was processed through ASYNC API.
Signed-off-by: Dmitry Eremin-Solenikov
---
/** Email created from pull request 22 (lum
From: Dmitry Eremin-Solenikov
An expectation would be that an application would check if there is any
exceptional status set by checking the all_status field and then further
descending on the reason on the particular exception.
Signed-off-by: Dmitry Eremin-Solenikov
---
/** Email created from
From: Dmitry Eremin-Solenikov
If outbound packet was processed in inline mode, soft limit expiration
event is not reported, as packet goes to the interface. Instead report
this as an ODP_IPSEC_STATUS_SA_SOFT_EXPIRED.
Signed-off-by: Dmitry Eremin-Solenikov
---
/** Email created from pull request
From: Dmitry Eremin-Solenikov
Add an explicit note telling that soft_exp bits are set only once, for
the packet actually crossing the boundary. They will not be set for
further packets.
Signed-off-by: Dmitry Eremin-Solenikov
---
/** Email created from pull request 22 (lumag:ipsec-limits)
** ht
The goal of this patchset is to fix small issues in IPsec limits support.
github
/** Email created from pull request 22 (lumag:ipsec-limits)
** https://github.com/Linaro/odp/pull/22
** Patch: https://github.com/Linaro/odp/pull/22.patch
** Base sha: 3ea9c1
Branch: refs/heads/api-next
Home: https://github.com/Linaro/odp
Commit: 3ea9c1dac34e0fb4785b0d643056c731daa55e85
https://github.com/Linaro/odp/commit/3ea9c1dac34e0fb4785b0d643056c731daa55e85
Author: Dmitry Eremin-Solenikov
Date: 2017-05-08 (Mon, 08 May 2017)
Changed paths:
On 05/05/2017 11:55 PM, Dmitry Eremin-Solenikov wrote:
On 05.05.2017 15:34, Petri Savolainen wrote:
Added maximum number of packets per result event to make it easy
for application to prepare enough storage for packets.
I'm still not sure that this is a good idea.
It will be good to get agree
On 05/05/2017 03:49 PM, Matias Elo wrote:
odp_shm_lookup() return value can be used to detect name conflicts.
Signed-off-by: Matias Elo
---
helper/hashtable.c | 3 +--
helper/lineartable.c | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/helper/hashtable.c b/helper/
In general I think that this patch is ok. It will be good to fix
following warning aslo:
WARNING: Missing a blank line after declarations
#39: FILE: platform/linux-generic/include/odp_crypto_internal.h:66:
+ uint32_t bytes;
+ const EVP_MD *evp_md;
total: 0 errors, 1
Hi, just to update you, I am using the TM example app (which I indeed works
fine, doing traffic prioritization) to find the exact setting missing in my
config. I will share my findings...
--
Oriol Arcas
Software Engineer
Starflow Networks
On Wed, May 3, 2017 at 3:35 PM, Bala Manoharan
wrote:
>
On Mon, May 8, 2017 at 4:55 AM Ola Liljedahl wrote:
>
>
> On 08/05/2017, 13:20, "Bill Fischofer" wrote:
>
> >On Sun, May 7, 2017 at 9:56 PM, Honnappa Nagarahalli
> > wrote:
> >> On 5 May 2017 at 21:46, Bill Fischofer
> >>wrote:
> >>> v5 still fails to compile on a 32-bit system using clang:
> >
13 matches
Mail list logo
