From: Peter Zijlstra <peterz@infradead.org>
To: guoren@kernel.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-csky@vger.kernel.org, linux-arch@vger.kernel.org,
Guo Ren <guoren@linux.alibaba.com>,
Arnd Bergmann <arnd@kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH v2 1/5] csky: Remove custom asm/atomic.h implementation
Date: Thu, 7 Jan 2021 12:19:04 +0100 [thread overview]
Message-ID: <X/buKPr5OCH3C32J@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1608478763-60148-1-git-send-email-guoren@kernel.org>
On Sun, Dec 20, 2020 at 03:39:19PM +0000, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> Use generic atomic implementation based on cmpxchg. So remove csky
> asm/atomic.h.
Clarification would be good. Typically cmpxchg() loops perform
sub-optimal on LL/SC architectures, due to the double loop construction.
next prev parent reply other threads:[~2021-01-07 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 15:39 [PATCH v2 1/5] csky: Remove custom asm/atomic.h implementation guoren
2020-12-20 15:39 ` [PATCH v2 2/5] csky: Fixup barrier design guoren
2020-12-20 15:39 ` [PATCH v2 3/5] csky: Fixup futex SMP implementation guoren
2020-12-20 15:39 ` [PATCH v2 4/5] csky: Fixup asm/cmpxchg.h with correct ordering barrier guoren
2021-01-07 12:40 ` Peter Zijlstra
2021-01-21 7:05 ` Guo Ren
2020-12-20 15:39 ` [PATCH v2 5/5] csky: Cleanup asm/spinlock.h guoren
2021-01-07 12:45 ` Peter Zijlstra
2021-01-07 11:19 ` Peter Zijlstra [this message]
2021-01-21 7:10 ` [PATCH v2 1/5] csky: Remove custom asm/atomic.h implementation Guo Ren
-- strict thread matches above, loose matches on Subject: below --
2020-12-20 15:12 guoren
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=X/buKPr5OCH3C32J@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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