[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <596cb20e-a03c-cc69-d525-719d5a5b4c12@huaweicloud.com>
Date: Sat, 21 Oct 2023 15:45:16 +0200
From: Jonas Oberhauser <jonas.oberhauser@...weicloud.com>
To: paulmck@...nel.org
Cc: Akira Yokosawa <akiyks@...il.com>, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org, linux-doc@...r.kernel.org,
Alan Stern <stern@...land.harvard.edu>,
Andrea Parri <parri.andrea@...il.com>,
Will Deacon <will@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Boqun Feng <boqun.feng@...il.com>,
Nicholas Piggin <npiggin@...il.com>,
David Howells <dhowells@...hat.com>,
Jade Alglave <j.alglave@....ac.uk>,
Luc Maranget <luc.maranget@...ia.fr>,
Daniel Lustig <dlustig@...dia.com>,
Joel Fernandes <joel@...lfernandes.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH memory-model] docs: memory-barriers: Add note on compiler
transformation and address deps
Am 10/20/2023 um 7:56 PM schrieb Paul E. McKenney:
> On Fri, Oct 20, 2023 at 06:13:34PM +0200, Jonas Oberhauser wrote:
>> Am 10/20/2023 um 5:24 PM schrieb Akira Yokosawa:
>>> Hi Paul,
>>>
>>> On 2023/10/20 22:57, Paul E. McKenney wrote:
>>> [...]
>>>> So if there are things that rcu_dereference.rst is missing, they do
>>>> need to be added.
>>> As far as I can see, there is no mention of "address dependency"
>>> in rcu_dereference.rst.
>>> Yes, I see the discussion in rcu_dereference.rst is all about how
>>> not to break address dependency by proper uses of rcu_dereference()
>>> and its friends. But that might not be obvious for readers who
>>> followed the references placed in memory-barriers.txt.
>>>
>>> Using the term "address dependency" somewhere in rcu_dereference.rst
>>> should help such readers, I guess.
>> I think that's a good point.
> How about the commit shown at the end of this email,
I think it's very clear.
> with a Reported-by for both of you?
I haven't reported anything.
>>> [...]
>>>>> Thanks for the response, I started thinking my mails aren't getting through
>>>>> again.
>>> Jonas, FWIW, your email archived at
>>>
>>> https://lore.kernel.org/linux-doc/1c731fdc-9383-21f2-b2d0-2c879b382687@huaweicloud.com/
>>>
>>> didn't reach my gmail inbox. I looked for it in the spam folder,
>>> but couldn't find it there either.
>>> [...]
>>
>> Thanks Akira!
>>
>> I wrote the gmail support a while ago, but no response.
>>
>> Currently no idea who to talk to... Oh well.
> Your emails used to end up in my spam folder quite frequently, but
> they have been coming through since you changed your email address.
In return, I receive all mail from the mailing list, if is also
addressed to me, twice.
So it evens out, somehow? (I suspect this is a configuration error in my
mail filters on my side though)
Have a lot of fun,
jonas
Powered by blists - more mailing lists