test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Ma, WenwuX" <wenwux.ma@intel.com>
To: "Tang, Xia" <ys.tangxia@h3c.com>, "spp@dpdk.org" <spp@dpdk.org>,
	"users@dpdk.org" <users@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>
Cc: Dengfei <YS.dengfei@h3c.com>,
	Dengxiaozhou <YS.dengxiaozhou@h3c.com>,
	Fuminyi <fu.minyi@h3c.com>, Zuoyihua <YS.zuoyihua@h3c.com>,
	Xueweiwei <YS.xueweiwei@h3c.com>
Subject: RE: DPDK内存复制性能测试dpdk-test-dma-perf,执行失败,case1报错 IDXD: idxd_dmadev_probe_pci(): Failed to create dmadev 0000:80:01.0
Date: Mon, 13 May 2024 08:04:32 +0000	[thread overview]
Message-ID: <MN0PR11MB6110C47829483AEEBAD359ADEBE22@MN0PR11MB6110.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5cc5c27f45e848d28e09fb4dee6d9dec@h3c.com>


[-- Attachment #1.1: Type: text/plain, Size: 2198 bytes --]

错误信息提示 reached maximum number of DMA devices,也许可以尝试减少dma设备个数

From: Tangxia <YS.tangxia@h3c.com>
Sent: Wednesday, May 8, 2024 3:21 PM
To: spp@dpdk.org; users@dpdk.org; dts@dpdk.org
Cc: Dengfei <YS.dengfei@h3c.com>; Dengxiaozhou <YS.dengxiaozhou@h3c.com>; Fuminyi <fu.minyi@h3c.com>; Zuoyihua <YS.zuoyihua@h3c.com>; Xueweiwei <YS.xueweiwei@h3c.com>
Subject: DPDK内存复制性能测试dpdk-test-dma-perf,执行失败,case1报错 IDXD: idxd_dmadev_probe_pci(): Failed to create dmadev 0000:80:01.0

DPDK内存复制性能测试dpdk-test-dma-perf,执行失败,case1报错 IDXD: idxd_dmadev_probe_pci(): Failed to create dmadev 0000:80:01.0
想请教一下报错原因,以及如何解决?
配置如下:
CPU : Granite Rapids-AP-ES2-96cores-550W-99CF6G/Q3YE *2
DIMM:MICRON_48GB 1RX4 DDR5 DIMM 1anm 5600B内存条_MTC20F104XS1RC56BB1 MLFF * 8
OS:velinux-2.0-hwe-amd64-DVD-1
kernel:6.6.3.bsk.business.1
报错如下:
[cid:image001.png@01DAA54D.20C49570]
同时我发了一份更多执行日志《详细信息日志.zip》,可以看到更多信息
如果没有收到附件日志,可能是由于邮箱限制,可以企业微信联系获取:13283877762
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!

[-- Attachment #1.2: Type: text/html, Size: 7866 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 73733 bytes --]

  reply	other threads:[~2024-05-13  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  7:21 Tangxia
2024-05-13  8:04 ` Ma, WenwuX [this message]
2024-06-06  3:02   ` 回复: " Tangxia

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=MN0PR11MB6110C47829483AEEBAD359ADEBE22@MN0PR11MB6110.namprd11.prod.outlook.com \
    --to=wenwux.ma@intel.com \
    --cc=YS.dengfei@h3c.com \
    --cc=YS.dengxiaozhou@h3c.com \
    --cc=YS.xueweiwei@h3c.com \
    --cc=YS.zuoyihua@h3c.com \
    --cc=dts@dpdk.org \
    --cc=fu.minyi@h3c.com \
    --cc=spp@dpdk.org \
    --cc=users@dpdk.org \
    --cc=ys.tangxia@h3c.com \
    /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).