Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

Ola Liljedahl [mailto:ola.liljed...@linaro.org] wrote: > > On 10 April 2017 at 10:56, Peltonen, Janne (Nokia - FI/Espoo) > wrote: > > Hi, > > > > Ola Liljedahl wrote: > >> Peltonen, Janne (Nokia - FI/Espoo)

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

On 10 April 2017 at 10:56, Peltonen, Janne (Nokia - FI/Espoo) wrote: > Hi, > > Ola Liljedahl wrote: >> Peltonen, Janne (Nokia - FI/Espoo) wrote: >> > In an IPsec GW (as a use case example) one might want

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

Hi, Ola Liljedahl wrote: > Peltonen, Janne (Nokia - FI/Espoo) wrote: > > In an IPsec GW (as a use case example) one might want to do all > > stateless processing (like ingress and egress IP processing and the > > crypto

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

On 7 April 2017 at 08:40, Peltonen, Janne (Nokia - FI/Espoo) < janne.pelto...@nokia.com> wrote: > Hi, > > On Thu, Apr 6, 2017 at 1:46 PM, Bill Fischofer > wrote: > > On Thu, Apr 6, 2017 at 1:32 PM, Ola Liljedahl > wrote: > > > On 6 April 2017

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

I forget to note that it will be great to update .travis file for testing new option. Maxim. On 04/04/17 21:47, Brian Brooks wrote: > This work derives from Ola Liljedahl's prototype [1] which introduced a > scalable scheduler design based on primarily lock-free algorithms and > data structures

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

Hi, On Thu, Apr 6, 2017 at 1:46 PM, Bill Fischofer wrote: > On Thu, Apr 6, 2017 at 1:32 PM, Ola Liljedahl > wrote: > > On 6 April 2017 at 13:48, Jerin Jacob > > wrote: > >> We see ORDERED->ATOMIC as main

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

Original Message- >>>> Date: Thu, 6 Apr 2017 12:54:10 +0200 >>>> From: Ola Liljedahl <ola.liljed...@linaro.org> >>>> To: Brian Brooks <brian.bro...@arm.com> >>>> Cc: Jerin Jacob <jerin.ja...@caviumnetworks.com>, >>>> &

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

lt;ola.liljed...@linaro.org> >>> To: Brian Brooks <brian.bro...@arm.com> >>> Cc: Jerin Jacob <jerin.ja...@caviumnetworks.com>, >>> "lng-odp@lists.linaro.org" <lng-odp@lists.linaro.org> >>> Subject: Re: [lng-odp] [API-NEXT PATCH v2 0

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

: Jerin Jacob <jerin.ja...@caviumnetworks.com>, >> "lng-odp@lists.linaro.org" <lng-odp@lists.linaro.org> >> Subject: Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software >> scheduler >> >> On 5 April 2017 at 18:50, Brian Brooks <

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

ists.linaro.org> > Subject: Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software > scheduler > > On 5 April 2017 at 18:50, Brian Brooks <brian.bro...@arm.com> wrote: > > On 04/05 21:27:37, Jerin Jacob wrote: > >> -Original Message- > >

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

On 5 April 2017 at 18:50, Brian Brooks wrote: > On 04/05 21:27:37, Jerin Jacob wrote: >> -Original Message- >> > Date: Tue, 4 Apr 2017 13:47:52 -0500 >> > From: Brian Brooks >> > To: lng-odp@lists.linaro.org >> > Subject: [lng-odp] [API-NEXT

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

On 04/05 21:27:37, Jerin Jacob wrote: > -Original Message- > > Date: Tue, 4 Apr 2017 13:47:52 -0500 > > From: Brian Brooks > > To: lng-odp@lists.linaro.org > > Subject: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler > > X-Mailer: git-send-email

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

-Original Message- > Date: Tue, 4 Apr 2017 13:47:52 -0500 > From: Brian Brooks > To: lng-odp@lists.linaro.org > Subject: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler > X-Mailer: git-send-email 2.12.2 > > This work derives from Ola Liljedahl's

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

_fdserver.c: #define FDSERVER_MAX_ENTRIES 256 /* store the file descriptor in table: */ if (fd_table_nb_entries < FDSERVER_MAX_ENTRIES) { } else { ODP_ERR("FD table full\n"); Weird that you get this but not we. It is

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

Environment is Ubuntu 16.10. On Wed, Apr 5, 2017 at 7:03 AM, Bill Fischofer wrote: > This is running on my desktop x86: > > ./bootstrap > ./configure --enable-schedule-scalable --enable-cunit-support > make > cd test/common_plat/validation/api/scheduler >

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

This is running on my desktop x86: ./bootstrap ./configure --enable-schedule-scalable --enable-cunit-support make cd test/common_plat/validation/api/scheduler ./scheduler_main On Tue, Apr 4, 2017 at 10:24 PM, Honnappa Nagarahalli wrote: > On 4 April 2017 at

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

On 4 April 2017 at 16:12, Bill Fischofer wrote: > When I compile configure this without --enable-schedule-scalable the > scheduler validation test runs normally, however if I enable the new > scheduler I get this output: > > > ... > CUnit - A unit testing framework

Re: [lng-odp] [API-NEXT PATCH v2 00/16] A scalable software scheduler

When I compile configure this without --enable-schedule-scalable the scheduler validation test runs normally, however if I enable the new scheduler I get this output: ... CUnit - A unit testing framework for C - Version 2.1-3 http://cunit.sourceforge.net/