On 05/19/2015 00:30, Ola Liljedahl wrote:
On 18 May 2015 at 20:36, Li, Charlie charlie...@amd.com
mailto:charlie...@amd.com wrote:
Hi Maxim,
I have tried linux-generic and odp_l2fwd worked.
But when I tried netmap
(https://git.linaro.org/lng/odp-netmap.git), I got the
Hi Steve,
please find comments inline.
Alex
On 19 May 2015 at 04:13, Steve Kordus (skordus) skor...@cisco.com wrote:
Sorry it took so long.
I just have a couple of questions/comments (see the SRK imbedded in
the diffs below), otherwise it looked fine to me.
Steve
-Original
Suggested-by: Maxim Uvarov maxim.uva...@linaro.org
Signed-off-by: Nicolas Morey-Chaisemartin nmo...@kalray.eu
---
platform/Makefile.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/platform/Makefile.inc b/platform/Makefile.inc
index f232daa..f64e37c 100644
---
On 19 May 2015 at 03:53, Bill Fischofer bill.fischo...@linaro.org wrote:
See comments inline. In general I like this, as it does seem clean and
minimal.
On Mon, May 18, 2015 at 5:03 PM, Ola Liljedahl ola.liljed...@linaro.org
wrote:
As promised, here is my first attempt at a standalone API
Signed-off-by: Nicolas Morey-Chaisemartin nmo...@kalray.eu
---
Note: the new checkpatch does not seem to be happy with PRIu32 put this way
(CamelCase and no space in concatenated strings) but I kept it homogeneous with
the other printfs
test/validation/odp_packet.c | 3 ++-
1 file changed, 2
From: Alexandru Badicioiu alexandru.badici...@linaro.org
v1 - added comment for tunnel DB entry use
Tunnel mode is enabled from the command line using -t argument with
the following format: SrcIP:DstIP:TunnelSrcIP:TunnelDstIP.
SrcIP - cleartext packet source IP
DstIP - cleartext packet
I ran into the same issue on our side and after a quick look, this is kind of
expected.
By setting a period to a time duration smaller than the resolution, the
probability is very high that this would happen
Example:
Get tick = N
Time out = Tick + Period = N + 0 = N
== New tick ==
On 19 May 2015 at 11:43, Nicolas Morey-Chaisemartin nmo...@kalray.eu
wrote:
I ran into the same issue on our side and after a quick look, this is
kind of expected.
By setting a period to a time duration smaller than the resolution, the
probability is very high that this would happen
Yes
https://bugs.linaro.org/show_bug.cgi?id=1449
--- Comment #4 from Ola Liljedahl ola.liljed...@linaro.org ---
I see now that the reason for the abort and core dump is that the timeout
period is smaller than the tick (the resolution of the timer). This does not
make sense and is also not supported
https://bugs.linaro.org/show_bug.cgi?id=1449
--- Comment #5 from Ola Liljedahl ola.liljed...@linaro.org ---
I am testing with periods 1x-2x the length of the timer resolution and still
get intermittent too early failures. I assume this is caused by the
non-determinism of Linux, the ODP threads
From: Alexandru Badicioiu alexandru.badici...@linaro.org
Signed-off-by: Alexandru Badicioiu alexandru.badici...@linaro.org
Signed-off-by: Maxim Uvarov maxim.uva...@linaro.org
---
v2: fix csum in odp generatior.
example/generator/odp_generator.c | 2 +-
helper/include/odp/helper/udp.h | 37
Actually those printf() calls are vestigial from debugging and should be
removed. They were not intended to be part of the final tests.
On Tue, May 19, 2015 at 3:32 AM, Nicolas Morey-Chaisemartin
nmo...@kalray.eu wrote:
Signed-off-by: Nicolas Morey-Chaisemartin nmo...@kalray.eu
---
Note:
On Wed, May 20, 2015 at 12:25:12AM +0200, Ola Liljedahl wrote:
On 19 May 2015 at 15:34, Jacob, Jerin jerin.ja...@caviumnetworks.com wrote:
Ola,
Is there any specific reason for following check in timer validation test ?
pa
diff --git a/test/validation/odp_timer.c
Ola,
Is there any specific reason for following check in timer validation test ?
diff --git a/test/validation/odp_timer.c b/test/validation/odp_timer.c
index 554b353..724026e 100644
--- a/test/validation/odp_timer.c
+++ b/test/validation/odp_timer.c
@@ -260,7 +260,7 @@ static void
On Tue, May 19, 2015 at 1:03 AM, Ola Liljedahl ola.liljed...@linaro.org wrote:
As promised, here is my first attempt at a standalone API for IPC - inter
process communication in a shared nothing architecture (message passing
between processes which do not share memory).
Currently all
On 19 May 2015 at 16:19, Ciprian Barbu ciprian.ba...@linaro.org wrote:
On Tue, May 19, 2015 at 1:03 AM, Ola Liljedahl ola.liljed...@linaro.org
wrote:
As promised, here is my first attempt at a standalone API for IPC - inter
process communication in a shared nothing architecture (message
UberConference Reminder___
lng-odp mailing list
lng-odp@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lng-odp
Hi all,
Your conference is about to begin!
Weekly ODP Design Discussion Call
May 19, 2015 at 8:00AM MST
Just to be sure, the conference is canceled this week, right?
Thanks,
ben
___
lng-odp mailing list
lng-odp@lists.linaro.org
It seems like there is still a discussion floating on patch 2, about
including helper code in the linux-generic implementation. I will have
a look at the other patches, but I think you need to solve the issue
with the ring code before marking the patchset as ready to be merged.
On Mon, May 18,
On 2015-05-07 18:09, Mike Holmes wrote:
On 5 May 2015 at 12:31, Christophe Milard christophe.mil...@linaro.org
wrote:
This is the one I'd like to be reviewed... (v2) sorry for the confusion.
On 27 April 2015 at 17:54, Christophe Milard christophe.mil...@linaro.org
wrote:
The 3
Hi Ola,
Thanks for sharing this. We are also looking at IPC at Kalray, where our
ODP model is multi-process, shared-nothing, architecture.
From our point of view, the main requirements for IPC would be:
- use it to communicate between different address spaces (AS), and as
such our messages
On 19 May 2015 at 15:34, Jacob, Jerin jerin.ja...@caviumnetworks.com wrote:
Ola,
Is there any specific reason for following check in timer validation test ?
pa
diff --git a/test/validation/odp_timer.c b/test/validation/odp_timer.c
index 554b353..724026e 100644
---
On 19 May 2015 at 19:04, Benoît Ganne bga...@kalray.eu wrote:
Hi Ola,
Thanks for sharing this. We are also looking at IPC at Kalray, where our ODP
model is multi-process, shared-nothing, architecture.
From our point of view, the main requirements for IPC would be:
- use it to communicate
23 matches
Mail list logo
