[dpdk-users] Fwd: rte_mempool_create( ) fails at rte_mempool_set_ops_byname () for name ring_mp_mc

Monika Mails mails.monika at gmail.com
Fri Jun 8 18:05:46 CEST 2018


Hi All,

I further checked the return error number from rte_mempool_create( ) it is
returning value 2 which means I guess "Missing rte_config"

Error types
*Enumerator: *
*RTE_MIN_ERRNO*

Start numbering above std errno vals
*E_RTE_SECONDARY*

Operation not allowed in secondary processes
*E_RTE_NO_CONFIG*

Missing rte_config <http://dpdk.org/doc/api/structrte__config.html>
*RTE_MAX_ERRNO*

Max RTE error number

Can someone please tell me how to fix this error?

Regards,
Monika


On Wed, Jun 6, 2018 at 2:50 PM, Monika Mails <mails.monika at gmail.com> wrote:

> Hi All,
>
> I am running DPDK version 18.05
>
> While running the binaries I see DPDK is failing in initialization, I
> checked after putting some logs and found that it is failing at
> API  *rte_mempool_set_ops_byname* () when it tries to read and compare
> rte_mempool_ops_table, highlighted below.
>
>
> /* sets mempool ops previously registered by rte_mempool_register_ops. */
> int
> rte_mempool_set_ops_byname(struct rte_mempool *mp, const char *name,
>         void *pool_config)
> {
>         struct rte_mempool_ops *ops = NULL;
>         unsigned i;
>            /* too late, the mempool is already populated.
> */rte_mempool_ops_table
>         if (mp->flags & MEMPOOL_F_POOL_CREATED)
>                 return -EEXIST;
>
>
>
>
>
>
>
> *       for (i = 0; i < rte_mempool_ops_table.num_ops; i++)
> {                if (!strcmp(name,
> rte_mempool_ops_table.ops[i].name)) {                        ops =
> &rte_mempool_ops_table.ops[i];                        break;
> }        }*
>
>         if (ops == NULL)
>                 return -EINVAL;
>         mp->ops_index = i;
>         mp->pool_config = pool_config;
>         return 0;
> }
>
> Can someone from Dev team please explain what is wrong here , why
> *rte_mempool_ops_table* is not initialized before using it.
>
> Here are the logs for DPDK run :-
>
> 1528317826.271857934 CoordinatorMain.cc:96 in main NOTICE[1]: Command
> line: /home/homa/platformlab/RAMCloud/obj.05302018_dpdk/coordinator -C
> basic+udp:host=10.10.10.14,port=12246 -l NOTICE --logFile
> logs/20180606154345/coordinator.homa4.log --dpdkPort 0 --configDir config
> 1528317826.271878426 CoordinatorMain.cc:97 in main NOTICE[1]: Coordinator
> process id: 4426
> 1528317826.271935304 DpdkDriver.cc:146 in DpdkDriver NOTICE[1]: Using DPDK
> version DPDK 18.05.0
> 1528317826.274933336 FileLogger.cc:100 in write NOTICE[1]: DPDK: EAL:
> Detected 32 lcore(s)
> 1528317826.274950808 FileLogger.cc:100 in write NOTICE[1]: DPDK: EAL:
> Detected 4 NUMA nodes
> 1528317826.275127489 FileLogger.cc:100 in write NOTICE[1]: DPDK: EAL:
> Multi-process socket /var/run/dpdk/homa4/mp_socket
> 1528317826.276794732 FileLogger.cc:100 in write NOTICE[1]: DPDK: EAL:
> Probing VFIO support...
> 1528317826.276839798 FileLogger.cc:100 in write NOTICE[1]: DPDK: EAL: VFIO
> support initialized
> 1528317826.630989301 CoordinatorMain.cc:153 in main ERROR[1]: Fatal error
> in coordinator at ???: RAMCloud::DriverException: Failed to allocate memory
> for packet buffers: No such file or directory, thrown at DpdkDriver at
> src/DpdkDriver.cc:172
>
> Regards,
> Monika
>
>


More information about the users mailing list