On Thu, Jan 19, 2023 at 12:22:50PM +0100, Jonas Oberhauser wrote:
[For everyone else, Jonas is referring to the fact that the last two
On 1/19/2023 3:28 AM, Alan Stern wrote:
[It seems the e-mail still reached me through the mailing list]This is a permanent error; I've given up. Sorry it didn'twork out.
emails I sent to his huaweicloud.com address could not be delivered, so
I copied them off-list to his huawei.com address.]
I think this isn't going to be a problem. Certainly any realThe issue I have with this is that it might create accidental ordering. HowI consider that a hack though and don't like it.It _is_ a bit of a hack, but not a huge one. srcu_read_lock() really
is a lot like a load, in that it returns a value obtained by reading
something from memory (along with some other operations, though, so it
isn't a simple straightforward read -- perhaps more like an
atomic_inc_return_relaxed).
does it behave when you throw fences in the mix?
implementation of scru_read_lock() is going to involve some actual load
operations, so any unintentional ordering caused by fences will also
apply to real executions. Likewise for srcu_read_unlock and store
operations.