From: Boqun Feng <boqun.feng@gmail.com>
To: guoren@kernel.org
Cc: arnd@arndb.de, palmer@dabbelt.com, mark.rutland@arm.com,
will@kernel.org, peterz@infradead.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
Guo Ren <guoren@linux.alibaba.com>,
Andrea Parri <parri.andrea@gmail.com>
Subject: Re: [PATCH V2 0/3] riscv: atomic: Optimize AMO instructions usage
Date: Wed, 13 Apr 2022 23:46:00 +0800 [thread overview]
Message-ID: <YlbwOG46mCR8Q5tJ@tardis> (raw)
In-Reply-To: <20220412034957.1481088-1-guoren@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
[Cc Andrea]
On Tue, Apr 12, 2022 at 11:49:54AM +0800, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> These patch series contain one cleanup and some optimizations for
> atomic operations.
>
Seems to me that you are basically reverting 5ce6c1f3535f
("riscv/atomic: Strengthen implementations with fences"). That commit
fixed an memory ordering issue, could you explain why the issue no
longer needs a fix?
Regards,
Boqun
> Changes in V2:
> - Fixup LR/SC memory barrier semantic problems which pointed by
> Rutland
> - Combine patches into one patchset series
> - Separate AMO optimization & LRSC optimization for convenience
> patch review
>
> Guo Ren (3):
> riscv: atomic: Cleanup unnecessary definition
> riscv: atomic: Optimize acquire and release for AMO operations
> riscv: atomic: Optimize memory barrier semantics of LRSC-pairs
>
> arch/riscv/include/asm/atomic.h | 70 ++++++++++++++++++++++++++++++--
> arch/riscv/include/asm/cmpxchg.h | 42 +++++--------------
> 2 files changed, 76 insertions(+), 36 deletions(-)
>
> --
> 2.25.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-13 15:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 3:49 [PATCH V2 0/3] riscv: atomic: Optimize AMO instructions usage guoren
2022-04-12 3:49 ` [PATCH V2 1/3] riscv: atomic: Cleanup unnecessary definition guoren
2022-04-12 3:49 ` [PATCH V2 2/3] riscv: atomic: Optimize acquire and release for AMO operations guoren
2022-04-12 3:49 ` [PATCH V2 3/3] riscv: atomic: Optimize memory barrier semantics of LRSC-pairs guoren
2022-04-13 15:46 ` Boqun Feng [this message]
2022-04-16 16:49 ` [PATCH V2 0/3] riscv: atomic: Optimize AMO instructions usage Guo Ren
2022-04-17 2:26 ` Boqun Feng
2022-04-17 4:51 ` Guo Ren
2022-04-17 6:30 ` Boqun Feng
2022-04-17 6:45 ` Guo Ren
2022-04-19 17:12 ` Dan Lustig
2022-04-20 5:33 ` Guo Ren
2022-04-20 17:03 ` Dan Lustig
2022-04-21 9:39 ` Guo Ren
2022-04-21 22:56 ` Boqun Feng
2022-04-22 1:56 ` Guo Ren
2022-04-22 3:11 ` Boqun Feng
2022-04-24 7:52 ` Guo Ren
2022-04-18 23:41 ` Andrea Parri
2022-04-19 17:13 ` Dan Lustig
2022-04-24 8:33 ` Guo Ren
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=YlbwOG46mCR8Q5tJ@tardis \
--to=boqun.feng@gmail.com \
--cc=arnd@arndb.de \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--cc=will@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