DPDK usage discussions
 help / color / Atom feed
From: vikram T <vikramet@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Segmentation fault at rte_cpu_get_flag_enabled
Date: Mon, 20 Apr 2020 23:33:56 +0530
Message-ID: <CANxYRjw+vHiK8SSMB3dzygXh2_W4RCZTT0ihz2H-yvftxHBvHg@mail.gmail.com> (raw)
In-Reply-To: <20200420080736.6934cee7@hermes.lan>

Hi Stephen,
Thanks for the response.
As far as I know the value given to CONFIG_RTE_MACHINE may be any of these:
( supported in DPDK)

armv7a  default  dpaa2  ivb     nhm        power8      snb       thunderx2
 xgene1
armv8a  dpaa     hsw    native  octeontx2  silvermont  thunderx  wsm

How do I find/determine the minimum CPU type from the above supported
machines?
Additionally our product runs on multiple machines and hence would like to
select the most minimum CPU set to avoid this issue.
Regards
Vikram

On Mon, Apr 20, 2020 at 8:37 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> On Mon, 20 Apr 2020 12:39:02 +0530
> vikram T <vikramet@gmail.com> wrote:
>
> > Hi,
> > I have been seeing the application crashes( DPDK v19.08) with
> segmentation
> > fault as below:
> > (gdb) bt
> > #0  0x000000000054fda9 in rte_cpu_get_flag_enabled ()
> > #1  0x00000000004f5d5e in rte_hash_crc_init_alg ()
> > #2  0x000000000084cf7d in __libc_csu_init ()
> > #3  0x00007ffff4df9425 in __libc_start_main () from /lib64/libc.so.6
> > #4  0x00000000005048df in _start ()
> > (gdb) q
> >
> > Here the DPDK is built and linked on the machine different from the
> target
> > machine.
> > Hence used the flag - "CONFIG_RTE_MACHINE = default"  but no success.
> >
> > Is there anything that needs to be followed to overcome this blocking
> issue?
> >
> > Regards
> > Vikram
>
> You need to to set CONFIG_RTE_MACHINE to the minimum cpu type that your
> product needs to run on. That value sets the compiler flags which determine
> which extended CPU instructions will be used.
>

  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  7:09 vikram T
2020-04-20 15:07 ` Stephen Hemminger
2020-04-20 18:03   ` vikram T [this message]
2020-04-20 20:23     ` Stephen Hemminger

Reply instructions:

You may reply publically 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=CANxYRjw+vHiK8SSMB3dzygXh2_W4RCZTT0ihz2H-yvftxHBvHg@mail.gmail.com \
    --to=vikramet@gmail.com \
    --cc=stephen@networkplumber.org \
    --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

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox