From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: Helge Deller <deller@gmx.de>, Richard Henderson <rth@twiddle.net>,
John David Anglin <dave.anglin@bell.net>,
linux-parisc@vger.kernel.org
Subject: Re: Testing the lws_compare_and_swap_2 syscall
Date: Tue, 7 Nov 2017 22:46:25 +0100 [thread overview]
Message-ID: <1510090803@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <20171106212734.GA29237@ls3530.fritz.box>
Helge Deller wrote...
> * Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>:
> > Status: My system boots and all my tests pass. However, I find smartd
> > stalling in 100% CPU, might be coincidence. Now I'm putting some more
> > load onto the box to see whether it's less crashy then it used to be the
> > previous weeks.
>
> Did you continued your tests?
> How were the results.
Basically I gave up on this. My change made things worse, and while I
still didn't get the point (read: For my understanding there's a
discrepancy between the syscall's description and what actually
happens), it's certainly better to keep things the way they are.
> > Aside, there is another ",ma" modifier in lws_compare_and_swap that I
> > fail to understand. Haven't checked yet in detail yet, though.
>
> I'd suggest to keep the other ",ma" modifiers for now.
Since, as I presume, this has no impact on performance, this boils down
to aid a human reviewing the code in understanding what's happening
here.
Christoph
prev parent reply other threads:[~2017-11-07 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 20:03 Testing the lws_compare_and_swap_2 syscall Christoph Biedl
2017-10-25 1:48 ` John David Anglin
2017-10-26 0:22 ` Christoph Biedl
2017-10-26 14:06 ` John David Anglin
2017-11-06 21:27 ` Helge Deller
2017-11-06 22:45 ` John David Anglin
2017-11-07 21:31 ` John David Anglin
2017-11-07 21:46 ` Christoph Biedl [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=1510090803@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.