DPDK usage discussions
 help / color / mirror / Atom feed
From: wang yufan <wangyufan854978151@outlook.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: meson options - build vs target machine cpuflags question
Date: Sat, 12 Oct 2024 10:14:06 +0000	[thread overview]
Message-ID: <TY1PR01MB107878A3D3FD96284F42741029C7A2@TY1PR01MB10787.jpnprd01.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]

Here’s a draft for your email that you can send to inquire about resolving the RDSEED issue with DPDK:
________________________________
Subject: Inquiry Regarding DPDK RDSEED Support on Non-RDSEED Machines
Dear DPDK Development Team,
I hope this message finds you well.
I am currently facing an issue while building and running a DPDK 21.05 application on Intel x86 machines that have RDSEED in the CPU flags. We also need to run this application on machines that do not support RDSEED, which leads to the following fatal error:

ERROR: This system does not support "RDSEED".
Please check that RTE_MACHINE is set correctly.
EAL: FATAL: unsupported cpu type.


To address this, I attempted to add the -Dplatform=haswell option while running Meson, as I understand that Haswell is the last architecture without RDSEED support. However, I am still encountering the same error.
Currently, our workaround is to modify the error handling in rte_cpu_is_supported() to print a warning instead of exiting the application. However, this is not an ideal solution for us.
Given that we do not have direct access to automated build machines and must go through a change request process, it would be helpful to know if there is a more effective Meson configuration option (such as machine=haswell or anything else) that could help us resolve this issue.
I appreciate any guidance or suggestions you can provide to help us navigate this challenge.
Thank you in advance for your assistance!
Best regards,
wyf

[-- Attachment #2: Type: text/html, Size: 4472 bytes --]

             reply	other threads:[~2024-10-14 17:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-12 10:14 wang yufan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-10 14:46 Sanford, Robert
2022-03-10 22:54 ` Dan Gora
2022-03-10 22:58   ` Dan Gora
2022-03-10 23:39     ` Sanford, Robert
2022-03-11  0:00       ` Dan Gora
2022-03-11  1:18   ` Stephen Hemminger
2022-03-11  2:45     ` Dan Gora
2022-03-11  3:01       ` Stephen Hemminger

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=TY1PR01MB107878A3D3FD96284F42741029C7A2@TY1PR01MB10787.jpnprd01.prod.outlook.com \
    --to=wangyufan854978151@outlook.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).