DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] arch check in example dpdk_qat
Date: Thu, 24 Mar 2016 10:50:11 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8CF6DC@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <3286701.A42TaaeMmo@xps13>

Hi Thomas,

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, March 23, 2016 11:04 AM
> To: Richardson, Bruce; De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: arch check in example dpdk_qat
> 
> When reading examples/dpdk_qat/Makefile, we can see this check:
> 
>     ifneq ($(CONFIG_RTE_ARCH),"x86_64")
>         ifneq ($(LBITS),i686)
>         $(error The RTE_TARGET chosen is not compatible with this environment
> \
>         (x86_64), for this application. Please change the definition of the \
>         RTE_TARGET environment variable, or run the application on a 32-bit
> OS)
>         endif
>     endif
> 
> Is it on purpose to limit the 32-bit support to i686 only?
> Instead of the message "run the application on a 32-bit OS", should it be
> "on an i686 OS"?

i686 OS looks fine to me. Basically, when this app was made, the only 32-bit target was i686,
and the app needs the QAT driver to be running in 32 bits, if DPDK target is 32-bit.

Thanks,
Pablo

  reply	other threads:[~2016-03-24 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 11:04 Thomas Monjalon
2016-03-24 10:50 ` De Lara Guarch, Pablo [this message]
2016-03-24 11:00   ` Thomas Monjalon
2016-03-24 11:58     ` De Lara Guarch, Pablo
2016-03-24 13:16       ` Thomas Monjalon

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=E115CCD9D858EF4F90C690B0DCB4D8973C8CF6DC@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    /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).