public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: "dust.li@linux.alibaba.com" <dust.li@linux.alibaba.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>
Subject: RE: [PATCH][net-next] net/smc: avoid atomic_set and smp_wmb in the tx path when possible
Date: Thu, 16 Nov 2023 07:02:50 +0000	[thread overview]
Message-ID: <64c98eb20e1244b981d0db9a912ce589@baidu.com> (raw)
In-Reply-To: <20231116061811.GC121324@linux.alibaba.com>

> -----Original Message-----
> From: Dust Li <dust.li@linux.alibaba.com>
> Sent: Thursday, November 16, 2023 2:18 PM
> To: Li,Rongqing <lirongqing@baidu.com>; wenjia@linux.ibm.co;
> netdev@vger.kernel.org; linux-s390@vger.kernel.org
> Subject: Re: [PATCH][net-next] net/smc: avoid atomic_set and smp_wmb in the
> tx path when possible
> 
> On Thu, Nov 16, 2023 at 10:20:41AM +0800, Li RongQing wrote:
> >there is rare possibility that conn->tx_pushing is not 1, since
> >tx_pushing is just checked with 1, so move the setting tx_pushing to 1
> >after atomic_dec_and_test() return false, to avoid atomic_set and
> >smp_wmb in tx path
> >
> >Signed-off-by: Li RongQing <lirongqing@baidu.com>
> Reviewed-by: Dust Li <dust.li@linux.alibaba.com>
> 
> >---
> > net/smc/smc_tx.c | 7 ++++---
> > 1 file changed, 4 insertions(+), 3 deletions(-)
> >
> >diff --git a/net/smc/smc_tx.c b/net/smc/smc_tx.c index 3b0ff3b..72dbdee
> >100644
> >--- a/net/smc/smc_tx.c
> >+++ b/net/smc/smc_tx.c
> >@@ -667,8 +667,6 @@ int smc_tx_sndbuf_nonempty(struct smc_connection
> *conn)
> > 		return 0;
> >
> > again:
> >-	atomic_set(&conn->tx_pushing, 1);
> >-	smp_wmb(); /* Make sure tx_pushing is 1 before real send */
> > 	rc = __smc_tx_sndbuf_nonempty(conn);
> >
> > 	/* We need to check whether someone else have added some data into
> @@
> >-677,8 +675,11 @@ int smc_tx_sndbuf_nonempty(struct smc_connection
> *conn)
> > 	 * If so, we need to push again to prevent those data hang in the send
> > 	 * queue.
> > 	 */
> >-	if (unlikely(!atomic_dec_and_test(&conn->tx_pushing)))
> >+	if (unlikely(!atomic_dec_and_test(&conn->tx_pushing))) {
> >+		atomic_set(&conn->tx_pushing, 1);
> >+		smp_wmb(); /* Make sure tx_pushing is 1 before real send */
> nit: it would be better if we change the comments to "send again".
> 

Ok, I will fix it, thanks

-Li


> Thanks
> > 		goto again;
> >+	}
> >
> > 	return rc;
> > }
> >--
> >2.9.4

  reply	other threads:[~2023-11-16  7:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16  2:20 [PATCH][net-next] net/smc: avoid atomic_set and smp_wmb in the tx path when possible Li RongQing
2023-11-16  6:18 ` Dust Li
2023-11-16  7:02   ` Li,Rongqing [this message]
2023-11-16  9:28 ` Wen Gu
2023-11-16 12:06   ` Li,Rongqing

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=64c98eb20e1244b981d0db9a912ce589@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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