From: Bruce Richardson <bruce.richardson@intel.com>
To: Aaron Conole <aconole@redhat.com>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Gavin Hu <gavin.hu@arm.com>,
Michael Santana <msantana@redhat.com>
Subject: Re: [dpdk-dev] [PATCH 3/3] acl: adjust the tests
Date: Wed, 10 Apr 2019 14:46:51 +0100 [thread overview]
Message-ID: <20190410134651.GC718@bricha3-MOBL.ger.corp.intel.com> (raw)
Message-ID: <20190410134651.GV8V0CI4tUOTNrdCwKMQ_o9r8eXvQRFJ2mNvJ3QT2TY@z> (raw)
In-Reply-To: <20190410132456.GB718@bricha3-MOBL.ger.corp.intel.com>
On Wed, Apr 10, 2019 at 02:24:56PM +0100, Bruce Richardson wrote:
> On Wed, Apr 10, 2019 at 09:10:25AM -0400, Aaron Conole wrote:
> >
> > Okay - I'll look at this part more. I think I went down the path of
> > explicitly setting these because the comments didn't match with what was
> > occuring (for example, in the section that I changed that loops through
> > all versions, only the AVX2 and Scalar were being tested on my system,
> > while the comment implied SSE).
> >
> > I also believe that I split out the functions because of the linking
> > issue (I guess the way the linker resolves the functions works properly
> > when the weak versions are in a different translation unit)? I'll spend
> > some time trying to get it working in a different way.
> >
> > Regardless, this wasn't ready for posting as 'PATCH' - I meant it as
> > RFC. I don't intend to change the first two patches, though.
> >
> > And thank you for the all the feedback!
> >
> I've dug into this a bit, and I'm doing up a patch to remove the use of
> weak symbols in our libraries (note, just libs, not drivers) entirely.
> That's fairly easy to do, and not a big change, but should make this
> problem go away.
>
> /Bruce
Ref: http://patches.dpdk.org/project/dpdk/list/?series=4242
next prev parent reply other threads:[~2019-04-10 13:46 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 18:24 [dpdk-dev] [PATCH 0/3] librte_acl: fixes related to testing with the meson build Aaron Conole
2019-04-08 18:24 ` Aaron Conole
2019-04-08 18:24 ` [dpdk-dev] [PATCH 1/3] acl: fix arm argument types Aaron Conole
2019-04-08 18:24 ` Aaron Conole
2019-04-10 14:39 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-04-10 14:39 ` Jerin Jacob Kollanukkaran
2019-04-10 15:52 ` Aaron Conole
2019-04-10 15:52 ` Aaron Conole
2019-04-10 16:07 ` Jerin Jacob Kollanukkaran
2019-04-10 16:07 ` Jerin Jacob Kollanukkaran
2019-04-10 17:20 ` Aaron Conole
2019-04-10 17:20 ` Aaron Conole
2019-04-30 12:57 ` Aaron Conole
2019-04-30 12:57 ` Aaron Conole
2019-06-05 15:16 ` Jerin Jacob Kollanukkaran
2019-06-05 17:09 ` Aaron Conole
2019-04-08 18:24 ` [dpdk-dev] [PATCH 2/3] acl: update the build for multi-arch Aaron Conole
2019-04-08 18:24 ` Aaron Conole
2019-04-08 18:24 ` [dpdk-dev] [PATCH 3/3] acl: adjust the tests Aaron Conole
2019-04-08 18:24 ` Aaron Conole
2019-04-09 8:41 ` Ananyev, Konstantin
2019-04-09 8:41 ` Ananyev, Konstantin
2019-04-09 13:01 ` Aaron Conole
2019-04-09 13:01 ` Aaron Conole
2019-04-09 16:03 ` Ananyev, Konstantin
2019-04-09 16:03 ` Ananyev, Konstantin
2019-04-09 17:04 ` Ananyev, Konstantin
2019-04-09 17:04 ` Ananyev, Konstantin
2019-04-10 8:13 ` Richardson, Bruce
2019-04-10 8:13 ` Richardson, Bruce
2019-04-10 13:10 ` Aaron Conole
2019-04-10 13:10 ` Aaron Conole
2019-04-10 13:24 ` Bruce Richardson
2019-04-10 13:24 ` Bruce Richardson
2019-04-10 13:46 ` Bruce Richardson [this message]
2019-04-10 13:46 ` Bruce Richardson
2019-04-09 17:05 ` Richardson, Bruce
2019-04-09 17:05 ` Richardson, Bruce
2019-04-09 18:29 ` Ananyev, Konstantin
2019-04-09 18:29 ` Ananyev, Konstantin
2019-04-10 9:06 ` Bruce Richardson
2019-04-10 9:06 ` Bruce Richardson
2019-04-08 20:40 ` [dpdk-dev] [PATCH 0/3] librte_acl: fixes related to testing with the meson build Aaron Conole
2019-04-08 20:40 ` Aaron Conole
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=20190410134651.GC718@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=msantana@redhat.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).