[dpdk-dev] [PATCH v3] build: establish an invariant machine type

Thomas Monjalon thomas at monjalon.net
Sun Nov 18 14:24:04 CET 2018


14/11/2018 20:39, Christian Ehrhardt:
> On Wed, Nov 14, 2018 at 3:33 PM Christian Ehrhardt
> <christian.ehrhardt at canonical.com> wrote:
> >
> > Add the machine definition 'default' which is special compared
> > to 'native' (most optimized for current system) or any explicit
> > type (external entity has to decide on the type).
> >
> > It defaults to the per arch agreed common minimal baseline
> > needed for DPDK to reasonable work.
> >
> > That might not be the most optimized, but the most portable
> > version while still being able to support the CPU features
> > required for DPDK.
> >
> > Going forward this can be bumped up by the DPDK project, but it
> > can never be an invariant like 'native'.
> >
> > Distributions and other needing portable code are expected to
> > define the machine as 'default'.
> >
> > Changes in v2:
> > - fixed the non 64 bit arm default type
> > - changed baseline to default to match the old build system
> >
> > Changes in v3:
> > - add acked-by's
> > - removed old wording from commit message
> > - adding Fixes line per request by Luca Boccassi
> 
> FYI: I'll drop the version update from the commit (I didn't have a
> cover letter to add them instead).

You don't need a cover letter for changelogs.
You can insert it after ---
Usually, I insert changelogs between two --- lines.




More information about the dev mailing list