From: Sindhura Bandi <sindhura.bandi@certesnetworks.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: How to enable logging and where to find the logs
Date: Thu, 22 Feb 2024 01:21:32 +0000 [thread overview]
Message-ID: <DM5PR2201MB149814656A7BD41247F6CF90FE562@DM5PR2201MB1498.namprd22.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
Hi Everyone,
I might be asking a basic question here. I'm facing some issues while bringing up a dpdk interface on ovs-dpdk on debian-12. Dpdk version is 22.11.1.
Dpdk seems to fail to allocate a mempool, even though there seem to be enough free huge page memory available on the machine.
I tried to enable dpdk debugs using the following command,
ovs-vsctl set Open_vSwitch . other_config:dpdk-extra="--log-level=lib.mbuf:debug"
The command was accepted, but I don't see any logs from dpdk anywhere in my /var/log.
I get the following information from ovs logs.
Feb 22 01:03:42 cep ovs-vswitchd[108468]: ovs|00237|netdev_dpdk|ERR|Failed to create mempool "ovs013337e900021580020512" with a request of 20512 mbufs
Feb 22 01:03:42 cep ovs-vswitchd[108468]: ovs|00238|netdev_dpdk|ERR|Failed to create memory pool for netdev vhost-user0, with MTU 1500 on socket 0: No such file or directory
Feb 22 01:03:42 cep ovs-vswitchd[108468]: ovs|00239|dpif_netdev|ERR|Failed to set interface vhost-user0 new configuration
Checked ovs code, and its callingvrte_pktmbuf_pool_create(), which is failing with "No such file or directory". I would like to enable debugs for lib.mbuf.
Please let me know if I'm missing anything.
Thanks,
Sindhu
[-- Attachment #2: Type: text/html, Size: 5374 bytes --]
next reply other threads:[~2024-02-29 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 1:21 Sindhura Bandi [this message]
2024-02-29 11:11 ` Tummala, Sivaprasad
2024-02-29 11:26 ` David Marchand
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=DM5PR2201MB149814656A7BD41247F6CF90FE562@DM5PR2201MB1498.namprd22.prod.outlook.com \
--to=sindhura.bandi@certesnetworks.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).