On 08/12/2014 05:21 PM, Ola Liljedahl wrote:
Are we discussing solutions before we have agreed on the problem?

+1 Lets discuss that on todays meeting. If there is time slot for that.

Maxim.

On 8 August 2014 01:52, Wiles, Roger Keith <[email protected] <mailto:[email protected]>> wrote:

    Hi Taras,

    Looks like this maybe a possible direction, but I feel adding some
    init support into ODP is a good thing.

    *Keith **Wiles*, Principal Technologist with CTO office, *Wind
    River*mobile 972-213-5533 <tel:972-213-5533>

    On Aug 7, 2014, at 3:08 PM, Taras Kondratiuk
    <[email protected] <mailto:[email protected]>>
    wrote:

    On 08/07/2014 10:36 PM, Wiles, Roger Keith wrote:

    *Keith **Wiles*, Principal Technologist with CTO office, *Wind
    River*
    mobile 972-213-5533 <tel:972-213-5533>
    On Aug 7, 2014, at 2:21 PM, Taras Kondratiuk
    <[email protected]
    <mailto:[email protected]>
    <mailto:[email protected]>> wrote:

    From implementation point it is not an issue to parse configuration
    strings, but it just feels wrong. The fact that DPDK does it
    doesn't
    mean it is a good approach.

    I'd prefer to pass generic parameters via structure to
    odp_init() and
    let implementation to figure out how to get other stuff if needed.
    In case of Linux-based implementations there are many ways to
    do it.

    I do understand, but DPDK is inited in this fashion and we would
    need to
    supply a argc/argv parameters to call its init routine. Now it
    is being
    done in the odp_init_dpdk() function and it can not support all
    of the
    args. We need to pass args to the SDK in some way and argc/argv
    is the
    best solution for DPDK. Now we can do as I suggested by adding
    ‘—sdk-args=“”’ to the command line or the odp_init_dpdk()
    routine will
    need to get the values some place. It just seems similar to add
    them to
    command line, even if ODP is not really launched from a command
    line.

    The first approach that comes to my mind is an environment variable.

    DPDK_CMD_LINE='some configs' odp_foobar

    then linux-dpdk can getevn('DPDK_CMD_LINE') and everybody happy.
    API is not changed and DPDK have its configuration.


    _______________________________________________
    lng-odp mailing list
    [email protected] <mailto:[email protected]>
    http://lists.linaro.org/mailman/listinfo/lng-odp




_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp


_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp

Reply via email to