From: "Li,Rongqing" <lirongqing@baidu.com>
To: Wenjia Zhang <wenjia@linux.ibm.com>
Cc: "linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH] net/smc: avoid atomic_set and smp_wmb in the tx path when possible
Date: Fri, 3 Nov 2023 04:56:00 +0000 [thread overview]
Message-ID: <3a5eedd0376b4a29b351a1f43b81c384@baidu.com> (raw)
In-Reply-To: <4b1c9303-9ad1-42f3-a1a2-b9ccfcafd022@linux.ibm.com>
> -----Original Message-----
> From: Wenjia Zhang <wenjia@linux.ibm.com>
> Sent: Friday, November 3, 2023 4:42 AM
> To: Li,Rongqing <lirongqing@baidu.com>
> Cc: linux-s390@vger.kernel.org; netdev@vger.kernel.org
> Subject: Re: [PATCH] net/smc: avoid atomic_set and smp_wmb in the tx path
> when possible
>
>
>
> On 02.11.23 10:27, Li RongQing wrote:
> > these is less opportunity 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 when possible
> >
> I think we should avoid to use argument like "less opportunity" in commit
> message. Because "less opportunity" does not mean "no opportunity". Once it
> occurs, does it mean that what the patch changes is useless or wrong?
>
I will reword the message.
I think this is a question of probability. even tx_pushing is not 1, this is still not a problem, atomic_dec_and_test(&conn->tx_pushing) will return false, transmit will be looped again, and tx_pushing will be added at any time
> > Signed-off-by: Li RongQing <lirongqing@baidu.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 */
> > goto again;
> > + }
> >
> > return rc;
> > }
> I'm afraid that the *if* statement would never be true, without setting the
> value of &conn->tx_pushing firstly.
I think conn->tx_pushing do not need to be set in this condition, and this patch is trying to avoid setting it
Thanks
-Li
prev parent reply other threads:[~2023-11-03 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 9:27 [PATCH] net/smc: avoid atomic_set and smp_wmb in the tx path when possible Li RongQing
2023-11-02 14:54 ` Dust Li
2023-11-03 4:43 ` Li,Rongqing
2023-11-02 20:42 ` Wenjia Zhang
2023-11-03 4:56 ` Li,Rongqing [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=3a5eedd0376b4a29b351a1f43b81c384@baidu.com \
--to=lirongqing@baidu.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wenjia@linux.ibm.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