DPDK usage discussions
 help / color / mirror / Atom feed
From: <nicolas.neel@allentis.eu>
To: <users@dpdk.org>
Subject: [dpdk-users] Segmentation fault with -msse3
Date: Thu, 4 Mar 2021 17:57:19 +0100	[thread overview]
Message-ID: <011601d71117$7076e8c0$5164ba40$@allentis.eu> (raw)

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 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 16:57 nicolas.neel [this message]
2021-03-04 17:27 ` Das, Surajit
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='011601d71117$7076e8c0$5164ba40$@allentis.eu' \
    --to=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).