From: "Li,Rongqing" <lirongqing@baidu.com>
To: Wen Gu <guwen@linux.alibaba.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"dust.li@linux.alibaba.com" <dust.li@linux.alibaba.com>
Subject: RE: [PATCH][net-next] net/smc: avoid atomic_set and smp_wmb in the tx path when possible
Date: Thu, 16 Nov 2023 12:06:21 +0000 [thread overview]
Message-ID: <3816364405a04427999739f5ca0b0536@baidu.com> (raw)
In-Reply-To: <d8c0ac0d-f28b-8984-06f9-41bfdcb03425@linux.alibaba.com>
> -----Original Message-----
> From: Wen Gu <guwen@linux.alibaba.com>
> Sent: Thursday, November 16, 2023 5:28 PM
> To: Li,Rongqing <lirongqing@baidu.com>; wenjia@linux.ibm.co;
> netdev@vger.kernel.org; linux-s390@vger.kernel.org; dust.li@linux.alibaba.com
> Subject: Re: [PATCH][net-next] net/smc: avoid atomic_set and smp_wmb in the
> tx path when possible
>
>
>
> On 2023/11/16 10:20, Li RongQing wrote:
> > there is rare possibility that conn->tx_pushing is not 1, since
> There
> > 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
> .
> >
>
> Some nits:
>
> 1. It is normally using [PATCH net-next] rather than [PATCH][net-next]
> in subject. And new version should better be marked. such as:
>
> # git format-patch --subject-prefix="PATCH net-next" -v 3
>
> And CC all relevant people listed by:
>
> # ./scripts/get_maintainer.pl <your patch>
>
> 2. Few improvements in the commit body.
>
>
Ok, thanks
-Li
prev parent reply other threads:[~2023-11-16 12:06 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
2023-11-16 9:28 ` Wen Gu
2023-11-16 12:06 ` 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=3816364405a04427999739f5ca0b0536@baidu.com \
--to=lirongqing@baidu.com \
--cc=dust.li@linux.alibaba.com \
--cc=guwen@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