[dpdk-dev] rte_eal_init independent from main(int argc, char** argv)

Periklis Akritidis akritid at niometrics.com
Tue Feb 18 14:52:24 CET 2014

Hi Hamid,

I do something similar and works fine. My compiler warning flags are more pedantic, so I have to ensure those strings are not const literals, but that doesn’t matter.

I would appreciate an init that takes a struct with options too.

On 18 Feb, 2014, at 8:57 pm, Hamid Ramazani <mrramazani at gmail.com> wrote:

> actually I've used:
> char* argv[] = {"./build/l2fwd","-c","ff","-n","4", NULL};
> (NULL at the end of the list).
> Thanks.
> On 2/18/14, Hamid Ramazani <mrramazani at gmail.com> wrote:
>> Hi,
>> I'm in need of running an open() function, that is part another program.
>> open() does many things, the very first of them is rte_eal_init(argv, argc)
>> I should not receive argc, and argv from main function of the program,
>> but rather I should produce it myself.
>> What I've done inside open() function is:
>> int argc = 5;
>> char* argv[] = {"./build/l2fwd","-c","ff","-n","4"};
>> ret = rte_eal_init(argc,argv);
>> But I receive: invalid EAL arguments.
>> I'm thinking about writing another rte_eal_init function for myself.
>> What do you think?
>> Thanks in advance.

More information about the dev mailing list