DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Vargas, Hernan" <hernan.vargas@intel.com>,
	"Marchand, David" <david.marchand@redhat.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"roretzla@linux.microsoft.com" <roretzla@linux.microsoft.com>
Subject: RE: [PATCH 1/2] baseband/fpga_5gnr_fec: use new barrier API
Date: Thu, 22 Feb 2024 18:05:39 +0000	[thread overview]
Message-ID: <BY5PR11MB4451018C8D2D61965A94C747F8562@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240222162113.1896370-1-maxime.coquelin@redhat.com>

Hi Maxime, 

Why would we change this here and now? Is the intent not to use new suggested semantics for new patches only?
Are all DPDK drivers being changed?
I am unsure we would want to change these drivers, this is kind of risk introduced by code churn that gets ecosystem unwilling to move to latest version.
These memory barriers issues are awful to troubleshoot or properly validate, so personally quite reluctant to change. 

Thanks
Nic

> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Thursday, February 22, 2024 8:21 AM
> To: dev@dpdk.org; Chautru, Nicolas <nicolas.chautru@intel.com>; Vargas,
> Hernan <hernan.vargas@intel.com>; Marchand, David
> <david.marchand@redhat.com>; thomas@monjalon.net;
> roretzla@linux.microsoft.com
> Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
> Subject: [PATCH 1/2] baseband/fpga_5gnr_fec: use new barrier API
> 
> rte_smp_rmb() is deprecated, use the new API instead as suggested in
> rte_atomic header.
> 
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
>  drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c
> b/drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c
> index efc1d3a772..314c87350e 100644
> --- a/drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c
> +++ b/drivers/baseband/fpga_5gnr_fec/rte_fpga_5gnr_fec.c
> @@ -2661,7 +2661,7 @@ vc_5gnr_dequeue_ldpc_enc_one_op_cb(struct
> fpga_5gnr_queue *q, struct rte_bbdev_e
>  		return -1;
> 
>  	/* make sure the response is read atomically */
> -	rte_smp_rmb();
> +	rte_atomic_thread_fence(rte_memory_order_acquire);
> 
>  	rte_bbdev_log_debug("DMA response desc %p", desc);
> 
> @@ -2690,7 +2690,7 @@ agx100_dequeue_ldpc_enc_one_op_cb(struct
> fpga_5gnr_queue *q, struct rte_bbdev_en
>  		return -1;
> 
>  	/* make sure the response is read atomically. */
> -	rte_smp_rmb();
> +	rte_atomic_thread_fence(rte_memory_order_acquire);
> 
>  	rte_bbdev_log_debug("DMA response desc %p", desc);
> 
> @@ -2722,7 +2722,7 @@ vc_5gnr_dequeue_ldpc_dec_one_op_cb(struct
> fpga_5gnr_queue *q, struct rte_bbdev_d
>  		return -1;
> 
>  	/* make sure the response is read atomically */
> -	rte_smp_rmb();
> +	rte_atomic_thread_fence(rte_memory_order_acquire);
> 
>  #ifdef RTE_LIBRTE_BBDEV_DEBUG
>  	vc_5gnr_print_dma_dec_desc_debug_info(desc);
> @@ -2768,7 +2768,7 @@ agx100_dequeue_ldpc_dec_one_op_cb(struct
> fpga_5gnr_queue *q, struct rte_bbdev_de
>  		return -1;
> 
>  	/* make sure the response is read atomically. */
> -	rte_smp_rmb();
> +	rte_atomic_thread_fence(rte_memory_order_acquire);
> 
>  #ifdef RTE_LIBRTE_BBDEV_DEBUG
>  	agx100_print_dma_dec_desc_debug_info(desc);
> --
> 2.43.0


  parent reply	other threads:[~2024-02-22 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 16:21 Maxime Coquelin
2024-02-22 16:21 ` [PATCH 2/2] baseband/fpga_lte_fec: " Maxime Coquelin
2024-02-22 18:05 ` Chautru, Nicolas [this message]
2024-02-26 11:03   ` [PATCH 1/2] baseband/fpga_5gnr_fec: " Maxime Coquelin
2024-02-27 16:56     ` Maxime Coquelin

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=BY5PR11MB4451018C8D2D61965A94C747F8562@BY5PR11MB4451.namprd11.prod.outlook.com \
    --to=nicolas.chautru@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hernan.vargas@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=roretzla@linux.microsoft.com \
    --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).