From: Torvald Riegel <triegel@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: andreas@gaisler.com, libc-alpha@sourceware.org,
adhemerval.zanella@linaro.org, carlos@redhat.com,
software@gaisler.com
Subject: Re: [RFC][PATCH 0/2] Make sparcv8 work again on cas enabled hardware
Date: Wed, 02 Nov 2016 22:33:00 -0000 [thread overview]
Message-ID: <1478125983.7146.733.camel@localhost.localdomain> (raw)
In-Reply-To: <20161102.113238.241484722789762790.davem@davemloft.net>
On Wed, 2016-11-02 at 11:32 -0400, David Miller wrote:
> From: Torvald Riegel <triegel@redhat.com>
> > Or do you intend to write sparc-specific versions of all the concurrent
> > data structures that are process-shared?
>
> This would be necessary anyways, if we have two modes. One that does
> the pure-userland code path and one that does the kernel helper code
> path.
All the other archs that use a kernel helper for CAS don't need it. If
you can call the helper in the atomic operations, you won't need a new
algorithm except if you wanted to optimize the generic one.
> Furthermore, sparc specific versions are needed in any case since we
> have the v9 detection even in the v8 libraries. Look at all of the
> code that checks for v9 in the dl_hwcap mask when deciding which
> atomic operation to use.
Or are you talking about the implementation of the atomic operations?
next prev parent reply other threads:[~2016-11-02 22:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 15:08 Andreas Larsson
2016-11-01 15:08 ` [RFC][PATCH 2/2] sparc32: Use cas for atomic_* operations and use general pthread_barrier_wait Andreas Larsson
2016-11-04 18:37 ` David Miller
2016-11-04 18:44 ` David Miller
2016-11-01 15:08 ` [RFC][PATCH 1/2] sparc32: Mark sendmsg and recvmsg system calls as unsupported Andreas Larsson
2016-11-01 17:28 ` Adhemerval Zanella
2016-11-02 11:38 ` Andreas Larsson
2016-11-02 12:49 ` Adhemerval Zanella
2016-11-04 18:36 ` David Miller
2016-11-01 16:00 ` [RFC][PATCH 0/2] Make sparcv8 work again on cas enabled hardware Torvald Riegel
2016-11-01 16:09 ` David Miller
2016-11-01 16:46 ` Torvald Riegel
2016-11-01 16:51 ` David Miller
2016-11-02 10:05 ` Torvald Riegel
2016-11-02 11:29 ` Andreas Larsson
2016-11-02 15:32 ` David Miller
2016-11-02 22:33 ` Torvald Riegel [this message]
2016-11-03 2:52 ` David Miller
2016-11-03 15:39 ` Torvald Riegel
2016-11-03 17:22 ` David Miller
2016-11-03 18:41 ` Adhemerval Zanella
2016-11-03 20:33 ` David Miller
2016-11-03 21:29 ` Adhemerval Zanella
2016-11-03 22:25 ` Torvald Riegel
2016-11-04 10:28 ` Andreas Larsson
2016-11-04 15:23 ` David Miller
2016-11-04 13:55 ` Richard Henderson
2016-11-04 15:31 ` David Miller
2016-11-04 16:10 ` Richard Henderson
2016-11-04 14:04 ` Richard Henderson
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=1478125983.7146.733.camel@localhost.localdomain \
--to=triegel@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=andreas@gaisler.com \
--cc=carlos@redhat.com \
--cc=davem@davemloft.net \
--cc=libc-alpha@sourceware.org \
--cc=software@gaisler.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).