From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
Cc: users@dpdk.org
Subject: Re: How to disable usage of VPCLMULQDQ
Date: Fri, 23 Dec 2022 14:57:38 +0300 [thread overview]
Message-ID: <20221223145738.67dc6e6a@sovereign> (raw)
In-Reply-To: <CAAFk=6CC6pTUkU_UvCLLh8c9dystjyApJqxaH0w0HDmxq-N_vA@mail.gmail.com>
2022-12-23 13:15 (UTC+0200), Oleksandr Nahnybida:
> Hi All,
>
> DPDKv22.11
>
> My build machine supports VPCLMULQDQ instruction, but the machine I run
> DPDK on doesn't support it, is there a way to force the build system not to
> use this instruction?
>
> Right now, I added this line at the beginning of config/x86/meson.build:
> machine_args += '-mno-vpclmulqdq'
>
> But, it would have been nice if there was a build config to do this.
Hi Oleksandr,
Use -Dcpu_instruction_set=haswell (for example) suitable for your target.
Read more about -Dplatform and -Dcpu_instruction_set:
https://doc.dpdk.org/guides/linux_gsg/build_dpdk.html
prev parent reply other threads:[~2022-12-23 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 11:15 Oleksandr Nahnybida
2022-12-23 11:57 ` Dmitry Kozlyuk [this message]
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=20221223145738.67dc6e6a@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=oleksandrn@interfacemasters.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).