DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] build: add platform meson option
Date: Thu, 15 Apr 2021 14:51:48 +0100	[thread overview]
Message-ID: <YHhE9DcU5dvYe7Ov@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <99700db0dcbf42d592771689de61aa9f@pantheon.tech>

On Thu, Apr 15, 2021 at 01:32:08PM +0000, Juraj Linkeš wrote:
> 
> 
> > -----Original Message-----
> > From: Bruce Richardson <bruce.richardson@intel.com>
> > Sent: Wednesday, March 31, 2021 2:39 PM
> > To: Juraj Linkeš <juraj.linkes@pantheon.tech>
> > Cc: thomas@monjalon.net; david.marchand@redhat.com;
> > Honnappa.Nagarahalli@arm.com; dev@dpdk.org
> > Subject: Re: [PATCH v4] build: add platform meson option
> > 
> > On Wed, Mar 31, 2021 at 12:16:59PM +0000, Juraj Linkeš wrote:
> > > Bruce, what do you think of the patch now? Do we need to add/change
> > anything else, like documentation?
> > >
> > > One thing to note is that we're changing the default behavior in this patch
> > from machine=native to machine=generic (or more accurately, to
> > cpu_instruction_set=generic). Do we want to do that?
> > >
> > The patch in general looks ok, but I am uncertain about this change indeed.
> > Especially since the -march flag we mirror to the pkg-config file. I'd like to see
> > something like [1] included along with such a change. It allows us per-arch to
> > select the flags to send to the pkg-config file, rather than just always using
> > machine_args blindly.
> > 
> > Feedback appreciated.
> > 
> 
> I'm not sure what feedback do you want here. I'm not that familiar with pkg-config files. I think this is about DPDK being built a set of instructions and an app using DPDK being able to be built another set of instructions and the pkg-config file bridges these? Could you expand a bit? I read the other commit msg (in [1]) as well and I don't know how it's related to this patch.
> 
The main thing I suppose I'm concerned about is that I'd like more input
from people on the change from "native" to "generic" build by default.

On top of that, the patch I linked to adjusts things a little further
allowing separation of the ISA level used for building DPDK and for
building the app using DPDK. For example, for x86, it would probably be
more respectful for applications to have "-msse4" in the pkg-config file,
rather than -march=native or -march=corei7. The fact that DPDK was compiled
for a particular micro-arch should not force the user to use the same
micro-arch. Instead, each architecture should be able to output a separate
value that is suitable - in x86 case, turning on SSE4.2 as the minimum
needed ISA level.

However, I'm prepared to accept that discussion of the latter change can be
dealt with separately from this patch. So long as others have no objection
to change in default machine flags, I'm ok with it too.

/Bruce

  reply	other threads:[~2021-04-15 13:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 15:47 [dpdk-dev] [RFC PATCH v1] " Juraj Linkeš
2020-11-26 16:02 ` Bruce Richardson
2020-11-27  8:31   ` Juraj Linkeš
2020-11-27 14:07     ` Bruce Richardson
2020-12-23 11:23       ` Juraj Linkeš
2021-01-04 11:52 ` [dpdk-dev] [RFC PATCH v2] " Juraj Linkeš
2021-01-04 11:59   ` Juraj Linkeš
2021-01-05 22:17     ` David Christensen
2021-01-06 14:42       ` Bruce Richardson
2021-02-19  9:11         ` Juraj Linkeš
2021-02-22 21:25           ` David Christensen
2021-02-23  8:45             ` Juraj Linkeš
2021-02-23  9:43               ` Bruce Richardson
2021-02-25 12:51                 ` Juraj Linkeš
2021-02-25 12:54                   ` Bruce Richardson
2021-02-25 12:57                     ` Juraj Linkeš
2021-03-29 11:03   ` [dpdk-dev] [PATCH v3] " Juraj Linkeš
2021-03-29 12:50     ` [dpdk-dev] [PATCH v4] " Juraj Linkeš
2021-03-31 12:16       ` Juraj Linkeš
2021-03-31 12:19         ` Juraj Linkeš
2021-03-31 12:39         ` Bruce Richardson
2021-04-15 13:32           ` Juraj Linkeš
2021-04-15 13:51             ` Bruce Richardson [this message]
2021-04-20  8:08       ` [dpdk-dev] [PATCH v5] build: use platform option for generic and native Juraj Linkeš
2021-04-20  8:16         ` Juraj Linkeš
2021-04-20  8:36           ` Thomas Monjalon
2021-04-21  8:37             ` Juraj Linkeš
2021-04-22  8:34               ` Wang, Yinan
2021-06-30 13:09         ` [dpdk-dev] [PATCH v6] build: use platform for generic and native builds Juraj Linkeš
2021-07-06  9:44           ` [dpdk-dev] [PATCH v7] " Juraj Linkeš
2021-07-07 13:59             ` Bruce Richardson
2021-07-09 12:30               ` Thomas Monjalon
2021-07-09 13:55                 ` Juraj Linkeš

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=YHhE9DcU5dvYe7Ov@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=thomas@monjalon.net \
    /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).