From: Alan Stern <stern@rowland.harvard.edu>
To: Jonas Oberhauser <jonas.oberhauser@huawei.com>
Cc: Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>,
"paulmck@kernel.org" <paulmck@kernel.org>,
"parri.andrea@gmail.com" <parri.andrea@gmail.com>,
"will@kernel.org" <will@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"boqun.feng@gmail.com" <boqun.feng@gmail.com>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"dhowells@redhat.com" <dhowells@redhat.com>,
"j.alglave@ucl.ac.uk" <j.alglave@ucl.ac.uk>,
"luc.maranget@inria.fr" <luc.maranget@inria.fr>,
"akiyks@gmail.com" <akiyks@gmail.com>,
"dlustig@nvidia.com" <dlustig@nvidia.com>,
"joel@joelfernandes.org" <joel@joelfernandes.org>,
"urezki@gmail.com" <urezki@gmail.com>,
"quic_neeraju@quicinc.com" <quic_neeraju@quicinc.com>,
"frederic@kernel.org" <frederic@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools: memory-model: Make plain accesses carry dependencies
Date: Thu, 1 Dec 2022 15:21:06 -0500 [thread overview]
Message-ID: <Y4kMskpQGOvlPyYf@rowland.harvard.edu> (raw)
In-Reply-To: <6abbb72eef6149eb842a3351ecea7af5@huawei.com>
On Thu, Dec 01, 2022 at 05:21:45PM +0000, Jonas Oberhauser wrote:
> Thanks a lot for the helpful and detailed comments!
> Three minor points before I send a new patch:
>
> > even if W' or R' (or both!) is plain.
>
> The "is" sounds slightly weird to me in the sentence because the last part I read is
> "(or both!)", so I would slightly prefer "are" here.
People are pretty casual about subject-verb number agreement these days
(there's a growing tendency in English for people to make the verb agree
with the last noun occurring in the subject rather than the subject as a
whole), so that should be okay.
> > On the other hand, if you change the second "dependencies" to "ones" and "unmarked" to "plain", maybe the whole thing will fit on one line.
>
> It fits even if I changed the second dependencies to "those" instead of "ones", i.e.,
> (* Redefine dependencies to include those carried through plain accesses *)
>
> which I would prefer.
Fine.
> > if you replaced the whole conditional with a simple
> > WRITE_ONCE(*y, *z2);
> > then the litmus test would become an example of OOTA!
>
> In my opinion it is already an example of OOTA, which I would define as an
> rfi | ctrl | addr | data | fence
> cycle.
That's not an unreasonable point of view (if you put rfe rather than
rfi), but to me OOTA suggests something more: a value arising as if by
magic rather than as a result of a computation. In your version of the
litmus test there is WRITE_ONCE(*y, 1), so it's a little understandable
that you could end up with 1 as the final values of x and y. But in my
version, no values get computed anywhere, so the final value of x and y
might just as easily be 1 or 56789 -- it literally arises "out of thin
air".
> Let me know if you agree with these deviations from your suggestion
> and have a great time,
Yes; with those changes you can add:
Reviewed-by: Alan Stern <stern@rowland.harvard.edu>
> jonas
>
> PS:
> > When a colon is followed by a clause (as opposed to a list), it is customary to capitalize the first letter of that clause, just like we capitalize the first letter at the start of a sentence.
>
> In German, we also capitalize after a colon; but my English teachers used to deduct many points throughout my adolescent life whenever I capitalized like that. I still remember some of that red ink with near perfect clarity. So I eventually really took it to heart and started pedantically not-capitalizing after every colon.
> Now the only time it ever mattered in my adult life, I find that I should do it German Style (or, as I just learned, APA & AP Style).
> I suppose life is that way sometimes.
Indeed.
Alan
next prev parent reply other threads:[~2022-12-01 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:18 [PATCH] tools: memory-model: Make plain accesses carry dependencies Jonas Oberhauser
2022-12-01 16:02 ` Alan Stern
2022-12-01 17:21 ` Jonas Oberhauser
2022-12-01 20:21 ` Alan Stern [this message]
2022-12-02 17:22 ` Jonas Oberhauser
2022-12-02 20:22 ` Alan Stern
2022-12-03 11:47 ` Jonas Oberhauser
2022-12-03 15:20 ` Alan Stern
2022-12-03 19:04 ` Paul E. McKenney
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=Y4kMskpQGOvlPyYf@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=frederic@kernel.org \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=jonas.oberhauser@huawei.com \
--cc=jonas.oberhauser@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=quic_neeraju@quicinc.com \
--cc=urezki@gmail.com \
--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