DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: david.marchand@redhat.com, junx.dong@intel.com
Subject: Re: [PATCH] config: remove explicit undef of unset values
Date: Mon, 13 Jun 2022 10:54:33 +0100	[thread overview]
Message-ID: <YqcJWcZkpwDiXkdb@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20211216111430.699717-1-bruce.richardson@intel.com>

On Thu, Dec 16, 2021 at 11:14:30AM +0000, Bruce Richardson wrote:
> Rather than explicitly clearing any setting of undefined values in our
> rte_config.h file, it's better to instead just add a comment that the
> value is not set. Using a comment allows the user to set the value using
> CFLAGS or similar mechanism without the config file clearing the value
> again.
> 
> The text used "<VALUE> is not set" is modelled after the kernel approach
> of doing the same thing.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> 
> Although DPDK coding convention forbids use of "//" for comments, using
> regular C comment style makes the config settings less clear, as they can
> be confused with regular comments in the file. Using "//" makes them stand
> out better, so I prefer it. However, if others feel strongly, they can be
> changed to standard.
> 
> Note: this is a resubmission of patch [1] which was part of a rejected
> series. However, the reasons for rejection - values in config being out
> of sync with those used for building apps - are less relevant for
> many, if not all, of these setting, so I believe the benefits for
> testing outweigh the potential downsides. If any setting is likely
> problematic, I can keep the explicit undef for that case in a new patch
> version.
> 
> [1] http://patches.dpdk.org/project/dpdk/patch/20200903144942.671870-2-bruce.richardson@intel.com/
> ---

Ping for review or feedback for this patch. I'd like to see it move forward
into a DPDK release if possible.

/Bruce

>  config/rte_config.h | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/config/rte_config.h b/config/rte_config.h
> index cab4390a97..953216babd 100644
> --- a/config/rte_config.h
> +++ b/config/rte_config.h
> @@ -83,17 +83,17 @@
>  
>  /* ip_fragmentation defines */
>  #define RTE_LIBRTE_IP_FRAG_MAX_FRAG 8
> -#undef RTE_LIBRTE_IP_FRAG_TBL_STAT
> +// RTE_LIBRTE_IP_FRAG_TBL_STAT is not set
>  
>  /* rte_power defines */
>  #define RTE_MAX_LCORE_FREQS 64
>  
>  /* rte_sched defines */
> -#undef RTE_SCHED_CMAN
> -#undef RTE_SCHED_COLLECT_STATS
> -#undef RTE_SCHED_SUBPORT_TC_OV
> +// RTE_SCHED_CMAN is not set
> +// RTE_SCHED_COLLECT_STATS is not set
> +// RTE_SCHED_SUBPORT_TC_OV is not set
>  #define RTE_SCHED_PORT_N_GRINDERS 8
> -#undef RTE_SCHED_VECTOR
> +// RTE_SCHED_VECTOR is not set
>  
>  /* KNI defines */
>  #define RTE_KNI_PREEMPT_DEFAULT 1
> @@ -127,7 +127,7 @@
>  
>  /* i40e defines */
>  #define RTE_LIBRTE_I40E_RX_ALLOW_BULK_ALLOC 1
> -#undef RTE_LIBRTE_I40E_16BYTE_RX_DESC
> +// RTE_LIBRTE_I40E_16BYTE_RX_DESC is not set
>  #define RTE_LIBRTE_I40E_QUEUE_NUM_PER_PF 64
>  #define RTE_LIBRTE_I40E_QUEUE_NUM_PER_VF 4
>  #define RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM 4
> @@ -140,6 +140,6 @@
>  #define RTE_LIBRTE_QEDE_FW ""
>  
>  /* DLB2 defines */
> -#undef RTE_LIBRTE_PMD_DLB2_QUELL_STATS
> +// RTE_LIBRTE_PMD_DLB2_QUELL_STATS is not set
>  
>  #endif /* _RTE_CONFIG_H_ */
> -- 
> 2.32.0
> 

  reply	other threads:[~2022-06-13  9:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 11:14 Bruce Richardson
2022-06-13  9:54 ` Bruce Richardson [this message]
2022-06-13 10:01   ` Morten Brørup
2022-06-13 12:26   ` David Marchand
2022-06-13 12:37     ` Bruce Richardson
2022-06-13 14:20       ` David Marchand
2022-06-13 14:48         ` Bruce Richardson
2022-06-13 14:46   ` Tyler Retzlaff
2022-06-15  7:14 ` David Marchand

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=YqcJWcZkpwDiXkdb@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=junx.dong@intel.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).