From: "Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
To: Sindhura Bandi <sindhura.bandi@certesnetworks.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: RE: How to enable logging and where to find the logs
Date: Thu, 29 Feb 2024 11:11:05 +0000 [thread overview]
Message-ID: <CH3PR12MB8233A3BE5197B903103AB25A865F2@CH3PR12MB8233.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM5PR2201MB149814656A7BD41247F6CF90FE562@DM5PR2201MB1498.namprd22.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2624 bytes --]
[AMD Official Use Only - General]
Hi Sindhu,
You can try enabling the dpdk logging with:
ovs-appctl vlog/set file:dpdk:dbg
DPDK logs should be in ovs-vswitchd log itself as indicated below.
2024-02-29T11:02:54.327Z|00115|dpif_netdev|INFO|Core 10 on numa node 0 assigned port 'dpdk0' rx queue 0 (measured processing cycles 0).
2024-02-29T11:02:54.332Z|00116|dpif|WARN|netdev@ovs-netdev: port_set_config failed (Invalid argument)
2024-02-29T11:02:54.332Z|00117|ofproto|WARN|br0: datapath configuration on port 1 (dpdk0) failed (Invalid argument)
2024-02-29T11:02:54.335Z|00118|dpdk|INFO|Device with port_id=1 already stopped
2024-02-29T11:02:54.350Z|00119|dpdk|INFO|ice_set_rx_function(): Using AVX2 OFFLOAD Vector Rx (port 1).
2024-02-29T11:02:54.813Z|00120|netdev_dpdk|INFO|Port 1: 6c:fe:54:6b:4f:11
2024-02-29T11:02:54.814Z|00121|netdev_dpdk|INFO|dpdk1: rx-steering: default rss
2024-02-29T11:02:54.814Z|00122|dpif_netdev|INFO|Performing pmd to rx queue assignment using cycles algorithm.
Thanks & Regards,
Sivaprasad
From: Sindhura Bandi <sindhura.bandi@certesnetworks.com>
Sent: Thursday, February 22, 2024 6:52 AM
To: users@dpdk.org
Subject: How to enable logging and where to find the logs
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
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: 10792 bytes --]
next prev parent reply other threads:[~2024-02-29 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 1:21 Sindhura Bandi
2024-02-29 11:11 ` Tummala, Sivaprasad [this message]
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=CH3PR12MB8233A3BE5197B903103AB25A865F2@CH3PR12MB8233.namprd12.prod.outlook.com \
--to=sivaprasad.tummala@amd.com \
--cc=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).