DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCHv3 0/5] ACL library
Date: Sat, 14 Jun 2014 00:07:09 +0000	[thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B01AA36227@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1541041.MVudaz1CFn@xps13>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Friday, June 13, 2014 4:38 PM
> To: Ananyev, Konstantin
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCHv3 0/5] ACL library
> 
> 2014-06-13 12:02, Ananyev, Konstantin:
> > 2014-06-13 13:56, Thomas Monjalon:
> > > > Konstantin Ananyev (5):
> > > >   Add ACL library (librte_acl) into DPDK
> > > >   acl: update UT to reflect latest changes in the librte_acl
> > > >   acl: New test-acl application
> > > >   acl: New sample l3fwd-acl
> > > >   acl: add doxygen configuration and start page
> > > >
> > > > v2 fixes:
> > > > * Fixed several checkpatch.pl issues
> > > > * Added doxygen related changes
> > > >
> > > > v3 fixes:
> > > > * Fixed even more checkpatch.pl issues
> > >
> > > Sorry to bother you but after checking v3,
> > >
> > > I think these errors should be avoided:
> > > 	ERROR: do not use assignment in if condition
> > > 	ERROR: return is not a function, parentheses are not required
> >
> > These changes would require a lot of changes inside ACL library.
> > As I said in cover letter, ACL library was part of IPL code for a while
> > (nearly a year).
> > I don't really want to make significant changes in it just before the
> > release without really good reason - bugs found.
> 
> I've made the code style changes, move some configuration lines and added
> to BSD build (not tested).
> As it was previously acked and tested,
> it is now applied for version 1.7.0.
> 
I'd be a bit wary about adding it to the BSD build. I'm only running BSD in a VM here, but there GCC fails to recognise the processor supports SSE4 instruction sets when using "-march=native", and so fails to compile the vector code - at least the vectorized PMD functions. That's why I've explicitly disabled those in the latest version of the vector PMD patch, and I would suggest doing the same for the ACL code for now.

Interestingly enough, in the same VM clang does seem to recognise SSE4. Output from the compilers below. Anyone with a physical box running BSD who could confirm if this issue is localised to VMs or not?

[bruce@BSD10-VM ~]$ gcc48 -dM -E -march=native - < /dev/null | grep SSE
#define __SSE2_MATH__ 1
#define __SSE_MATH__ 1
#define __SSE2__ 1
#define __SSSE3__ 1
#define __SSE__ 1
#define __SSE3__ 1
[bruce@BSD10-VM ~]$ clang -dM -E -march=native - < /dev/null | grep SSE
#define __SSE2_MATH__ 1
#define __SSE2__ 1
#define __SSE3__ 1
#define __SSE4_1__ 1
#define __SSE4_2__ 1
#define __SSE_MATH__ 1
#define __SSE__ 1
#define __SSSE3__ 1

  reply	other threads:[~2014-06-14  0:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 11:26 Konstantin Ananyev
2014-06-13 11:26 ` [dpdk-dev] [PATCHv3 1/5] Add ACL library (librte_acl) into DPDK Konstantin Ananyev
2014-06-13 11:26 ` [dpdk-dev] [PATCHv3 2/5] acl: update UT to reflect latest changes in the librte_acl Konstantin Ananyev
2014-06-13 11:26 ` [dpdk-dev] [PATCHv3 3/5] acl: New test-acl application Konstantin Ananyev
2014-06-13 11:26 ` [dpdk-dev] [PATCHv3 4/5] acl: New sample l3fwd-acl Konstantin Ananyev
2014-06-13 11:26 ` [dpdk-dev] [PATCHv3 5/5] acl: add doxygen configuration and start page Konstantin Ananyev
2014-06-13 11:56 ` [dpdk-dev] [PATCHv3 0/5] ACL library Thomas Monjalon
2014-06-13 12:02   ` Ananyev, Konstantin
2014-06-13 23:38     ` Thomas Monjalon
2014-06-14  0:07       ` Richardson, Bruce [this message]
2014-06-14  7:55         ` 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=59AF69C657FD0841A61C55336867B5B01AA36227@IRSMSX103.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --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).