DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Sarosh Arif <sarosh.arif@emumba.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] setting parameters in meson build system
Date: Thu, 22 Oct 2020 14:52:38 +0100	[thread overview]
Message-ID: <20201022135238.GA90@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CABoZmYNuPKhFHitnzqyAKAx69ssujC-TK8HTEFXEaNGnJb_k4Q@mail.gmail.com>

On Thu, Oct 22, 2020 at 04:43:50PM +0500, Sarosh Arif wrote:
> Hello,
> 
> I was using make build system previously, but since it is removed from
> dpdk now, I am trying to figure out how to enable/disable certain
> things using meson,
> 
> Previously we were able to set some parameters using .config file.
> Some examples of these parameters are:
> 
> CONFIG_RTE_LIBRTE_I40E_PMD=y
> CONFIG_RTE_LIBRTE_I40E_DEBUG_RX=n
> CONFIG_RTE_LIBRTE_I40E_DEBUG_TX=n
> CONFIG_RTE_LIBRTE_I40E_DEBUG_TX_FREE=n
> CONFIG_RTE_LIBRTE_I40E_RX_ALLOW_BULK_ALLOC=y
> CONFIG_RTE_LIBRTE_I40E_INC_VECTOR=y
> CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC=n
> CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_PF=64
> CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM=4
> 
> Can someone help me figure out how to enable/disable/change these
> using the meson build system?
> 

Enabling/disabling of specific drivers can be done using the
"disable_drivers" meson option to disable drivers, otherwise the drivers
will be enabled automatically if their pre-requisites are met. [In the case
of i40e it has no pre-requisites beyond basic DPDK requirements so it's
always enabled by default].

For the debug settings, there has been discussion onlist about having a
global debug setting which can be scope limited in the same way as the log
level APIs, but in the absense of support for that you can turn on the
DEBUG settings by passing them as cflags (or c_args meson option) to the
build.

For the other settings, these are present in config/rte_config.h header
file and can be edited directly there. However, we'd prefer if this wasn't
necessary, so if you feel the defaults are not suitable for your use,
please let the maintainers know, to see if we can adjust the default to be
suitable for as many users as possible.

Regards,
/Bruce

      reply	other threads:[~2020-10-22 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 11:43 Sarosh Arif
2020-10-22 13:52 ` Bruce Richardson [this message]

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=20201022135238.GA90@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=sarosh.arif@emumba.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).