Re: [lng-odp] Planning for 2.0 work items

[Honnappa Nagarahalli]

On 5 December 2017 at 09:03, Yi He  wrote:
> Hi, Honnappa
>
> We've talked about these goals in today's 2.0 call, here has some
> discussions and comments:
>
> 1, for net-mdev, Ilias suggested that upstreaming to Linux kernel will take
> very long time, we'd better define the net-mdev goal around demo
> definitions.
I do not have any issue with this. Upstreaming to Linux Kernel is not
a dependency for ODP for now, but the upstreaming to Linux Kernel has
to happen. Francois, how would you like to handle this? Is this our
responsibility? Should we make plans for this within ODP's scope?
Would it be taken up by LEG?

> 2, for performance benchmarking and directory structure goals, we need some
> clarifications and narrow the scope to some parts of ODP.
I will add it to Thursday's call.

>
> Please add this into Thursday's call to continue the discussion.
>
> Thanks and best regards, Yi
>
> On 5 December 2017 at 13:19, Honnappa Nagarahalli
>  wrote:
>>
>> Hi,
>>As discussed in the ODP 2.0 call (11/30/2017), we identified the
>> following areas of work. The idea is to have few demos with net-mdev
>> and user-space drivers for HKG18. The goal is to have all this
>> upstreamed by HKG18. I have mentioned a partial list of owners, please
>> feel free to add yourself to the list. Can the respective owners get
>> with Darcy, identify the scope and work items.
>>
>> 1) Upstreaming net-mdev (Ilias, Mykyta, Francois)
>>
>> a) Upstreaming to ODP 2.0
>>
>> b) Upstreaming to Linux Kernel
>>
>> 2) Performance benchmarking (need owners)
>>
>> a) Need to have a framework which allows for instrumenting
>> the code and logging the time stamp. This will allow for identifying
>> the number of cycles spent in various parts of the code. Need to
>> identify tools that can be used to plot the collected data.
>>
>>b) Need to have a benchmarking application which runs
>> packets through the typical path with dummy packet I/O - could be run
>> on any machine - loopback pkt I/O could be used.
>>
>> 3) Directory structure
>>
>>   a) Changes required to provide clarity of design.
>>
>> 4) Upstream user space drivers (Jianbo, Yi, Josep)
>>
>> Please let me know if you have any questions.
>>
>> Thank you,
>> Honnappa
>
>

Re: [lng-odp] Planning for 2.0 work items

[Yi He]

Hi, Honnappa

We've talked about these goals in today's 2.0 call, here has some
discussions and comments:

1, for net-mdev, Ilias suggested that upstreaming to Linux kernel will take
very long time, we'd better define the net-mdev goal around demo
definitions.
2, for performance benchmarking and directory structure goals, we need some
clarifications and narrow the scope to some parts of ODP.

Please add this into Thursday's call to continue the discussion.

Thanks and best regards, Yi

On 5 December 2017 at 13:19, Honnappa Nagarahalli <
honnappa.nagaraha...@linaro.org> wrote:

> Hi,
>As discussed in the ODP 2.0 call (11/30/2017), we identified the
> following areas of work. The idea is to have few demos with net-mdev
> and user-space drivers for HKG18. The goal is to have all this
> upstreamed by HKG18. I have mentioned a partial list of owners, please
> feel free to add yourself to the list. Can the respective owners get
> with Darcy, identify the scope and work items.
>
> 1) Upstreaming net-mdev (Ilias, Mykyta, Francois)
>
> a) Upstreaming to ODP 2.0
>
> b) Upstreaming to Linux Kernel
>
> 2) Performance benchmarking (need owners)
>
> a) Need to have a framework which allows for instrumenting
> the code and logging the time stamp. This will allow for identifying
> the number of cycles spent in various parts of the code. Need to
> identify tools that can be used to plot the collected data.
>
>b) Need to have a benchmarking application which runs
> packets through the typical path with dummy packet I/O - could be run
> on any machine - loopback pkt I/O could be used.
>
> 3) Directory structure
>
>   a) Changes required to provide clarity of design.
>
> 4) Upstream user space drivers (Jianbo, Yi, Josep)
>
> Please let me know if you have any questions.
>
> Thank you,
> Honnappa
>

[lng-odp] Planning for 2.0 work items

[Honnappa Nagarahalli]

Hi,
   As discussed in the ODP 2.0 call (11/30/2017), we identified the
following areas of work. The idea is to have few demos with net-mdev
and user-space drivers for HKG18. The goal is to have all this
upstreamed by HKG18. I have mentioned a partial list of owners, please
feel free to add yourself to the list. Can the respective owners get
with Darcy, identify the scope and work items.

1) Upstreaming net-mdev (Ilias, Mykyta, Francois)

a) Upstreaming to ODP 2.0

b) Upstreaming to Linux Kernel

2) Performance benchmarking (need owners)

a) Need to have a framework which allows for instrumenting
the code and logging the time stamp. This will allow for identifying
the number of cycles spent in various parts of the code. Need to
identify tools that can be used to plot the collected data.

   b) Need to have a benchmarking application which runs
packets through the typical path with dummy packet I/O - could be run
on any machine - loopback pkt I/O could be used.

3) Directory structure

  a) Changes required to provide clarity of design.

4) Upstream user space drivers (Jianbo, Yi, Josep)

Please let me know if you have any questions.

Thank you,
Honnappa