DPDK usage discussions
 help / color / mirror / Atom feed
From: "Das, Surajit" <Surajit.Das@commscope.com>
To: "nicolas.neel@allentis.eu" <nicolas.neel@allentis.eu>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Segmentation fault with -msse3
Date: Thu, 4 Mar 2021 17:27:51 +0000	[thread overview]
Message-ID: <DM6PR14MB3757C351B15EB143940EE68AE9979@DM6PR14MB3757.namprd14.prod.outlook.com> (raw)
In-Reply-To: <011601d71117$7076e8c0$5164ba40$@allentis.eu>

Hi Nicolas,

Looks like the CPU you are running on does not have the instruction ssse3.
To check the list of flags available of your cpu, you can run:
lscpu | grep Flags
You will find that in the list of flags, ssse3 is not available on your cpu.

You can compile and run your app with the flag removed without functional issues.
Only difference will be that a bunch of instructions that could have been done faster in CPU hardware using ssse3, will now be done in software.

Regards,
Surajit

From: users <users-bounces@dpdk.org> On Behalf Of nicolas.neel@allentis.eu
Sent: Thursday, March 4, 2021 10:27 PM
To: users@dpdk.org
Subject: [dpdk-users] Segmentation fault with -msse3

Hello dpdk users, I'm a newbie to dpdk and I try to get the list of the rss hash functions for a given port with the following code : static uint64_t get_rss_function(int port_id){ int ret; struct rte
Caution (External, nicolas.neel@allentis.eu<mailto:nicolas.neel@allentis.eu>)
First-Time Sender   Details<https://shared.outlook.inky.com/details?id=Y29tbXNjb3BlL3N1cmFqaXQuZGFzQGNvbW1zY29wZS5jb20vNjQxYTEzNjExYzE5MDE4YTRmNjdmNGM4NzAxZjFkNTcvMTYxNDg3NzA2Mi4zOA==#key=0d6d90ea2c04f62ddfb3edae57dd7e6c>
  Report This Email<https://shared.outlook.inky.com/report?id=Y29tbXNjb3BlL3N1cmFqaXQuZGFzQGNvbW1zY29wZS5jb20vNjQxYTEzNjExYzE5MDE4YTRmNjdmNGM4NzAxZjFkNTcvMTYxNDg3NzA2Mi4zOA==#key=0d6d90ea2c04f62ddfb3edae57dd7e6c>  FAQ<https://www.inky.com/banner-faq/>  Protection by INKY<https://www.inky.com>


Hello dpdk users,





I'm a newbie to dpdk and I try to get the list of the rss hash functions for

a given port with the following code :





static uint64_t get_rss_function(int port_id){



                int ret;



                struct rte_eth_rss_conf rss_conf;





                ret = rte_eth_dev_rss_hash_conf_get(port_id,&rss_conf);



                if(ret < 0){



                               printf("No supported rss\n");



                               return 0;



                }



                return rss_conf.rss_hf;



}





I use dpdk version 20.11 and my code is compiled with the following flags (I

'm following the tips of the doc) :



CXXFLAGS += -mssse3 -mfma -mcx16 -msse4.1 -msse4.2 -mpopcnt -mavx -mavx2

-DALLOW_EXPERIMENTAL_API





I have a segmentation fault calling ret =

rte_eth_dev_rss_hash_conf_get(port_id,&rss_conf) ; and the coredump tell an

issue with __memcpy_ssse3().





If I remove the -mssse3 I don't have the crash.





Can you help me to identify the reason of the segmentation fault and tell me

if I can easily remove the < -mssse3 > flag ?





(Sorry for my english)



Regards



Nicolas



  reply	other threads:[~2021-03-04 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 16:57 nicolas.neel
2021-03-04 17:27 ` Das, Surajit [this message]
2021-03-05 11:25   ` nicolas.neel
2021-03-05 12:38     ` Das, Surajit

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=DM6PR14MB3757C351B15EB143940EE68AE9979@DM6PR14MB3757.namprd14.prod.outlook.com \
    --to=surajit.das@commscope.com \
    --cc=nicolas.neel@allentis.eu \
    --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).