ok. Can we do it in separate patch for l3fwd and l2fwd  together? Or I and
Forest have to update our patches.

Maxim.

On 11 August 2016 at 17:21, Mike Holmes <mike.hol...@linaro.org> wrote:

> We need to also add this to ~/git/odp/doc/application-api-guide/examples.dox
> so that it gets seen in the application users guide if we really want to
> get the maximum exposure to it.
>
> On 11 August 2016 at 10:09, Maxim Uvarov <maxim.uva...@linaro.org> wrote:
>
>> ping
>>
>>
>> On 07/22/16 14:05, Maxim Uvarov wrote:
>>
>>> odp_l2fwd is standalone application which can be used
>>> as example or as performance test. Hiding it inside
>>> performance tests might be not new users friendly way.
>>> Create symlink with small readme file for better finding
>>> it.
>>>
>>> Signed-off-by: Maxim Uvarov <maxim.uva...@linaro.org>
>>> ---
>>>   example/l2fwd/README      | 8 ++++++++
>>>   example/l2fwd/odp_l2fwd.c | 1 +
>>>   2 files changed, 9 insertions(+)
>>>   create mode 100644 example/l2fwd/README
>>>   create mode 120000 example/l2fwd/odp_l2fwd.c
>>>
>>> diff --git a/example/l2fwd/README b/example/l2fwd/README
>>> new file mode 100644
>>> index 0000000..891620b
>>> --- /dev/null
>>> +++ b/example/l2fwd/README
>>> @@ -0,0 +1,8 @@
>>> +    ODP L2FWD application
>>> +
>>> +Source code and Makefiles placed under test/common_plat/performance/
>>> +directory.
>>> +
>>> +This L2 forwarding application can be used as example reference as well
>>> +as performance test for different odp modes (direct, queue or scheduler
>>> +with parallel, atomic or ordered queues).
>>> diff --git a/example/l2fwd/odp_l2fwd.c b/example/l2fwd/odp_l2fwd.c
>>> new file mode 120000
>>> index 0000000..eea3a34
>>> --- /dev/null
>>> +++ b/example/l2fwd/odp_l2fwd.c
>>> @@ -0,0 +1 @@
>>> +../../test/common_plat/performance/odp_l2fwd.c
>>> \ No newline at end of file
>>>
>>
>>
>
>
> --
> Mike Holmes
> Technical Manager - Linaro Networking Group
> Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs
> "Work should be fun and collaborative, the rest follows"
>
>
>

Reply via email to