DPDK usage discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: gowrishankar <gowrishankar.m@linux.vnet.ibm.com>, users@dpdk.org
Subject: Re: [dpdk-users] Difficulty With rte_eal_init()
Date: Tue, 29 Mar 2016 14:30:44 -0700	[thread overview]
Message-ID: <20160329213044.GA15001@mhcomputing.net> (raw)
In-Reply-To: <CA+Gp1nbRj273joNS6Euv3RzLrBw41PRtXnuPofZbd2keswpORg@mail.gmail.com>

On Tue, Mar 29, 2016 at 02:16:45PM -0700, Cliff Burdick wrote:
> Hi Matthew, sorry for the late response. I'm getting compilation errors
> when I try to do what you suggested. I should have the same headers
> included by the l2fwd example. I'm running g++ 4.8.5. Here are the new
> errors and the compilation line:

All of those seemed to be referencing _mm_alignr_epi8 which is part of 
Supplemental Streaming SIMD Extensions 3 (SSSE3).

So you have to check GCC man page, docs, and code, to make sure whatever flag 
required for enabling Supplemental Streaming SIMD Extensions 3 (SSSE3) 
instructions is present or the intrinsic function implementations (which get 
stubbed out to the assembly trampoline for the instruction named) will not 
exist.

Personally, the fact that the intrinsics don't come with a default software 
implementation that raises a compile warning is one of my top hatreds 
associated with the use of these instructions. I've spent hours on issues like 
this w/ my DPDK app...

Matthew.

  reply	other threads:[~2016-03-29 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 21:45 Cliff Burdick
2016-03-18 21:56 ` Matthew Hall
2016-03-18 23:40   ` Cliff Burdick
2016-03-19  2:45     ` Matthew Hall
2016-03-20  6:16 ` gowrishankar
2016-03-29 21:16   ` Cliff Burdick
2016-03-29 21:30     ` Matthew Hall [this message]
2016-03-30  7:49       ` Van Haaren, Harry
2016-03-30 14:16       ` Cliff Burdick
2016-03-30 22:40         ` Matthew Hall

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=20160329213044.GA15001@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=gowrishankar.m@linux.vnet.ibm.com \
    --cc=shaklee3@gmail.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).