DPDK usage discussions
 help / color / mirror / Atom feed
From: Monika Mails <mails.monika@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Fwd: rte_mempool_create( ) fails at rte_mempool_set_ops_byname () for name ring_mp_mc
Date: Fri, 8 Jun 2018 09:04:58 -0700	[thread overview]
Message-ID: <CALPXby9kG-R=sP5DXBnXdKbCw6YwRaZMB+q+_cvaMQLwRxkp_g@mail.gmail.com> (raw)
In-Reply-To: <CALPXby-2VOF9EjrVh1-=6YyVW=JM=u0_jHNaUoz8S=y0WhQmLw@mail.gmail.com>

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

       reply	other threads:[~2018-06-08 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALPXby-2VOF9EjrVh1-=6YyVW=JM=u0_jHNaUoz8S=y0WhQmLw@mail.gmail.com>
2018-06-08 16:04 ` Monika Mails [this message]
     [not found] ` <CALPXby_kc7LXxV0YxNuyLwf8sCGquK7GkgR++am9n+mh6dqawg@mail.gmail.com>
2018-06-08 16:05   ` Monika Mails

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALPXby9kG-R=sP5DXBnXdKbCw6YwRaZMB+q+_cvaMQLwRxkp_g@mail.gmail.com' \
    --to=mails.monika@gmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).